#Prosody restored to working again on the stable Debian package.

It looks like #prosody had nuked itself, so this is a lesson: don't use upstream, just stick with the Debian package. Upstream moves fast and breaks things.

Today I upgraded my #Prosody #XMPP server from 0.12.5 to 0.13. I had to stop calling the vcard_muc module in my configuration files, as that functionality is already provided by another module. To double check: I was able to change a chat room's avatar, even after removing vcard_muc.

Thanks for the #debian backport, @debacle

PS: running "prosodyctl check" *doesn't* (and arguably should) notice that vcard_muc was called, and recommend that it should be removed.

Edit: I reported this in the Prosody XMPP chatroom.

#Prosody is the best modular #xmpp server you can use in my opinion

@tk My #prosody 0.12.5 server also can't do reactions in chatrooms - #XMPP clients are #Conversations and #Gajim. There is a claim that Prosody supports XEP-0421 here:
https://prosody.im/doc/xeplist
...ever since 0.12, but it's not enabled/installed by default, as stock-installed on #Debian 12 (from the backport for 0.12.5).

Note: XEP-0421 is absent from this page:
https://modules.prosody.im/xeps.html

I am not a happy camper.

Jitsi-meet (a chat server) had an upgrade today. It broke this thing called jitsi-meet.

It edited the config file for my domain at 9:20 this morning, which was when I ran apt upgrade, and screwed it up.

Arr, matey. Whar's the backup?

It's also looking for files whar they ain't. Arr. That's a known bug that happened with old versions in 2021, and was tagged "wontfix."

Maybe the domain config errors triggered the later ones. That would be nice. Otherwise, I'm chasing old ghosts, which is never fun, and makes me wonder about their release process.

There have been many upgrades. This is the first breakage like it for me.

Grr. Grumble. Gripe.

#Prosody 13.0.0 has been released (#XMPP / #Jabber / #ProsodyIM / #Lua / #lxmppd / #SCRAM / #SCRAMSHA / #SCRAMSHA1 / #SCRAMSHA256) https://prosody.im/

Okay, seriously. How do you use ad hoc commands in #prosody ?

Prosody 13.0.0 is here! Farewell Zero-ver!
This major release brings a number of exciting new features, including improved security, performance, and administration tools.
Check it out: https://blog.prosody.im/prosody-13.0.0-released/
#prosody #xmpp

#Prosody version 13 released:

https://blog.prosody.im/prosody-13.0.0-released/

Soon....

I finally got around to setting up my little personal #XMPP server. I've used #Prosody on a leightweight Hetzner instance, thanks to the #Guix deploy command and its fantastic Hetzner integration that's been added recently.

Here's a little blog post that I wrote about the process:

https://fabionatali.com/posts/xmpp-self-hosting-tutorial/

If you're an XMPP user and want to get in touch, my handle is fnat@xmpp.fnat.me.

#XMPP enthusiasts out there: what would you say the ultimate Achilles heel of the XMPP ecosystem is, at present? Fragmentation of clients? What?

My sense is that it's this: when one goes to store an XMPP address in one's addressbook, there doesn't seem to be standard way to store an XMPP address. #Android doesn't have that as an allowable field, and #Thunderbird and #Nextcloud have an "Instant Messaging" field, where the type can be set to "XMPP". But are these two compatible with each other when trying to sync between them? Edit: Yes, but there's a catch: *the XMPP address must be prefixed with "xmpp:"*

So "user@foo.bar" is not an OK XMPP address, but "xmpp:user@foo.bar" is.

Then to make matters worse, now there's a wish to change the labeling of "XMPP Address" to "Chat ID": https://gultsch.social/@daniel/114012904576436518

It might be a long time before the address synchy-ness ever works again between Android <-> #Davx5 <-> Nextcloud <->Thunderbird

Note: Android allows a "Jabber" type for an IM address, where you *don't* prefix the address with "xmpp:".

(#DeltaChat gets to gloat hard here, as they have plain-old email addresses)