Post #3846257
2026-07-16 00:23 UTC
Replies (1)
-
@azonenberg@ioc.exchange 2026-07-16 00:44
@soatok@furry.engineer @hazelnoot@enby.life I guess a higher level question: most people use fedi partially or entirely via web frontends. Is any kind of meaningful E2EE possible if you aren't storing secrets and running trusted code client side in a thick client? I think not - the instance either has to store a long lived key or derive it from your password, and even if the crypto itself runs clientside it's in javascript authenticated only by the server's TLS certificate. Meaning that a rogue instance can read or tamper with your traffic. So what's the plan for this use case? Do you make E2EE messages only work with native clients? Allow users to store a key server side and make the UI clearly explain that they are trusting the instance by doing so? I feel like the UI/UX challenges here are 10x harder than the cryptographic ones.