![]() ![]() They tried to do too much, for too many platforms, they did it badly, and they did it in a lowest-common-denominator (hence: “ race to the bottom“) kind of way, meaning that the “open” clients like Pidgin and Adium were always going to be second class citizens (no stickers, no payments, no location sharing, no heart-emoji-animation-effects) and – worse – the people using the clients would be complaining about being second class citizens whilst also being righteous about exercising their choice to use shit software. Reason: the extant XMPP and MQTT clients were, frankly, pieces of shit. This was - including by me - regarded as a “ bad thing” from the perspective of software and communications freedom, and at the time I felt that that was a valid complaint. Sometime around 2013, Facebook removed XMPP API and (eventually) MQTT API access to Facebook Messenger, which killed-off the ability to use Facebook Messenger from third-party clients such as Pidgin or Adium. …but it’s still a bloody scary, illiberal, misconceived idea. We need Messenger Interoperability – Martin Recke.Why Messenger Interoperability is a digital canary in the coal mine – Adam Tinworth.Interoperability as a tool for competition regulation – Ian Brown.I’m relieved that ( so far?) (April 2022 Edit: Alas, I was correct.) I seem to have misspoken about the depth of active EU commitment and have simply been channeling Professor Ian Brown and a selection of journalism pundits, for instance: …and I used that observation to kick off some side discussion, essentially that any academics who are trying to solve for “ tracking a message’s creation and propagation within a messenger platform” will be stymied in a few years by EU demands to “ open up messengers to competition” by coercing them all into interoperability, thereby turning our ecosystem of diverse messaging platforms into the same kind of “ race to the functional bottom” nightmare where email has lived for the past 25 years. Would this mean that E2EE messenger apps would have to restrict/track use of being used to transport super encrypted content? q.v. This will be a nightmare re: proper and complete, interoperable crypto within (say) the Signal message space/network, but putting that aside: this also opens-up the potential for re-emergence of over-the-top E2EE like OTR on Pidgin/Adium was (same crypto, multiple transports). Regards cross-platform communication, the European Union is on track to pursue “interoperability” APIs so as to open up alternative-client access to messengers. technical proposals to implement “sender tracking” of messages in ways that the (eg: Indian) Governments are NOT asking for, thereby simultaneously weakening the defence against implementing what the Governments ARE asking for, whilst also not solving THAT problem in a minimally-privacy-invasive way.Īt one point I made the following observation in the chat:.distributed client-side keyword blocklists.…and there were also some (IMHO) disastrous suggestions, such as: ![]() reddit/slack-bot like “vaxbots” (“ you appear to be repeating some misinformation re: Covid, here are some links to sites which explain the issues…“).There were some (IMHO) constructive solutions proposed, such as: I was on a E2EE conference Zoom-call yesterday, run by the Stanford mob and discussing combatting political misinformation on end-to-end-secure messenger platforms. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |