@eliocamp #xmpp just works

New version of ejabberd is out (26.02). Wrt to `mod_invites` it contains a whole bunch of accessibility improvements for the landing page. Feedback more than welcome!

https://github.com/processone/ejabberd/releases/tag/26.02

#ejabberd #xmpp #greatInvitations #nlnet

Nice! The #XMPP logo is now officially part of Font-Awesome. 🎉

https://fontawesome.com/icons/xmpp?f=brands&s=solid

@Tamtam

While #Jabber/#XMPP has not the same #confidentiality as Signal (e.g. more meta data is stored on the server; and current #OMEMO 1 is not as good as, OMEMO 2, which unfortunately is not widely implemented), but it's close enough for me.

The advantages of #federation and #digitalSovereignty outweight those minor problems. YMMV.

Moxie Marlinspikes:"One of the controversial things we did with Signal early on was to build it as an unfederated service. Nothing about any of the protocols we’ve developed requires centralization; it’s entirely possible to build a federated Signal Protocol-based messenger, but I no longer believe that it is possible to build a competitive federated messenger at all."
So after reading this I thought, well, everything that we like about signal can be turned into a federated messenger. Why is nobody doing it?
I gave me at least a little bit of hope that someone or, some group will.
I believe the need for privacy is getting more urgent by the minute.. The situation has changed quite a bit, since that decision at signals was made. We need a signal -quality messenger as part of the fediverse
#Signal #matrix #xmpp #privacy #security #opensource #fediverse

@Oldine @Wiebke_Worm

Beides jedoch auch zentrale Lösungen. D.h. man hat hier auch eine Abhängigkeit zu einem Unternehmen / Organisation.

Es gibt auch dezentrale Lösungen, ähnlich wie hier und wie man es von E-Mail kennt.

Hier mal ein Beispiel zum einlesen:
https://anoxinon.media/blog/xmpp1/

#XMPP #jabber

It’s been almost a decade since I wrote a blog post on the State of Mobile XMPP in 2016. Time to start working on an update.

The situation has only improved since then, and #XMPP has matured into a solid, feature-rich protocol for federated instant messaging

https://gultsch.de/posts/the-state-of-mobile-xmpp-in-2016/

Nice, https://compliance.conversations.im/test/xep0485/ is now testing for XEP-0485: PubSub Server Information. That’s gonna boost adoption, I hope. Thanks @daniel, I suppose!

@guusdk

#xmpp

Monal 6.4.18 (Build 1077, PR #1555) released.

To see the complete list of bugfixes and improvements, check our releases page: https://github.com/monal-im/Monal/releases/tag/Build_iOS_1077

#Monal #ios #macos #xmpp #im #chat #messaging

#XMPP Community

Join the XMPP #Berlin #Sprint from 19th to 21st of June 2026.
Work side by side with developers from the XMPP community!

More information and registration here: https://wiki.xmpp.org/web/Sprints/2026-06_Berlin

#jabber #chat #interoperability #rtc #opensource #federation #messaging #Germany #development

Alt...

The XMPP Community Banner with the XMPP Logo and a triangle with three encircled colored person icons next to it.

XMPP Extensions and Specifications (XEP)

Read about the new #XMPP #Extensions and #Specifications changes and updates in January 2026:

https://xmpp.org/2026/02/the-xmpp-newsletter-january-2026/#extensions-and-specifications

#jabber #chat #interoperability #rtc #xep #standards #opensource #decentralization #federation #messaging #newsletter

Alt...

The XMPP Specs Banner

The XMPP Newsletter for January 2026 is out!

Read about the latest updates in the #XMPP universe and our #standards!

https://xmpp.org/2026/02/the-xmpp-newsletter-january-2026/

Enjoy reading! ☕

#jabber #chat #interoperability #rtc #opensource #decentralization #federation #messaging #newsletter #xep

Alt...

The XMPP Newsletter Banner

An #XMPP sprint has just been announced for June 2026 in the Berlin offices of Wikimedia Germany. I will definitely put that on my calendar. Last year was great fun. Thank you @debacle.

https://wiki.xmpp.org/web/Sprints/2026-06_Berlin

@Oleksii @danish_akhtar7

For A/V calls, #XMPP itself does the signalling, while the payload is going either directly from device to device, or, if one or multiple clients are behind firewall/NAT, a TURN server is used.

Most public servers should do that. Check on https://compliance.conversations.im/ if XEP-0215 is supported by your server.

Btw. which clients have you tried?

@danish_akhtar7

I never tried Signal or Whatsapp, but I'm on free and federated #Jabber/#XMPP since 2014. I came late to the party — Jabber exists since 1999. At some point, Google chat federated with Jabber, but they stopped it, because #BigTech does bigtech things.

Bridges from Jabber to Whatsapp and Signal do exist, i.e. #slidge, but because WA and Signal are anti-federation, the bridge can only work, if one has an account on WA/Signal 😞

Anyway, all friends and family are on Jabber now.

What I love about #Conversations_im as a #UnifiedPush distributor—aside from #XMPP being a reliable, secure, and efficient protocol—is that it comes with a healthy dose of decentralization.

Sure, you can technically self-host a Sunup instance, but will you? XMPP already offers thousands of providers out of the box.