Thanks everyone for your confirmations. I’ll keep the workaround in mind in case this doesn’t get solved soon, and can confirm it worked for me before.
Thanks everyone for your confirmations. I’ll keep the workaround in mind in case this doesn’t get solved soon, and can confirm it worked for me before.
It is! Thank you very much 🧡 (Limbus Company is a turned-based strategy game with a heavy emphasis on story, and the less gacha-esque gacha to ever exist x’) )
In this specific case the community owner posted good guidelines before disappearing so we have that at least, but I’d appreciate being able to change the pinned message for example (current one is outdated), and the other community I adopted got a totally random troll post once so I now consider that these can pop absolutely anywhere at any time =')
Thank you for your answer! I suppose I’ll do that, then. So far the magazine has honestly not really needed moderation, but it’s always better to have someone ready before problems happen =')
Hello, does anyone know if it’s possible to moderate a magazine hosted on kbin with a lemmy account? I’ve been taking care of a magazine hosted here for months and the owner is MIA as far as I can tell (I tried messaging them to no avail), but the adoption feature mentioned here doesn’t appear for me from the lemmy side. Given how lemmy and kbin are compatible-yet-different, I’d understand if the moderation features can’t cross over, but for now I just don’t know so here I am =) Thanks for reading!
I can’t remember in which community I saw the link to this article, so I’ll add it there just in case given it’s very relevant: How to Kill a Decentralised Network (such as the Fediverse) (TL;DR: it already happened several times, by having the big corpo enter the network as the first step)
I’m personally in favour of defederating from/blocking everything owned/operated by Meta.
There are at least three communities for crochet between Lemmy and Kbin. I didn’t check knitting but would be surprised if it doesn’t exist soon =)
Thank you! Though I don’t understand github enough to see if this mean the fix will apply with the next update of the instances or if it’s supposed to already be deployed? If someone could clarify for me I’d very much appreciate it!