fennell.dev is a Fediverse instance that uses the ActivityPub protocol. In other words, users at this host can communicate with people that use software like Mastodon, Pleroma, Friendica, etc. all around the world.
This server runs the snac software and there is no automatic sign-up process.
@jwildeboer 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'.
@jwildeboer
Just a serious, genuine question: with the fragmentation of #InstantMessenger alternatives what program do you suggest? #xmpp, #deltachat, #simplex, #Matrix #jami #Briar
There are more options:
https://mov.im/blog/debacle/76bf90a4-5f59-4962-92db-6cd859f42ec9
I'll stick with #Jabber/#XMPP, because I'm used to it and there are bridges to IRC, Matrix, SMS.
Dear friends,
Wishing you all Merry Christmas and hopefully, happy holidays. Hope you get time to unwind, relax and spend time with your loved ones.
Our Hetzner server's bill, hosting Diasp.in, Durare.org and Poddery.com XMPP services for October and November 2025 is - €8.94 (~ ₹949). These are public services, maintained by volunteers and sustained on donations by people like you. Please help us by either sponsoring this expense or a part of it.
Continued...
Automatically finding other #prav users is a core feature of @prav but in the last update this functionality was broken. We missed this during testing of the update.
I just added 2000 rupees to the bounty - we will give the money raised to anyone who fixes the issues.
Would you consider increasing the bounty? Small amounts are ok too.
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).
Ich habe mich damit abgefunden, daß ich kaum Einfluss auf mein Gegenüber habe, sondern nur für mich entscheiden kann.
Ich bin per #Jabber, Email, Festnetztelefon, Postkarte und persönlichem Besuch erreichbar, also im Prinzip alles ohne Bigtech möglich. Signal wäre mir schon zu viel Bigtech.
Aber ob die Leute z.B. alles von einem mitlesenden Bigtech-LLM korrekturlesen lassen oder #XMPP bei Azure hosten will ich gar nicht wissen. Da endet meine Verantwortung 🤷
🇬🇧 ANNOUNCEMENT
I am happy to announce that XMPP/AP Bridge is fully published now!
Chat between the Fediverse and XMPP from your usual account and application! Nothing to install, nothing to configure, it just works...
Full documentation in 7 languages:
https://chat.gayfr.online/blog/ap_bridge%40gayfr.live/xmpp-activitypub-bridge-documentation-KdpNJ9
Open sourced to install it yourself if you want: https://github.com/Barbapulpe/xmpp-ap-bridge
Try it out as our version is open to all: follow @xmpp_bridge from the Fediverse to start out.
🔄 Boost so we may promote open source and open protocols for a better and more ethical internet!
🇬🇧 XMPP/AP Bridge NEW RELEASE
Version v0.7.0 has just been published, it brings additional moderation capabilities.
Check it out!
https://github.com/Barbapulpe/xmpp-ap-bridge
XMPP/AP Bridge allows you to chat between the Fediverse and XMPP from your usual account and application! Nothing to install, nothing to configure, it just works...
If you want to try it out, our instance is open to all: follow @xmpp_bridge from the Fediverse to start out.
🇬🇧 XMPP/AP Bridge NEW RELEASE
Version v0.7.1 has just been published, bringing some enhancements.
Check it out!
https://github.com/Barbapulpe/xmpp-ap-bridge
XMPP/AP Bridge allows you to chat between the Fediverse and XMPP from your usual account and application! Nothing to install, nothing to configure, it just works...
If you want to try it out, our instance is open to all: follow @xmpp_bridge from the Fediverse to start out.
🇬🇧 XMPP/AP Bridge NEW RELEASE
Version v0.7.2 has just been published, with a bugfix in messages parsing.
Check it out!
https://github.com/Barbapulpe/xmpp-ap-bridge
XMPP/AP Bridge allows you to chat between the Fediverse and XMPP from your usual account and application! Nothing to install, nothing to configure, it just works...
If you want to try it out, our instance is open to all: follow @xmpp_bridge from the Fediverse to start out.
🇬🇧 XMPP/AP Bridge NEW RELEASE
Version v0.7.3 has just been published, updating libraries and dependencies.
Check it out!
https://github.com/Barbapulpe/xmpp-ap-bridge
XMPP/AP Bridge allows you to chat between the Fediverse and XMPP from your usual account and application! Nothing to install, nothing to configure, it just works...
If you want to try it out, our instance is open to all: follow @xmpp_bridge from the Fediverse to start out.
🇬🇧 XMPP/AP Bridge NEW RELEASE
Version v0.7.4 has just been published.
Check it out!
https://github.com/Barbapulpe/xmpp-ap-bridge
XMPP/AP Bridge allows you to chat between the Fediverse and XMPP from your usual account and application! Nothing to install, nothing to configure, it just works...
If you want to try it out, our instance is open to all: follow @xmpp_bridge from the Fediverse to start out.
"Im Umfeld von #Wuseltronik entstand unter anderem die Firma #Kosonanz, die später den Windmessbereich von Wuseltronik übernahm und unter dem Namen #Ammonit Measurement GmbH bis heute weiterbesteht." (#Wikipedia)
Ammonit sitzt in #Berlin-#Kreuzberg und nutzt recht viel #freieSoftware. Und versucht, diese auch zu unterstützen, z.B. Spenden für #DebConf (#Debian), #XMPP-Sprints und hoffentlich bald einer Fördermitgliedschaft bei @Codeberg.
Disclaimer: Bin bei dem Laden 🙂
I’m happy to announce the 12th annual Holiday season Conversations giveaway. 🎄☃️
The federated instant messaging client is now available for free on Google Play until New Year’s Eve. 🧨🎆
Merry Christmas, Happy Holidays. Enjoy #39C3.
https://play.google.com/store/apps/details?id=eu.siacs.conversations
#XMPP #Jabber #Conversations_im #DigitalSovereignty #Fediverse
Monal 6.4.15 (Build 1067, PR #1521) released.
To see the complete list of bugfixes and improvements, check our releases page: https://github.com/monal-im/Monal/releases/tag/Build_iOS_1067
It's not me: it's you!
No, I'm not giving you my phone number nor my email. Your mobile is chock full of apps that harvest every bit of personal data they find in it and keep them to themselves to do who knows what, sell it to the best bidder and even do things I can't imagine. You may not care about your #privacy but I do care about mine. So, you are not getting my phone number even if you want to have my contact on #Signal.
Want to stay in touch? I can give you my #XMPP address though.
"Sharing is caring" said #Whatsapp .. then took all the details from every contact in your contacts list and left ... never to be seen again ... or give you anything in return ...
@lazarus @daniel #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. But look at #Matrix, only 25% of matrix servers federate.
Anyway, all three share a strong focus on protocols, but there is a big difference: https://chatmail.at does not expose protocols to client developers, just a Rust SDK.
So, I have a long-term vision. I want to marry my mobilizon instance (AP) with XMPP.
Each account should also be an XMPP account under the same domain. For this authentication needs to be changed to the style the Fediverse does it. Plus support for 2FA. (XEPs might exist but clients don’t support it that way - maybe oAuth, not widely supported either).
1/2
@duncan_bayne Same mix of surprise and frustration here! I've been unhappy about #Mattermost's behaviour on mobile for a while (extremely slow, no matter how I tweaked the server config) so I guess this is just the final straw for me.
My ideal solution would be #XMPP-based - I know how to set up a server pretty easily already - but I'm not sure whether typical XMPP clients would support similar workflows/UIs as Mattermost/Slack/..., i.e. typical team collaboration workflows. I'll see...
@kris Thank you for mentioning #Prose, it looks pretty cool!
Although I notice a 20-user limit on the community edition?
Honestly this sounds a bit like the #Mattermost nonsense. I'd expect "as many users as your server/hardware can take", instead?
I wonder how far a vanilla #Prosody installation would take me in terms of UX and team workflow... that would seem like the safest, zero vendor-locking option.
Right now IMHO the client that needs desperately the most investment in time and COMMUNITY engineering effort is Conversations.im .
Monocles for example, need someone to implement OMEMO to WebXDC which is the uniquely interesting feature of DeltaChat. Pixelsocial is incredible for in-group private rolls (could literally take the power away from neighbourhood/thematic facebook groups).
Give her a hand! https://codeberg.org/monocles/monocles_chat/issues/353
I'd be happy as fuck to help any of this projects if they were using Kotlin Multiplatform or the RFCs of XMPP were as understandable as NIPs, but they arent
My partner (du-jour) struggles to configure Conversations because there's no Spanish translations of it. He can't disable its nofications on his watch because of this.
And I would be happy using Monocles if WebXDC worked without cumbersome steps in between (read the issue before this toot). I can follow those steps with @surfhosting because we're tech saavy, but most of humanity isn't. Hence they need Whatsapp simplicity.
UX rule number 1 = if users need a manual you've failed. This is pretty much the reason Apple refries tech better. They are a UX-centred company. It's also why it bores power-users.
RE: https://gultsch.social/@daniel/115751087451745641
1. Rivaling clients to Whatsapp.
2. Incredible simplification, people don't want, cannot afford to learn what OMEMO is, "this message has been encoded for another device" is a humongous UX failure.
3. Consistency among clients.
4. Consistent "send voice message" button, consisten "send short video" button, consistent "send live location" button. Go to reason 1.
5. Less FOSS now, paid later projects. Why are most free on F-droid and paid-for in Google Playstore?
6. An iOS client that doesn't look as ugly as Shrek doing yoga.
7. Clip button should only be for attachments, not for everything (Conversations)
8. Stick to a name either Jabber or XMPP, not both. It's confusing.
9. Make people aware of how many things are Jabber in disguise (Whatsapp, Grindr, Google Hangouts, etc) with a corporation behind monetising it using the people as the product.
10. Incentives for running servers. In Mastondon we're really good at justifying donating to our admins when they run a decent service.
11. RFCs or XEPs written as easy to read an implement as NIPs.
12. Attached directories. XMPP is directoryless same as email, what about searching people by their Mastodon handle, by their email handle, use WebFinger.
> 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
@daniel 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
@daniel 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.
@arcanechat @delta I’m not 'blaming' Delta Chat for making the wrong choice. And you in particular probably weren’t even around back then.
My question is rather: How can #XMPP market itself better to people who want to build instant messaging solutions.
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.
@bonfire @swf @sovtechfund @benpate Ooof, just another instant messenger..?
We've already had XMPP since the 90s... and since then it's become pretty reliable.
i hope there'll at least be interoperability. I'm so tired of new ways to communicate that are not interoperable with what's already there.
#XMPP Community
User & developers are spread #world-wide in the XMPP community!
This is a call to show where you are! 🌍🌎🌏
Post a photo with the XMPP #logo and a nice view of your location 📷
Add city name and country, too.
#jabber #chat #rtc #standards #decentralization #federation #messaging
The @dino and #Conversations_im developers have a booth at @FrOSCon. Come find us to talk about #XMPP and grab some merch.
Gajim 2.3.4 has been released! 🥳
This release supports time zones 🕑 in profiles, adds drag and drop improvements, enables displaying long messages inline, and fixes many smaller issues.
Thank you for all your contributions ❤️ Let us know what you think!
Support Gajim's development: https://liberapay.com/Gajim