|
|
|
|
|
by ycmbntrthrwaway
3409 days ago
|
|
The problem with federated approach is that it leaks metadata. When you take centralized system apart and expose internal communications to the Internet, you reduce anonymity. Extreme case is when everyone uses his own homeserver and information on who calls who and when is completely exposed. It is not enough to make the system distributed, you need to exploit the fact that different parts of the network are controlled by different parties to build self-enforcing protocols that ensure anonymity. For comparison, see how bitcoin is just distributed and zerocoin is anonymous. Gnutella is just distributed and FreeNet is anonymous. |
|
https://whispersystems.org/blog/giphy-experiment/
This is how Signal provides Giphy search (spoiler: they tunnel a TLS connection through their own server, with TLS negotiated end-to-end from the Signal app to the Giphy server, so that Giphy can't tell what client is searching for what GIF while at the same time Signal's server's can't see what people are searching for).
Does anyone believe that in a world where 90% of Signal-network client installs weren't Signal.app, that this is how features like this would work? It's not an unknowable question. All you have to do is look and see how Signal's competitors, like Wire, tackle this problem.
It's true that in a federated Signal-network, you might get clients that have security features Signal itself lacks. But because it's far easier to produce an insecure client than a secure one, insecurity will dominate, and be a boat anchor around any efforts to improve security down the road.
Call it "the libpurple problem".