As a community, we often ask ourselves how to attract more users to #XMPP.
General Discussion
10
Posts
5
Posters
0
Views
-
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.
-
System moved this topic from Uncategorized on
-
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.
@daniel
I'm guessing there are complex problems in IM space that they don't realize they'll have to solve from scratch, which XMPP already solved for them.What are these 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.
@daniel I think people have never truly forgiven XMPP for being an XML based protocol.
-
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.
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.
-
@daniel I think people have never truly forgiven XMPP for being an XML based protocol.
@mariusor @daniel what would've been a better alternative?
https://www.process-one.net/blog/stop-telling-us-xmpp-should-use-json/
-
@daniel
I'm guessing there are complex problems in IM space that they don't realize they'll have to solve from scratch, which XMPP already solved for them.What are these problems?
@wolf480pl yes I think that is a huge part of the problem. It is very easy to completely underestimate the complexity of Instant Messaging. Sending a message from A to B seems like something every software developer can write before lunch and people don’t see how it can and will rapidly escalate from there.
But I don’t know how do communicate that to other people.
-
@mariusor @daniel what would've been a better alternative?
https://www.process-one.net/blog/stop-telling-us-xmpp-should-use-json/
@joshix based on what's popular today: JSON.
(I'm joking, my assumption is that they chose what was the best alternative at the time. As far as I know JSON hadn't been described by Crockford at Jabber's inception)
-
-
-
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.
@daniel@gultsch.social The Lemmy developers have added a user profile field where you can enter a Matrix account. It would certainly be better to also add a link to XMPP, and I believe this would be the most viable way to immediately achieve secure communication in the Fediverse.
However, it's always helpful for someone to try to "reinvent the wheel": diversity is a very prolific mother of solutions to problems that don't yet exist.
Gli ultimi otto messaggi ricevuti dalla Federazione
-
Our initial clients will be built in JavaScript, so you’d need to enable JS on your browser to use it (for now)
And, it will require special features on your server, so this won’t work on Mastodon (for now)
Download the road, things will change. We’re defining a standard API that anyone can build in. So hopefully someone can built installable clients (iOS, Android, desktop) that work separate from your browser.
-
@bonfire
How will this work for clients of servers with no JavaScript, like #snac2 and #honk? Well the server be doing the decryption as surely that breaks the point of it being "end-to-end"?
@swf @sovtechfund @benpate
-
@daniel@gultsch.social The Lemmy developers have added a user profile field where you can enter a Matrix account. It would certainly be better to also add a link to XMPP, and I believe this would be the most viable way to immediately achieve secure communication in the Fediverse.
However, it's always helpful for someone to try to "reinvent the wheel": diversity is a very prolific mother of solutions to problems that don't yet exist.
-
@julian said in New Fediverse features that actually aren't new:
> Don't forget NodeBB is also based off of groups! We've increased support for it in 2025 and it's continuing to be our core focus into 2026.No one familiar with the Fediverse can ignore it! In my opinion, NodeBB represents the most complete implementation of Activitypub groups today, adding the ergonomics of Lemmy and the versatility of Kbin to the great flexibility of Friendica!
NodeBB forum categories function as excellent Activitypub groups, perfectly compatible for Mastodon users.
Unfortunately, while users Lemmy/Piefed, Mbin, and Friendica can easily view NodeBB groups, Mastodon users lack a valid interface for managing groups, and almost no one is familiar with the Raccoon app, which is the only app that can recognize Activitypub groups and group discussions by topic.
For me, NodeBB was the best surprise in the Fediverse of this amazing 2025, and I thank the entire development team again for this wonderful gift!
-
Latest FOSS Academic post is -- you guessed it -- a 2025 year in review post. Thrill to the fact that I'm using much of the same FOSS to do my work as I always have! Feel the chills as I talk about #generativeAI and how terrible it is! Above all, join me in living the FOSS Academic Lifestyle Dream!
https://fossacademic.tech/2025/12/21/year-in-review.html
Replies to this post will appear as comments on the blog thanks to the magic of #ActivityPub!
-
@mariusor hey I haven’t published it yet, I’ll be doing so in the next couple of weeks
-
@django is the code available anywhere, I'd like to have a look if possible.
-
to be clear there are more issues than being able to represent an actor alongside a post
but the short version is that not having a proxyUrl endpoint means your client will hit CORS everywhere!
