The perils of federated protocols
The perils of federated protocols
Posted May 19, 2016 13:08 UTC (Thu) by javispedro (guest, #83660)Parent article: The perils of federated protocols
E.g. end to end decryption does not really require changes on the protocol (on the contrary; if you need to change the protocol it most probably means you're leaking information to the server).
Posted May 19, 2016 13:41 UTC (Thu)
by pizza (subscriber, #46)
[Link] (2 responses)
The funny thing about XMPP interoperability is that, it was the big players (most notably Google) that were the worst offenders -- For example, Google Talk was subtly incompatible with the Jingle spec and reference implementation that Google itself authored.
Posted May 26, 2016 3:33 UTC (Thu)
by Garak (guest, #99377)
[Link] (1 responses)
Posted May 26, 2016 11:13 UTC (Thu)
by pizza (subscriber, #46)
[Link]
I don't see this at all. There is real value in a third party providing services for folks who can't be bothered to do it themselves -- and I say this as someone who chooses to run his own.
The home-server-persecution bit is largely ISP driven because it breaks their asymmetric download-heavyish models they've based their pricing on. That, and the sad fact that most home systems' "servers" are really just spam bots and sources of various forms of malware.
The perils of federated protocols
Long Live The Prosperous Federation, So Say We All!!!
Long Live The Prosperous Federation, So Say We All!!!