Aye, my proposal was a trade off between privacy and convenience for non technical users ( it's only as bad as a non federated social media site).
The best balance here would be a client on the user device that manages the keys for you, and an API in lemmy for accepting and sending encrypted messages.
As a side note, I thing PGP is more or less superseded by AGE
On encrypting messages, this is a solved e2e problem if users home instances generate public private key pairs for its users on sign-up ( or users can provide their own )
Tbh it would be trivial to just salt and hash the usernames (for keying the votes), no need to encrypt or involve the users password. The salting and hashing would be handled by the users home instance ( which presumably the user trusts ) so building a rainbow table would be non trivial for an attacker ( assuming the home instance keeps its salts secret ).
Ah right! I didn't realise that switching instances would invalidate your Auth! This sounds very useful. I'm with you that the platform should probably just handle this!
Noob here! Why would you want to? This Is the first federated service I've used!
It could be a vets I suppose. Still odd.