Frédéric JacobsApr 5, 2017

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?

Show threadxamar
@fj Doesn't do harm to require content signing as it provides source verification. Along with certificate pinning you can spot impostors. It also enables adding per certificate trust levels for server-to-server and end user identification or source via visual representation of the key's fingerprint.
Apr 5, 2017 at 4:58pmWeb