No idea what the Google login thing was. If I had to take a wild guess, maybe you found some place that also offers some key management/signing features as a way to make things more user friendly?
I’ll buy that. I just have trouble squaring things like that with things like gpg-agent and how they cache passphrases and keep them from swapping to disk, etc. I’d want to know more about it and whether it’s generated in the browser or on the server. I’m also not even sure how I’d go about doing some sort of review of the javascript algorithms or where their random numbers come from. I’m not throwing shade on them; I just don’t know.
I’d want to know more about it and whether it’s generated in the browser or on the server.
FWIW, most of these web-based Nostr clients are just static JS files. They’re SPAs that connect to the relay servers (via WebSocket, IIRC). You can open up your browser’s devtools, go to the “Network” tab, and see what’s happening.
I don’t think I’d trust one that does any server-side rendering. No particular reason (though I’m sure I could think of some) other than it just wouldn’t feel right for Nostr.
I’m also not even sure how I’d go about doing some sort of review of the javascript algorithms or where their random numbers come from
I’d guess they just use the native WebCrypto APIs, but I have not verified. More info on native crypto APIs available in JS here:
https://nostr.com/
I’ll buy that. I just have trouble squaring things like that with things like gpg-agent and how they cache passphrases and keep them from swapping to disk, etc. I’d want to know more about it and whether it’s generated in the browser or on the server. I’m also not even sure how I’d go about doing some sort of review of the javascript algorithms or where their random numbers come from. I’m not throwing shade on them; I just don’t know.
I’ll look.
FWIW, most of these web-based Nostr clients are just static JS files. They’re SPAs that connect to the relay servers (via WebSocket, IIRC). You can open up your browser’s devtools, go to the “Network” tab, and see what’s happening.
I don’t think I’d trust one that does any server-side rendering. No particular reason (though I’m sure I could think of some) other than it just wouldn’t feel right for Nostr.
I’d guess they just use the native WebCrypto APIs, but I have not verified. More info on native crypto APIs available in JS here:
(FWIW, every Node.js distro I’ve ever used leveraged OpenSSL for those, under the hood. I imagine other runtimes do too.)