4 ms·
>Federated E2EE can work. Matrix did it Kind of hard to claim they've done it given their current level of adoption.
by bragr 4y ago
>Federated E2EE can work. Matrix did it
Kind of hard to claim they've done it given their current level of adoption.
- Arathorn 4y agoQuite easy actually when you look at the number of governments who rely on Matrix - https://element.io/case-studies/tchap https://element.io/case-studies/tchap, https://element.io/case-studies/bundeswehr https://element.io/case-studies/bundeswehr and many more (US, UK, Sweden, Ukraine, Luxembourg, Finland…). But if your friends aren’t on it, i guess that means nothing.
- jwestbury 4y ago> But if your friends aren’t on it, i guess that means nothing. Well... yes, actually. Governments use a lot of things that don't have widespread adoption outside of governmental use cases. If your goal is to build for that market -- for environments with very specific needs -- then you're doing a great job. But governmental use isn't the ringing endorsement that you seem to think, because it has no bearing on actual widespread adoption.
- omniglottal 4y agoBack in the day, I used to use BBSes via local dial-up. Everyone did, so you could expect BBSes were on the rise from so much usage. Meanwhilr, governments were stuck on ArpaNet and futzing around with some newfangled "TCP/IP" protocol. What good does government support even provide???
- recuter 4y agoHis entire point is that Matrix went for and is in the process of getting the larger goal right for the sake of long-term adoption at the cost of development time -- whereas Signal opted for worst-is-better limited-scope pragmatism for the sake of near-term adoption. Whatever lesson you want to derive from this technical trade-off is up to you, but yeah the psychobabble about Moxie is absolutely tiresome.