Search

Items tagged with: XMPP


The XMPP Newsletter for December 2025 is out!

Read about the latest updates in the #XMPP universe and our #standards!
xmpp.org/2026/01/the-xmpp-news…

Enjoy reading! ☕

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


J'en ai eu marre de voir un ami galérer avec un client XMPP sur Mac…

Et bon je suis impulsif·ve vous le savez, donc comme j'adore le client Gajim, bah ça fait 4 semaines que je travaille sur le fait de pouvoir enfin utiliser Gajim sur MacOS, vous avez du le voir passer ici vu mes demandes en décembre :D

Et ça y est on a enfin des .dmg qui marchent bien et que vous pouvez tester en nightly ici :
gajim.org/download/#install-ma…

N'hésitez pas à nous faire vos retours sur le salon de Gajim !

#XMPP #MacOS


I’m getting a ton of spam on Mastodon. On the Jabber/XMPP side of things, we are doing a lot behind the scenes to combat it that regular users might not even notice.

I hope the people behind the scenes of Mastodon are working on similar things.

#Jabber #XMPP #Fediverse #Mastodon



Announcing Jabboratory, a partner collective of @joinjabber
Jabboratory aims to be for the people who already have an XMPP account and want to help improve XMPP and the Jabber network.

We use the same CoC as JoinJabber and all the same governance documents. All of them being by Vojkruco codeberg.org/Vojkruco/Cooperat… and we are hosted under the Vojkruco umbrella.

Some of the things we do are:
- specifications (called XCSPs in Jabboratory),
- developer help/documentation and implementation collaboration
- improve XMPP/Jabber network socially (safer spaces, blocklists, outreach, organizing events, pushing for a better non-tech culture, etc.)
or anything else that includes improving XMPP and Jabber network as a whole.

We aim for diversity of ideas, include people directly in all aspects of decision making (protocol, implementations, social, etc.) and build a space where people feel safe to talk, ask for help, bring up any kind of ideas and work with others to implement said ideas. By the community for the community with inclusive decision making to serve the people affected.

you are welcome to join our lounge room here -> invite.joinjabber.org/#lounge@…
It is strictly non-tech because we aim for inclusivity, but we do of course have other channels some of them being tech related🙂

We already have some implementations, servers, and XMPP collectives involved (including JoinJabber) and we are all building a better XMPP and Jabber network together 🙂

#xmpp #jabber #xml #SecureMessaging #decentralization #privacy #security #federated #jabboratory


Happy Jabber Day 🎂 🥳

On January 4, 1999, Jabber was first announced to the public¹.

Twenty-seven years later, Jabber—or XMPP, as it became known after standardization through the #IETF—remains the only truly vendor-independent, federated instant messaging platform.

In almost three decades, XMPP has never stopped evolving and remains our best tool for digital independence.

¹: tech.slashdot.org/article.pl?s…

#DigitalIndependenceDay #Jabber #XMPP #DiDit #DigitalSovereignty #DiDay #JabberDay


I think you are 100% correct on your assumption: it won't move the needle at all

But, personally, I fail to see how that's a good reason enough not to follow that path and drastically reduce the amount of metadata as any step on that direction can only bring beneficial results for the whole ecosystem regardless of the impact on the adoption rate.

As a matter of fact, at least 3 of the points you described on your technical details should probably be already implemented.

#XMPP #Jabber


I think #XMPP has a relatively clear and achievable path to drastically reduce the amount of metadata, but I’m increasingly worried that it is not going to move the needle in terms of adoption.

For 99.99% of people, the only relevant feature for an instant messenger is simply 'Are my friends using it?' The other 0.01% are equally divided between people who already use XMPP and don’t mind the metadata, and people who won’t use it anyway.

#Jabber #Conversations_im


#xmpp


It would be great if #xmpp community was better represented in various social networks. For example, there's no #conversations_im account in mastodon.



If you use a Mac computer with MacOS 14 (Sonoma), 15 (Sequoia) or 26 (Tahoe), you can maybe help me test Gajim (a cool XMPP client) for MacOS!

You can follow instructions on this page and then tell me if it's working (or not):
lithio.fr/gajim/

For now I can only build a x86_64 (Intel) dmg.

Boost can help understanding if a version built on MacOS 14 also work on MacOS 15 and 26 :D

Thanks for your help!

#MacOS #XMPP



я использовал #xmpp месяц,и ... #DeltaChat / #ArcaneChat лучшое что есть❤️🥛
я другие мессенджеры тоже тестировал #Session / #SimplexChat / #Signal ну такие себе,у каждого есть свои жёсткие минусы



What's the current state of XMPP and OpenID Connect? My web search returned that ejabberd is still considering if and how to implement and Prosody has experimental alpha-stage support via a module. I couldn't find anything conclusive in regards to XMPP clients. What's with Gajim(?) and Conversations? Or other clients? Are there any web clients supporting OIDC?

#jabber #xmpp #oidc #openidconnect




#xmpp


The #XMPP assembly at #39C3 is live!
Come find us in the Critical Decentralization Cluster in the corner of hall H!

We also have a phone reachable at 45816.


Same with Signal. I can't write anything remotely viral on #XMPP without some self proclaimed security expert stepping up to explain to me how much better Signal is.

I'm afraid that's just how the Fediverse works.

And since you seem to be advocating primarily for Signal you get to experience the XMPP fan boys and I get to enjoy the 'security experts'.

#xmpp


Ich habe den Eindruck, dass Matrix weitaus problemloser läuft als XMPP.

Bei XMPP kann sich nicht jeder Client an jedem Server anmelden (ich habe diverse Clients und Server, nicht nur meinen eigenen mit ejabberd, getestet). Und auch die Kommunikation zwischen zwei Accounts funktioniert manchmal gar nicht, manchmal nur in eine Richtung und irgendwie nur selten problemlos. Auch da wieder stark abhängig vom Client.

Ein Problem mit meinem Server mag sein, dass er unter einer Subdomain (xmpp.example.com) läuft. Ich mutmaße, dass nicht jeder Server bzw. Client damit zurechtkommt. Zwischen meinem Server und dem von Mailbox.org klappt jedenfalls gar nichts. Aber ich habe noch nicht einmal eine Möglichkeit gefunden, für Mailbox.org einen andeten Client als deren Web-Client zu verwenden. Ich glaube fast, die sind nur zu sich selbst kompatibel.

Manche sagen freilich auch, dass ejabberd recht eigenwillig sei.

Mit Matrix hingegen hatte ich bisher keine Probleme (auch da habe ich einen eigenen Server am Start).

#Matrix #XMPP #Jabber #ejabberd





#XMPP is still a thriving ecosystem with lots of good FOSS developers doing interesting things.

XMPP is also used under the hood in tons of products needing instant messaging even if they are not advertised as XMPP clients, or do not federate.

Anyway, XMPP and #matrix all share a strong focus on protocols, but there is a big difference: chatmail.at does not expose protocols to client developers, just a Rust SDK.


> My question is rather: How can #XMPP market itself better to people who want to build instant messaging solutions.

my humble opinion: I would still pick #deltachat / chatmail core to build my client if I had to start from scratch today, with #xmpp I just have a protocol, with delta chat I don't actually need to use the #email protocol at all, only the core library that takes care of dealing with networking and #encryption while all I have to do is to create the UI


well it depends on the context, I am Cuban, that Delta Chat used email was the whole point I started using it and contributing, besides cheaper data plan for national email, you see down there in the 3rd world on an unstable 2g connection at 1kb/s #email, asynchronity and offline-first comes on top of #xmpp which together with #Telegram really struggles to even get connected, in a fast hyperconnected 1st world this might be less relevant until some emergency times or in isolated areas


The big plus of #DeltaChat is that the infrastructure is already there. Infrastructure is a big part of the problem. And obviously using mail for that is only for people born before 2000.

Second is branding: When people hear #XMPP they hear 20 years of failure of implementing robust solutions both server-side and client-side. People just don't know that after 20 years there now are server and client solutions really working.


I have a lot of respect for #DeltaChat (@delta); By all accounts they provide a good looking client and a homogenize experience across platforms. Users absolutely don’t need to care about the underlying protocol!

However there is no way, shape or form in that IMAP+Submission is a more suitable stack for instant messaging than #XMPP.


I consider this a failure on our part but I don’t really know what to do about it. Most arguments against #XMPP don’t hold if you’re building from scratch anyway:

• #Conversations_im looks very outdated: OK, but you are developing your own clients anyway.

• XMPP doesn’t have an SDK: Neither does your #ActivityPub or email stack

• OMEMO is insecure and I would prefer #MLS: Yes, let’s work on that together and you’ll still benefit from XMPP’s 100+ solved IM problems.


As a community, we often ask ourselves how to attract more users to #XMPP. Yet the real tragedy is that people would rather build something entirely new (loosely based on email or #ActivityPub) than consider XMPP. Need end-to-end encryption by default? If compatibility with existing XMPP clients is a secondary concern, you can implement it in your own solution while still benefiting from our two decades of experience in instant messaging.


Do we have an XMPP chat yet for people going to be at #39c3?

#XMPP


#XMPP Community

The XMPP assembly for the #Chaos #Communication #Congress #39C3 in #Hamburg has been confirmed! The space is inside the Critical #Decentralization Cluster habitat.

xmpp.org/2025/12/xmpp-at-chaos…

#ccc #chat #messaging #jabber #standards #opensource
#interoperability #operators