this post was submitted on 27 Jul 2026
1348 points (99.3% liked)

Fediverse

43182 readers
1340 users here now

A community to talk about the Fediverse and all it's related services using ActivityPub (Mastodon, Lemmy, Mbin, etc).

If you wanted to get help with moderating your own community then head over to !moderators@lemmy.world!

Rules

Learn more at these websites: Join The Fediverse Wiki, Fediverse.info, Wikipedia Page, The Federation Info (Stats), FediDB (Stats), Sub Rehab (Reddit Migration)

founded 3 years ago
MODERATORS
 

As part of the devs farewell message on their site, they have included malicious code to make each visitor sends 2,000 requests to the dbzer0 servers in an attempt to DDOS and take the instance offline.

you are viewing a single comment's thread
view the rest of the comments
[–] EggInDisguise@lemmy.blahaj.zone 102 points 2 days ago (1 children)

Anyone who thinks "yeah lgbt stuff should be hidden because we want to attract people who don't want to see LGBT stuff" is someone I don't want anywhere near the fediverse.

[–] Coelacanth@feddit.nu 45 points 2 days ago (2 children)

Yes, agreed. Wholesome Yuri being banned might be the most outrageous decision of them all on the banlist, for me.

[–] mfed1122@discuss.tchncs.de 21 points 1 day ago

Idk, "🥺👉👈" was pretty wild

[–] basxto@discuss.tchncs.de 35 points 2 days ago* (last edited 2 days ago) (1 children)

Tbh for me it was more outrageous how it interferes with moderation. There are admins from big instances who weren’t blocked themself and mods from big active communities on that list. If they write warning comments, users of this frontend will simply not see them

And tho user and comment regex is a mess, partially containing very random things. Lot’s of possible wrong matches. This whole thing is from no viewpoint a good idea

[–] T156@lemmy.world 2 points 7 hours ago* (last edited 7 hours ago) (1 children)

Also from the other end, because of how the filter works, mods using couldn't see messages the user put, so they'd have been free to do whatever, until caught by either a bot, or moderators not using the frontend.

One of the reasons it was found to begin with was because the db-zer0 instance was on it, and the admin, who was using tesseract, suddenly couldn't load any posts from the instance at all. As Tesseract presents it as a compatibility issue, they were trying to track down the fault at the time.

[–] basxto@discuss.tchncs.de 1 points 6 hours ago

Very good point, that’s horrible. And blocking "your own" instance is pretty dumb. I wonder if db0 would also not been able to read own posts if the instance wasn’t blocked.