3 ms·
Signal choosing not to federate isn't in the scope of this thread. IMO not federating is a guarantee of client quality. The last time I had a look at Matrix E2E
by maqp 5y ago
Signal choosing not to federate isn't in the scope of this thread. IMO not federating is a guarantee of client quality. The last time I had a look at Matrix E2EE implementations, only Riot was barely usable. There was a ton of clients that didn't support it, didn't intend to, didn't have the confidence to go about implementing etc.
>Also, what about the server source code?
https://github.com/signalapp/Signal-Server https://github.com/signalapp/Signal-Server There you go, last commit two days ago.
- int_19h 5y ago> IMO not federating is a guarantee of client quality. That's not how it worked out for email long-term; why should IM be any different?
- tffgg 5y agoIt's not a quality guarantee for clients in practice since you can't control Client Side with open source Regarding Riot, which is called Element by now, you may want to update your knowledge
- maqp 5y agoYeah I'm familiar with Riot being called Element now, and you don't need to look further than this chat for me to state that. "It's not a quality guarantee for clients in practice since you can't control Client Side with open source" What? Open source native client with reproducible builds is literally the gold standard of individual control over software, it's even GPL licenced.