Replied in thread
@dino Nice. Calls working or me again on #postmarketOS with #Librem5. Call icon no longer greyed out.
Recent searches
Search options
#jabber
1 post1 participant0 posts today
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.
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
Replied in thread
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?
#XSF Announcement
Today the #XMPP Standards Foundation publishes an Open Letter to urge #Meta to adopt XMPP for messaging #interoperability.
It’s time for real interoperability. Let’s make it happen.
https://xmpp.org/announcements/open-letter-meta-dma/
#jabber #chat #rtc
#opensource #decentralization #standard #dma
После 17-18 лет использования #Jabber, кажется, решил совсем с ним распрощаться. Может показаться, что совсем не вовремя на фоне блокировок #Telegram (пока в Чечне и Дагестане официально, кстати, не пользуюсь им последние года 4 и не планирую в него возвращаться) и #WhatsApp (в перспективе: в декабре 2024 он был добавлен в "лист ожидания" #Роскомнадзора), но помимо DeltaChat (и ужасных клиентов #matrix для #Android) подыскалась вполне годная альтернатива в виде #Signal Messenger.
Хоть он и заблокирован на территории РФ, комфортно пользоваться им вполне реально: https://tinyurl.com/signal-in-russia (мануал в .txt, 7kB). Более того, создали и группу для его тестирования (её адрес есть по ссылке выше). Выглядит на #Андроиде примерно так (и тел.номера там друг другу можно не светить):
Replied in thread
On my OS, #Debian, there are various Matrix clients. #EmentEl is probably the best, but because I use #Jabber more than Matrix, I have a #slidge matridge bridge from #XMPP and use #Gajim as my one-stop client.
Element (with or w/o X) is not in Debian and after almost eight years, I doubt to see it anytime soon.
bugs.debian.org#866502 - RFP: element-web -- web-based matrix client - Debian Bug report logs
If you're still recommending #Signal, you may have missed the tech oligarchs' takeover of the US government. The best time to recommend European alternatives was 8 years ago; the second best is now.
Replied in thread
Absolutely nobody knows what an XMPP address is, so just go ahead and call it a:
European Parliament #security advice after #China hacked #US infrastructure: Use plaintext #Microsoft Teams and only use encrypted @signalapp if Teams is unavailable. 
Politico: "Parliament’s email reminded lawmakers they should use (...) Teams and #Jabber when possible and only #Signal if the two are unavailable."
“The use of Signal is proposed as a safe alternative in cases where no equivalent corporate tool is available,” the Parliament’s press service said in a statement.
#XSF Summit 27
We published a small summary on XMPP Summit 27 with reference to more details from @alex !
https://xmpp.org/2025/02/xmpp-summit-27-report/
#jabber #chat #interoperability #rtc
#opensource #decentralization #standard
The #XMPP Newsletter for January 2024 is out!
Read about the latest XMPP universe updates and the latest updates on our #standards!
https://xmpp.org/2025/02/the-xmpp-newsletter-january-2025/
Enjoy reading!
#jabber #chat #interoperability #rtc
#opensource #decentralization
It’s incredibly sad that we’ve lost the open, federated team chat space to #Matrix—where the only viable server isn’t open source, it’s debatable whether the underlying standard is truly open, and the most charitable thing I’ve heard about the UX is that it’s 'OK.'
Replied in thread
Yes: One adhoc MUC for one ticket, accessible by the customer from the web UI (maybe using #ConverseJS by @jcbrand), while support staff can use their #Jabber client of choice. Not trivial though, e.g.
- chat logs must be attached to the ticket and searchable (#elasticSearch)
- MUCs must not be accessible by other customers
- invitation of support staff must be "generic", i.e. not to specific JID, but to everyone doing support and is on duty, first one in queue is in
Replied in thread
At $WORK we use #Zammad by @zammad_hq. They provide a .deb package, but it is unfortunately not packaged in #Debian itself. We run it in a #bookworm container.
(The only missing feature for us (but not important enough to fund it) were integration into an #XMPP based support chat system, as we already use #Jabber and it would be nice to able to use our existing clients and accounts.)