Earlier quoted context omitted.
> but at the very least I think Bluesky could start with generating a private key on each client device, and then using a simple box algorithm to encrypt messages towards the user they want to talk to. Furry cryptography nerd here. No. This is inadequate. > I don't think https://tweetnacl.cr.yp.to/ is hard to mess up. Yes it is! If you're doing to encrypt some things in a constrained use-case, sure, NaCl is better th…
Well, exactly. My point is that in a constrained use-case NaCl would be sufficient. If you want to rotate keys, then simply delete your private key and since we trust Bluesky so much we can use the PDS to share new pubkeys once we rotate. In fact, this would work for signing keys too! Then the PDS wouldn't be able to write messages for you if it wanted to. For group messaging you simply encrypt the message to each re…
https://github.com/soatok/rawr-x3dh
I'm telling you, TweetNaCl is not enough to build a secure messenger
libsodium, maybe