Post #1229251

2026-04-15 15:16 UTC

@jaz @benpate @earth_walker I understand you do not know, but my point is if you are operating a mastodon instance, and you are connecting users via https, you are already operating a E2EE service. That is what https is (via TLS, used to be SSL). You do not need to know more to have your messaging be E2EE within the instance unless they have done something very wrong with the masto instance. It's an international standard, the concerns you have can be raised, but likely are not valid.

Replies (2)

@reflex@retrogaming.social 2026-04-15 15:18

@jaz @benpate @earth_walker HTTPS is E2EE between the server (instance) and client (app/browser/etc). It ensures data in transit cannot be intercepted easily. E2EE messaging is the same thing but user to user, essentially keeping the data invisible to the server (instance). Same principle. It's commonly used and typically invisible to the admin. It does not block screenshots, reporting mechanisms will still be valid. Again, assuming this implementation does not do something weird.

Open ##1229252
@benpate@mastodon.social 2026-04-15 16:11

Sorry. We are talking about a different end. E2EE means encrypting messages from my device all the way through to your device, and not being decrypted by the server in the middle. HTTPs://does not do this, so this message I’m sending to you is readable by the admins of several intermediate servers. It’s a very different model for communication. @reflex @jaz @earth_walker

Open ##1328810