devlug.de 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.
Quietly slipped in today: the XSF has published a new XEP - XEP-0512 - which I had the pleasure of authoring.
It's a small step, but one that opens up some interesting directions for #XMPP implementations. Curious to see where people take it from here.
As an aficionado of #tango #dance, music, and lyrics, and also a die-hard #Jabber user, I'm happy about this new #XMPP #standard of today:
XEP-0512: XMPP as Interpretive Dance
https://xmpp.org/extensions/xep-0512.html
I do, however, feel the need for a #protocol #bridge, as the #XEP relies on 4/4, while tango is, as everybody knows, 2/4 (el famoso "dos por cuatro"). Time for #slidge "slango" or "tangidge" maybe?
Actually, even if you don’t care about #UnifiedPush, having this minimal #Prosody server that just accepts messages via a simple REST API and sends them out via #XMPP is great alternative to the various sendxmpp scripts out there.
"Unlike other secure messaging solutions, qTox does not require you to be a computer programmer to use it."
Because #Jabber/#XMPP would require a CS master degree? 🤦 Most of my non-techie friends and even the elderly of my family use it without problems.
Anyway, added qTox to my IM chart 🙂
https://mov.im/blog/debacle/76bf90a4-5f59-4962-92db-6cd859f42ec9
Even with your proposal, a #Jabber client still can just ignore the name in the message and do whatever they want 🤷
I assume, that it depends on the clients DB structure.
Do I have only a simple JID ⇒ nickname table?
Or is it a more complex (JID, datetime) ⇒ nickname table?
Or do I even attach the nickname to every single message?
Changing the #XMPProtocol wouldn't help much.
How hard is it to propose an #XMPP XEP?
Right now it seems name changes are applied retroactively to past messages, or at least Gajim does it that way. This means we can't use our display name to indicate who is talking.
@skyweird::gryphon says that didn't used to be the case when they were using XMPP back in the day? Which means someone came along and fucking changed the semantics of namechanges out from under everyone? (Which by the way, over in Matrix land they're trying to do /exactly/ that. There's a setting to retroactively apply name changes in Element now. It's /on by default/ IIRC. I bet one day they'll remove it.)
We need a way to embed your name into the message itself. That embedded name overrides whatever your global/per-room display name is. Singlets can leave it off and have their retroactive name changes; we can enforce actually seeing our names like they should be.
(Of course it's possible to infer the correct name from the chat history, which is what clients did before, but that's only reliable as long as some jackass doesn't come along and change the semantics out from under you, nuking the names on years of chat history... embedding the name would be a very clear signal "HEY, KEEP THIS NAME".)
I could write up a spec myself if that'd be helpful!
Gajim 2.4.5 has been released! 🎉
Gajim now lets you know when somebody reacted to one of your messages 👍 😎
It also comes with automatic timezone updates ⌚ and improvements for macOS, and bugfixes
Thank you for all your contributions ❤️ Let us know what you think!
Support Gajim's development: https://liberapay.com/Gajim
You might like to take a look into #Movim by @movim, if you are interested in the combination of secure chat, public chats, blogging, A/V calls etc.
I looked at Briar some years ago, because I was interested in packaging it for #Debian. IIRC, the protocol wasn't formally documented, so that people could implement it in the programming language of choice, like it is for #XMPP, Matrix etc. Only a Java reference implementation to copy from. I hope, it's better nowadays.
Our combined booth for #UnifiedPush and #XMPP at #CLT2026 went great. There was huge interest in UnifiedPush, and we successfully funneled some of that interest into XMPP as well.
I think it's a great combination since those projects are ideologically well-aligned, and we will likely do it again.
Matrix started around the time, when I started using #Jabber/#XMPP ≈ 2014. Jabber was not very good back then. Message loss was common, maybe because "XEP-0198: #StreamManagement" wasn't (correctly) implemented in (mobile) clients.
That's not an issue anymore, but that, together with loads of VC money for their pretty good marketing and a modern looking client ("Riot") gave them a temporary advantage over Jabber.
@xmpp_providers
My XMPP server, chat.between-us.online, fell off the Category A list about a week ago, and the reasons I see each day are inconsistent. I also can no longer connect with chat.xmpp-providers.org. I get "Could not authenticate remote servers". Other than this, my server seems to have no problems connecting to any other server, as far as I can tell.
It seems to have happened coincident with getting updated Let's Encrypt certificates.
Let's Encrypt no longer creates dual-use certificates; they dropped ClientAuth from their certificates. I tried switching to ZeroSSL certificates, but they too have dropped ClientAuth.
Is the certificate change coincidental, or do you know if there's another explanation?
If it is the certificates, what do I do? Prosody does not yet have an ability to serve different certificates for inbound and outbound server connections, and so I cannot present a certificate with ClientAuth any longer.
🚀 Snikket Chat. Einfach, sicher und privat.
In meinem neuen Video zeige ich euch, wie ihr mit Snikket in wenigen Minuten einen sicheren und einfach zu bedienenden Messenger installiert. Basierend auf dem etablierten XMPP-Standard und mit integrierter Verschlüsselung sind eure Nachrichten wirklich sicher.
Installiere dir noch heute die Android-App aus F-Droid und verbinde dich mit unserer Community.
Still waiting for our ISP to get their issues solved ... meanwhile https://web.archive.org/web/20260215113226/https://cyberdelia.com.ar/isp-nightmares.html
So, the past few days we focused on fixing numerous bugs in Movim with many fixes in Multi-participants calls and general presences handling.
We're slowly getting closer to a proper release, stay tuned ✨
And if you wan't to help us making Movim the best Free Software, decentralized web platform: https://movim.eu/#fund ♥️
We are at Chemnitzer Linux Tage with a stand for #XMPP and #UnifiedPush.
Come find us and talk to us or grab some stickers or Haribo.
What's a good #xmpp app for apple iphone?
I'm using #conversations_im on android, but want to add someone on my server who exists in the apple world
Buem, para terminar la semana, nuestro ISP esta teniendo problemas en la zona, asi que #cyberdelia y nuestros servicios #XMPP y #Mumble estan offline hasta que los vuelvan a conectar con la civilización.
I'm testing #xmpp with #snikket today. It was straight forward to install the server. Like 10minutes. I was very impressed!!
But then the problem started… with #encryption key managment problem.
Basically I wanted to write to a #quicksy user (aka myself) and that didn't work because of some 'Aucun appareil pour qui chiffrer ce message n'a été trouvé. Recherche d'appareils en cours…'
I know that there is a lot of work to improve the situation. I'm open to report bugs, but I have no idea if it should be done in snikket, quicksy, gajim, kaidan …
That's two issues: One is #security (Signal is good regarding #confidentiality and #integrity, but not necessarily #availability) and the other #digitalSovereignty, which calls for #federation.
My comment was about the chart by @AliceStollmeyer, titled "take back control". Signal is partially controlled by AWS, i.e. they can switch it off.
Not mentioning #Jabber/#XMPP among secure messaging apps is wrong, of course 🙂 Just don't take that site serious.
https://framapiaf.org/@debacle/115804383499425330
You like Signal for it's outstanding #confidentiality? Fine!
You like Threema, since it's safe, it's from #Switzerland, and #ElsbethSigmund as #Heidi was your #childhoodCrush? Great!
You like Whatsapp, because your friends are there? I don't blame you!
But 𝐩𝐥𝐞𝐚𝐬𝐞 don't claim, that any of those #centralServices would support #digitalAutonomy, #digitalIndependence, #digitalSovereignty. They have their merits, but they still are #walledGardens.
Suggesting federated apps, like Lemmy, Mastodon, Pixelfed, Friendica, Peertube, and Loops for more #digitalSovereignty makes sense. Not only for the #EU, but for every country or #NGO.
Mentioning Signal, however, does not help. It's a centralized service on the Amazon cloud, also depending on Google. If DJT wants to shut it down, it's gone in a second.
Bettter suggest federated chat, like #Jabber/#XMPP. It's the fediverse of chat since 1999 🙂
JabberFR sera présent en tant que stand aux @jdll cette année les 30 et 31 mai de 10h à 18h à l’ENS de Lyon !
N’hésitez pas à passer nous voir si vous voulez discuter de messagerie instantanée libre, fédérée, extensible et légère, adhérer à l'association, ou encore être bénévole sur le stand.
I released yesterday version 0.16 of Poezio, a terminal XMPP client, here is the blog post with a release announcement: https://blog.mathieui.net/poezio-0-16.html
Some nice bugfixes (thanks @ge0rg for testing), and finally handling of message moderation & retraction.
Note: the fact that we very often share version numbers with @profanity is a pure coincidence!
With the help of the Prosody channel (specifically MattJ), I finally fixed sending XMPP messages from Home Assistant.
The trick was adding and configuring https://modules.prosody.im/mod_muc_bot.html properly:
Component "muc.example.com" "muc"
modules_enabled = { [...], "muc_bot"}
known_bots = { "homeassistant@example.com" }
bots_get_messages = false
ignore_bot_errors = true
Graças ao excelente trabalho de um dos membros da nossa comunidade, nosso site agora também está disponível em português: https://joinjabber.org/pt-br/
#xmpp #jabber #xampu
Because free software is also about accessibility, I'm doing some important work in Movim to ensure that the user interface can be navigated using the keyboard only. ♥️
This work also involves proper labeling and description of the page elements for people with visual impairments. 💬
This side project is supported by @nlnet. Thanks to them for making Movim an even better communication platform for everyone. ✨
New blog post! Some heartwarming news from the slidge community: the family is growing.
A tiny but very useful feature has been added in Movim today: you can now swipe to reply! ✨
And thanks a lot for your support, the yearly project costs has almost been covered 😁! And if you want to support me, everything is on the main website https://movim.eu/#fund
Enjoy ♥️!
(I also heard that there might be a Movim release in the upcoming weeks 👀)
I was a bit silent the past few days. It's because I was focusing on improving and fixing many features related to Spaces in Movim 😁
Notifications and message counter are now correctly working in Spaces 🔔✨ Some other issues, related to performances and navigation were also fixed along the way 👀
There is also a totally new flow when adding a chatroom or answering an invite. Movim will try to know if the room you are joining is valid and gives you hints about it before adding it to your bookmarks ℹ️
I'm planning a new release in the upcoming weeks with all those exciting new features in it 😉
Enjoy!
#XMPP Community
The #Chat of the Future Initiative discusses their spring activities progress today from 19:00 (UTC+1)!
Topics: Unified promotion material as well as an idea for a new community online event.