Another #prosody release and another smooth upgrade. This one's a biggie, the 0. versioning has been dropped !
There's some additions for #DANE and channel binding, which I should look into. Also more granular permissions, which will surely be useful for deployments bigger than mine.
Downtime was also short enough to not trigger the uptime monitors.
I see even the bookworm-backports package is updated. https://blog.prosody.im/prosody-13.0.0-released/
#xmpp #selfhosting

diasp.in and durare.org #xmpp services are now running the latest version 13.0 of #prosody xmpp server!

Thanks to @buster for doing the upgrade. There was a small unexpected down time as database format had changed and we needed to fix that manually.

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.

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

Prosody 13.0.0: A Major Leap for XMPP Server with Enhanced Security and Performance

The Prosody Team has unveiled version 13.0.0 of its open-source XMPP server, introducing significant improvements in security, performance, and user management. This release marks a pivotal transition...

https://news.lavx.hu/article/prosody-13-0-0-a-major-leap-for-xmpp-server-with-enhanced-security-and-performance

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

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.

This weeks #Fedibruary topic was an #XMPP / #Jabber server and following a suggestion here on masto (thanks @erebion !) I installed Prosody .
In a move which probably made my life harder overall, I decided to install within our network and not on a public server. This is a problem because XMPP servers push mail to each other like SMTP... which I should have remembered before hand....

Anyway, I did successfully set up #Prosody and did some experiments, messaging to my #xmpp.social account and a second account I had created on the private server.

Because (i believe) of split dns issues i was having the users on my private server can't share media or files . I hope that would be a matter of correctly configuring dns and the issue might go away.

I'd have liked to have done a better job of this one but I think this is a valid proof of concept and I will be storing my notes ("documentation") away for a future live deployment.

#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)

I just migrated my personal #XMPP server based on #Prosody to its own #selfhosted server. I could not believe how easy it was, including transferring configuration, accounts, stored messages/files, etc.

BTW, the new server is just tiny, with 1GB of RAM, and it still seems to use only a fraction of it.

I suppose this is the result of dealing with an amazing protocol (XMPP) coupled with an excellent piece of technology (Prosody)

Ooof. I'm trying to set up #Prosody, but in a possibly weird way: it's running on a Mac Mini on the shelf, TLS cert is obtained via LetsEncrypt DNS-01, and the whole thing is fronted by a haproxy on a remote VPS.

So far, it is a bit of a pain in the ass. Possibly because I tried to test against my existing install, and that is bleeding from many wounds, too.

Estic intentant muntar un servidor de missatgeria xmpp (en servidor cloud debian). He provat #prosody, amb #Snikket, amb #eJabberd... Seguint les passes que indiquen a les seves webs sembla que s'instal·len correctament però les aplicacions (tipus Conversations) no troben aquests servidors xmpp quan intento connectar-hi.

Em podeu recomanar algun recurs (per novells!) per aprendre conceptes bàsics de servidors en general (ports, certificats, nginx...) i/o xmpp?
Gràcies!
#ajuda #servidors #xmpp