Every chat system after #Zephyr was a mistake.
https://mov.im/blog/debacle/76bf90a4-5f59-4962-92db-6cd859f42ec9
Seriously, IRC is not my cup of tea. I want to receive messages when offline, multiline messages, multi-device support, message correction, message reactions, message retraction, message replies… I'll stay with #Jabber, which is brandnew compared to Zephyr or IRC 
I wish people had even higher expectations for #instantMessaging apps: #Privacy, #noAds, freedom from corporate interests, respect for #humanRights, low energy consumption, #digitalSovereignty. And not AI powered, flashy #stickers.
Free and federated applications and services, made and run by e.g. small cooperatives or volunteers, cannot compete with billion dollar companies on resources. We have other strengths, though!
(Btw. I love stickers!)
A recent security audit of #Conversations_im¹ found that wildcard certificate handling didn’t fully comply with the spec.
Conversations was accepting *.a.example for c.b.a.example, even though wildcards are only meant to match a single label.
This issue has been fixed in version 2.18.0, now live on Google Play.
#XMPP Community
XMPP #Sprint in #Berlin on 23rd - 25th May 2025! It is open to all interested.
More details: https://wiki.xmpp.org/web/Sprints/2025-05_Berlin
#jabber #chat #interoperability #rtc
#opensource #decentralization #standard
Yw!
Note, that when you have `apt-listchanges` on your #Debian (or derivative) machine, you get such information directly on uprade!
"drop mod_muc_restrict_pm and mod_vcard_muc (not needed with Prosody 13)"
EDIT: Sorry, this version is not yet in #backports. Will be soon™!
I can't rule out, that there are anonymously run #Jabber servers, but is that really common?
Maybe the most popular server here in DE is #conversations.im and it has all relevant data published, incl. a #PrivacyPolicy: https://account.conversations.im/
Better not use a random server, but one recommended by @joinjabber https://joinjabber.org/docs/servers/ or @xmpp_providers https://providers.xmpp.net/#providers
The #XMPP Newsletter for March 2025 is out!
Read about the latest XMPP universe updates and the latest updates on our #standards!
https://xmpp.org/2025/04/the-xmpp-newsletter-march-2025/
Enjoy reading! 
#jabber #chat #interoperability #rtc
#opensource #decentralization
The #XMPP Newsletter for February 2025 is out!
Read about the latest XMPP universe updates and the latest updates on our #standards!
https://xmpp.org/2025/03/the-xmpp-newsletter-february-2025/
Enjoy reading!
#jabber #chat #interoperability #rtc
#opensource #decentralization
@AskSteve @sturmsucht @urbanprivacy @xmpp
Nichts gegen neue Chat-Apps. Aber ich bin seit ca. 2014 bei #Jabber (bevor es Signal oder Matrix gab bzw. mir bekannt gewesen wären) und es funktioniert gut. Mit gateways habe ich auch Zugang zu IRC und Matrix. Für einen Wechsel fehlt der Leidensdruck
Delta ist OK, aber es gibt noch keine native Linux-App, was mir sehr wichtig ist. Und (noch) keine Gateways zu IRC, Matrix, #XMPP, daher derzeit für mich nicht interessant.
#UnplugTrump, daher Signal in der Amazon Cloud von Jeff B., einem DJT-#Broligarchen? Vom Regen in die Traufe!
Threema ist dbzgl. besser, zumal es Users nicht zwingt, ihre Telefonnummer rauszurücken.
Aber #digitaleSouveränität bietet der Silo nicht, da man sich den Server nicht aussuchen kann, z.B. in der #EU oder #selfHosting.
Zum Glück gibt es seit 1999 einen Internet-Chat-#Standard, der freie Föderation erlaubt wie Email oder das #Fediverse.
Signal as an easy-to-use and probably more secure WA replacement? Sure.
But for #digitalSovereignty we should go for something really free and federated, just like the fediverse. There are various options, of course. Each with pros and cons attached.
(My personal favourite is #Jabber, which exists since 1999 and is extremely easy to use thanks to #Quicksy and its Indian cousin #Prav.)
In 3 days, the jabber.fr wiki, a niche specialized wiki with a lot of outdated info and only one or two occasional contributors at the moment, has served more than 200 000 pages to shitty LLM bots.
Our PHP and mariadb processes are constantly hammered by them, and most of them are masquerading as normal traffic with browser user agents.
Is there a better solution than blocking off entire countries and cloud provider subnets at the moment?
Le serveur jabber.fr a été brièvement indisponible pour une opération de maintenance il y a quelques minutes.
Plus de détails sur https://statut.jabberfr.org/
#Jabber #XMPP
>> 1. I don't want to use Google Android or Apple iOS. There is no first class client for Linux/#Debian/#Mobian.
Build one.
>> 2. I don't want to fuel the Amazon cloud of Jeff B., but prefer services in my home "country", the #EU.
Use #OpenStack or ask an EU provider to use it.
>> 3. I don't want to use a phone number for creating an account. E.g. it makes multi-account setups hard.
>> …grey beard, but I'll stay with #Jabber
How about #Mastodon? 
Just reading through the #xmpp / #jabber core specification bc I initially wanted to write an own jabber <-> matrix bridge (the ones that exist either dont work anymore, aren't maintained or didn't work with my usecase), and I seriously consider just scraping that idea.
It's even more awefull of an protocol than HTTP; no length-prefix of messages, malformed xml, and genneraly try-and-error mentality for most of the protocol.
