4 ms·
- Lack of federation Use a federated secure protocol. Oh wait, there are none. Because if a problem appears you just can't fix it without breaking all federate
by raverbashing 10y ago
- Lack of federation
Use a federated secure protocol. Oh wait, there are none. Because if a problem appears you just can't fix it without breaking all federated clients. And then they will whine.
- Dependency on Google Cloud Messaging
Fair enough
- Your contact list is not private
Fair enough
- The RedPhone server is not open-source
While it would be nice that it was Open sourced I can understand them not releasing it (might be for IP issues)
tl,dr: "Signal does not work the way I wanted"
- SamWhited 10y ago> Use a federated secure protocol. Oh wait, there are none. Because if a problem appears you just can't fix it without breaking all federated clients. And then they will whine. That's why you have to design your protocol with backwards compatibility and versioning in mind, ala XMPP. I'm not going to pretend its perfect, but it works pretty well 90% of the time. It does mean clients have to implement versioning and feature negotiation and not just blindly assume everything else supports all the features they do; convincing client authors to do this is the tricky part.
- nickik 10y agoThere are really two federated protocols, xmpp and matrix. Matrix is pretty young but looks good, they just added e2e encryption. Check out the Riot client, web, android and ios. The apps are even native. Plus, you don't have to show your phone nr.
- antocv 10y agoRing.cx and tox.im work better. Signal is a honeypot by NSA/Google and the likes.
- qwertyuiop924 10y agoUmm... Tox?
- exo762 10y agoTox on mobile? Have you actually tried to use it? It drains your battery like crazy.
- qwertyuiop924 10y agoHe didn't ask about that. He asked about a federated/distributed protocol that actually worked. Tox is one.