They are, but I suspect ejabberd itself which generates the hash from your password to compare to the hashed password in the Lemmy database might mess it up. It is quite backwards in regards to unicode in other ways, so that sounds plausible. But at this point I am really only making random guesses.

Edit: although if it was a hashing problem, it should return a wrong password error. I’ll have a closer look at the ejabberd logs if it shows anything relevant later today.

Try changing it to something simpler. It might be an issue Ejabberd side with those characters.

Do you have some really long password, like 60 characters or more? There was some issue with the Lemmy database dropping characters after that limit.

I don’t see anything broken with it right now.

Were you trying Movim in Fennec on Android? There is some odd issue with that browser specifically due to some recent changes with webpush, but with Chromium or regular Firefox for Android it seems to work.

As for Conversations, that should normally work unless your network blocks the xmpp ports for some reason. As this has become somewhat common on public wifis I am planning to add a workaround to allow connecting via the normal 443 port automatically.

The only other thing I can think off is that Conversations startet to enforce disallowing SASL plain connections. The dev talked about wanting to do that, but it breaks our auth integration with Lemmy. If so then there is probably a way to restore it to allowing that in the settings like on Monal.

Edit: the setting might be called “require channel binding” or similar. I personally use the Conversations fork Monocles and there is is called like that but afaik disabled by default.

I’ll be quite busy with something else tomorrow, but maybe I can add a few pixels now and then. Does the Fediauth work with Lemmy?

Aha, das war der ZDF Leitung also zu heikel. Naja, ich hoffen mal der Streisandeffekt wirkt 😅

Those have been active for a few months now and usually get banned from most (non-ask) communities quite quickly.

What concerns me more is despite how obvious it is that they are bots, the posts often seem to get a lot of engagement from other accounts that are both human and some less obvious bots (or maybe lurkers).

Not yet, no. There is some preliminary work merged, but it doesn’t seem like it will fully arrive soon.

I do a lot more food related DIY stuff, like balcony gardening, food preservation (bought from local farmers directly), planning to grow mushrooms etc.

Ah, sorry. That is my fault. Will fix it now.

Edit: Should work again.

This tutorial seems to work for basic Iocaine, but the Nam-Shub of Enki part is failing here.

Also somehow Iocaine works for other websites here, but in front of Lemmy it currently fails. Not sure why.

Edit: of course right after writing this I find the error with Lemmy and it seems to be working 🤦

But why a new Discord server? 🤦

This is a setting admins can change for both.

Ok, the main work is done, hopefully the images will work better now.

Edit: there are still some issues with images from blog posts and maybe remote images from other XMPP servers. Still investigating the issue.

Da kann jeder völlig unkontrolliert Kram posten, daher wird das gerne verwendet um erfundende Bekennerschreiben zu posten.

Die Tagesschau versteht mal wieder Indymedia nicht 🤦

Aber einfach selber wegmachen ging nicht?

You are referring to Lemmy as a whole or slrpnk.net specifically? Because I think there are some shitposting meme communities on Lemmy and there isn’t really a need to have another one on slrpnk.net

https://www.cdc.gov/floods/safety/index.html