Snikket is a new XMPP/Jabber-based decentralised FOSS messenger service. You can follow at:

➡️ @snikket_im

The official website is

It aims to make XMPP into a more viable alternative to Whatsapp etc by providing consistency in design and terminology.

(It's sort of how Mastodon made ActivityPub more mainstream, by using consistency to make it clear the instances are part of one network.)

#Snikket #XMPP #Jabber #Messaging #Messenger #WhatsApp #IM #FOSS #SelfHosting

@FediFollows @snikket_im Interesting! How does it differ from Matrix, is there any showcase comparison for two?


They're the same architecture, but XMPP uses an extensible XML communication while Matrix uses an extensible JSON.
As far as I can tell, they're intended to do the same thing but are just implemented with different technologies.

I should also point out that there's a pretty well known Matrix-to-XMPP bridge called Bifrost (though I can't speak to it's quality or compatibility between surface-similar features)

@aaravchen Thanks, makes more sense now. Is there any inherent benefit to XML that would justify this development?

@vazub @aaravchen The big advantage of XML that XMPP uses extensively is its concept of "namespaces".

By using namespaces it's possible to extend and evolve the protocol over time, while maintaining backwards compatibility (as long as you want to). XMPP is 20 years old (!) and would be totally irrelevant now if it didn't have the ability to adapt to new technology and communication styles.

@vazub @aaravchen
The core XMPP protocol was standardized at the IETF (the organization that develops and maintains many internet protocols such as HTTP and email) in 2004 and updated in 2011. But most of the protocol changes happen through documented extensions known as "XEPs".

New extensions are developed by the community and published at

Due to XML namespaces, these extensions don't break existing software when they start getting used on the XMPP network.

@vazub @aaravchen

To avoid chaos and confusion, each year updated guidance is published about which XEPs should be implemented by e.g. IM clients:

The whole process is managed by the XMPP Standards Foundation (XSF), which is governed by community members:

This was so much more helpful than my 2 hours of trying to detangle the contentious arguments from biased enthusiasts' posts.

@mattj @vazub @aaravchen Matrix has the same concept of namespacing in JSON, though, so in the end it really doesn’t matter much.

@js @mattj @aaravchen That is what I am afraid of. The biggest challenge for me is to pitch the use of alternative messengers to my friends, and having virtually similar solutions to the same issue is a tough sell in terms of what option to suggest.

@vazub @mattj @aaravchen The Matrix experience is a lot more polished, since Matrix was designed for connection-less from the start, which works better for mobile, especially iOS. XMPP has extensions to work around XMPP being connection oriented, but that still has many problems in practice and the Matrix experience is a lot more polished. Configuring push notifications is done Server side in Matrix and works well and a huge pain point in XMPP, so MUCs + Mobile aren’t fun.

@vazub @mattj @aaravchen Also the client landscape on iOS for XMPP is pretty bad. Recommending XMPP right now to an iOS user is a way to make sure they won’t try it again in the future and might be averse to trying any other messengers you might recommend in the future.

Sign in to participate in the conversation

Fosstodon is an English speaking Mastodon instance that is open to anyone who is interested in technology; particularly free & open source software.