What the hell is wrong with XMPP?

As always, this shit is touted as the next best thing by the terminally genius ivory tower dwellers who populate FOSS projects, but what it really is is a piece of stinking crap.

For 25 years now, none, I repeat, none of the servers or clients, be it the hugely overrated OpenFire or modest Jabberd and its clones, on the server side, or Jitsi, Pidgin, Gajim, Dino, Conversation, ConverseJS, yada, yada, yada, are able to do anything more than to send plain-text messages.

For 25 fucking years their enormously arrogant teams berate users for not being able to make sense of their monstrosities, other than in the ideal environment which means widely open to all hackers of the world, ideally from a CDN or when using their own server, they only mimic the success of the 35 now year old ICQ, and this is the best they can do.

Lots of lies are being circulated about XMPP: that it can offer rich content such as voice, video, or desktop sharing. No, it can't. It can't even reliably send an encrypted message, whether with OTR or OMEMO. It can't even reliably send a file. It can't even reliably send a screenshot.

Its commercial competition be it Skype, Teams, Telegram, Zoom, Watsapp or whatever have zero problems doing all of the above, but the terminally genius FOSS community is stuck on stupid: barks at users and puffs its cheeks.

Dare to tell them that their stuff does not work, and bear consequences: berating, shaming, abusive behavior, cancellation.

Dudes! You demand respect. Respect can be only earned. It cannot be forced. Yes, we do not respect you because you claim lots but deliver zilch. All you can do with this is learn a lesson and deliver. Until then you are nobody but anonymous Internet failures.

Posted by: LinuxLies at 11:19 AM | No Comments | Add Comment
Post contains 316 words, total size 2 kb.