Mastodon's federation introduces UX challenges.
One that worries me a lot is about message forgery. Anyone can forge a twoot, even cross-server.
Whereas Twitter Inc might be trustworthy enough to not forge transcripts. Anyone can run a Mastodon server and might want to abuse it to influence people (see Russian troll campaigns).
Should Mastodon "home servers" cryptographically sign updates? Should there be end-to-end signatures? Anyone has thoughts on this?
@fj e2e is mandatory at least for dm. Signature should also be implemented in order to be able to validate both accounts and contents.
Not easy, but if we want to be able to trust contents and members, it must be there, and in the easiest possible way so that everybody can use it without hassle nor pain.
