> There are two hard things in computer science: cache invalidation, naming things, and off-by-one errors.
@raichoo Any feature in any complex software needs permanent work. E.g. developers change APIs, then plugins must be changed accordingly. Because many XMPP client developers use OMEMO these days, they don't want to have additional (most of the time unpaid!) work to keep OTR code up to date. If somebody would do the work, OTR would remain. But it seems, that nobody cares enough. Maybe energy is better spend in adding OMEMO support to the clients, that don't have it yet?
The question is: Why is XMPP federated and why do so many servers exist and federate successfully? And why is Matrix poorly federated and 99.8 % of all Matrix users are on matrix.org?
Because XMPP has, despite many issues and drawbacks, a very good, solid design. That's why you can run Ejabberd or Prosody on a Raspberry Pi and that's why a chat system with 1 billion users, WhatsApp, is based on XMPP.
Matrix is not bad and has a nice (but slow) client, but cannot compared to XMPP.
Gut, der Weg zu den Wurzeln scheint auf jeden Fall kein breiter zu sein ;-) viele wandern offenbar nicht darauf
I've decided to start a regular progress note on SàT, to show new features and explain design choices, you can find it at
Please let me know if you find it useful to see if I should continue :)
2019-04-10 18:00 CEST
xHain, Grünberger Str. 14, 10243 Berlin
Nice look over the rim of the tea cup and definitely something the XMPP ecosystem needs.
Framapiaf est un service de microblog similaire à Twitter. Il est libre, décentralisé et fédéré. Il permet de courts messages (max. 500 caractères), de définir leur degré de confidentialité et de suivre les membres du réseau sans publicité ni pistage.