Hello everyone.

As you most likely have noticed, this community (along with some communities on other Lemmy instances) has become the target of a spam wave that quickly rose to prominence across the Fediverse: https://techcrunch.com/2024/02/20/spam-attack-on-twitter-x-rival-mastodon-highlights-fediverse-vulnerabilities/

For a while I thought staying alert and catching spam posts manually would be sufficient to weather the storm, but I was wrong. Even when I managed to remove posts immediately, it appeared as if the federation of either removals or reports was delayed, as I kept receiving plenty of reports by members of foreign instances for posts I had already removed.

I’m aware this spam has negatively impacted many users who view [email protected], some of which have understandably seen themselves forced to block this community to keep the spam off their feed. I took too long to take proper action, and I’m sorry.

A group of great Mastodon instance admins have managed to aggregate a list of instances that currently house the spam bots. As of now, dormi.zone blocks all instances found in this list. If you’re at home on one of those instances and are now cut off from this community because of the block, please understand that this is currently the best option Lemmy by itself offers to contain these sorts of attacks.

In the future, I will try to set up an AutoModerator that should handle these attacks more efficiently. Recent IRL circumstances have left me with limited time to look after dormi.zone, and I’m thankful for your patience in these times.

EDIT: I have been informed by admins from other Lemmy instances that because of the specific moderation action I took (banning the spammers from this instance), post removals weren’t federating, keeping the posts visible on some foreign instances. This is why I might have looked like I took days to remove some posts.