Important progress has been made regarding bringing MLS end-to-end encryption to the ActivityPub protocol, with developers already building implementations and providing feedback to a future version of the protocol spec.
Important progress has been made regarding bringing MLS end-to-end encryption to the ActivityPub protocol, with developers already building implementations and providing feedback to a future version of the protocol spec.
why? because it would be cool if only intended recipients are able to view sent messages.
That’s not really going to be the case if you’re using a website instead of an audited app like signal/matrix.
that argument doesn’t hold. you’re letting perfect be the enemy of good-and if you truly believe that, then you wouldn’t be recommending Matrix which has web clients, see https://app.element.io/
Any we client including Matrix webclient is incredibly vulnerable to the server just injecting JS and reading your messages.
Like there is no point of E2E encryption in Twitter, Musk can read your messages if you open them on any device he can execute arbitrary code on.
That doesn’t preclude fediverse clients from enabling E2EE. A web-client isn’t a requirement.
Agreed, nobody should trust twitter, but I would trust most mastodon clients to send encrypted messages, if/when implemented correctly. Does it guarantee that messages will never be read? No, but it does an extra layer that wasn’t there before.