Hacker News new | ask | show | jobs
by cgranier 1315 days ago
I did not know this...
2 comments

If you are about to write a DM you will see this warning:

  Posts on Mastodon are not end-to-end encrypted. Do not share any sensitive information over Mastodon.
What did you expect? Messages have to be stored on the server, and the instance owner has access to the server...
(Hypothetically) wouldn't it be possible for client devices to generate key pairs, and for messages to be stored on the server encrypted in such a way that recipients' client devices could decrypt them? (I think that's what Signal does?)

Not saying that that's what happens on Mastodon instances, I don't know enough about it's operation to comment.

Yes, end-to-end encryption is possible. It just needs support in clients, as well as a common protocol if you want it to work between different clients.

Mastodon has actually done some work towards that but I don't think it's useable yet, see https://github.com/mastodon/mastodon/pull/13820

Thanks!
Normal users do not understand what federation is, much less how messages are stored.
This has nothing to do with federation. It's just a fact of life on any hosted internet service.
Chances of a centralized Twitter stealing your sensitive information is quite a bit lower than N number of federated Mastodon instances run by any number and types of actors.
Not if end-to-end encryption is available.
If you don't own the key exchange (and you don't, even on the services most people consider secure), you're still, on some level or another, just relying on trust that this is the case.

At any rate, mastodon is a web app, not an IM client. No one who's ever raised this has even begun to explain how you could work e2e into something like it. Certainly no other microblogging platform has e2e anything, because that's not actually a thing that makes sense.

> because that's not actually a thing that makes sense.

No for micro-blogging, but Mastodon supports direct messaging, and if you support direct messaging, you should support end-to-end.

> If you don't own the key exchange ...

Sure, but I trust https://letsencrypt.org/ more than I trust some random running a server.

The foundations for E2EE were merged into Mastodon, there's a merged pull request for it elsewhere in this thread.