pull down to refresh

Guess Nostr's still at the stage where each user should audit code and network access themselves.
Wonder what the disclosure timeline on this was. Did he just open up the bug tool one day and go wow that's bad or did someone alert him.
The fun part is hodlbod can never prove that he doesn't have all those nsecs so lots of people should be setting up new npubs and deprecating existing ones. Might turn into a sort of proof of alive followers event.
reply
21 sats \ 0 replies \ @ek OP 26 Oct
Wonder what the disclosure timeline on this was. Did he just open up the bug tool one day and go wow that's bad or did someone alert him.
Second sentence actually 👀
This morning, as I was adding error handling to flotilla, I discovered that Coracle has been sending user session objects to bugsnag when reporting errors.
reply
Read again the note. Is about those users that didn't used an external keys extension signer and directly used nsec to login.
Always use Alby, nos2x or hardware signer to login on nostr clients. Do not use directly plain text nsec. more nostr signers:
Putting your nsec in plain text is like pasting your BTC wallet seed in plain text on a random webpage...
reply
People always say that but it also seems reasonable to expect an app not to send the nsec anywhere. It's not like it was hacked. A signer app may separate concerns but it's still more code to audit.
reply
It's a common practice now that you as a developer need "external" tools to know what's is going on in your own program, sad... but true.
reply
47 sats \ 0 replies \ @nym 26 Oct
If I read this correctly. Someone else had the API key also
reply