3 ms·
Perhaps the "federation" that should evolve is not federation of the servers behind a single protocol or app, but federation between multiple apps. Applying the
by chatmasta 11y ago
Perhaps the "federation" that should evolve is not federation of the servers behind a single protocol or app, but federation between multiple apps. Applying the traditional definition of "federation" to Signal implies that any entity could host a Signal server, and any Signal client could talk to that server. Moxie mentions the main issue with this, namely that because of the "evolving ecosystem," it's impossible to keep all servers using the same protocol. Also consider that trust is another significant issue -- can you trust the operator of the Signal server you're connecting to? Can you trust not only that the server software is up to date, but also that no malicious actor has modified it?
Because of these trust issues, the benefits of federation for users are unclear. Why connect to some random Signal server if you feel safer connecting to the official servers?
If the answer to that question is, "because I can connect to my own Signal server, so I don't need to trust anyone," then I posit this question: Do you need permission to build a federated service? Is it possible that federation can evolve without any central planning or permission to do so?
Consider the "messenger wars" of the early 2000s. There was no official "federation" of messaging services, and yet, people built clients that could interoperate with all of them. In fact, Microsoft itself wrote a client that was interoperable with AIM. [0]
Why can't the same sort of "grassroots federation" evolve within the current ecosystem of chat apps? If somebody reverse engineers the whatsapp protocol and builds a "whatsapp server," then modifies the whatsapp binary to talk to it (perhaps using something like theos-jailed [1]) instead of the official servers, isn't that effectively accomplishing unsanctioned federation? Along the same lines, is there anything stopping somebody from reverse engineering Signal to talk to Whatsapp, and vice versa?
The "walled gardens" have made it harder to reverse engineer binaries and protocols, but there is no fundamental impediment to achieving cross-messenger interoperability. If developers are motivated enough to build third party clients, it will always be possible, although the requisite reverse engineering effort grows more complex with every release.
[0] https://nplusonemag.com/issue-19/essays/chat-wars/ https://nplusonemag.com/issue-19/essays/chat-wars/
[1] https://github.com/BishopFox/theos-jailed https://github.com/BishopFox/theos-jailed
- mcepl 11y agoSee http://spectrum.im/ http://spectrum.im/ with https://github.com/davidgfnet/whatsapp-purple https://github.com/davidgfnet/whatsapp-purple (or use it with pidgin/adium/finch directly).