@kelbot #Prosody is usually really simple and easy. You'll want to make sure your chosen distro has reasonably up-to-date Lua libraries. You'll also want to set up Let's Encrypt, but last time I set it up, you'll need to ensure the Prosody user can read the certs (probably by copying them into Prosody's directory and chown ing them).
Look at the features you consider must-have and make sure there are plug-ins / extensions for those features, such as message carbons and message delivery receipts. (See: https://petermolnar.net/instant-messenger-hell/ )
@kai Well, I do like the #Prosody !XMPP server--easy to set up and works very well, except when it doesn't--but I think I'm going to use #ejabberd next time I set one up.
@amic #Prosody is mostly very easy and reliable, but when it doesn't work, there's no easy solution besides waiting for several months until it miraculously starts to work again. You can try #ejabberd, #OpenFire, or (according to a certain account here) #Tigase in those situations. !XMPP
@tigase Mostly whatever their contacts use. I chose #Prosody because people I knew were using it. When I spun up an #XMPP sever at work years ago, I ran Jive ( now #OpenFire ) because they also made Spark, the client we used. (Sadly, the test was successful, and $EMPLOYER chose to go with Lync / Skype.)
@maiyannah Are you moving from #Prosody to #ejabberd? (re: "XMPP server is changing to ejabberd in the near future." in the header on HAC)
First of all I'm curious why, because I moved from ejabberd to prosody because the first was just a mess to administer and barely supported anything that I wanted a couple of years ago. Has that changed?
Also, there are migration scripts for accounts from ejabberd to prosody. Aren't there any the other way around?
@gargron Either way, I don't think there would be a problem for !GNUsocial with remote #Unicode (non-ASCII) characters. Nicknames are normalised as-is (for example removal of underscores which was another discussion). I don't remember if transliteration of nicknames is done, but we do that for #håshtägs (which has also sparked controversy due to incompatibility with farsi).
My desire is to implement unicode support for nicknames. I don't know about the best strategy for homoglyph attacks etc, but I bet the !xmpp community has lots to share there. There you can have at least a large set of Unicode in your user part of the XMPP ID. Maybe #Prosody developer @zash knows more about unicode in XMPP usernames etc?
@tardigrader Dvs vad är src-attributet i bilden du försöker använda och vad får du för statuskod/svar vid anrop? Och vad säger felloggarna i #prosody (viktigast kanske)?