1225
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
view the rest of the comments
this post was submitted on 27 Jul 2026
1225 points (99.0% liked)
Fediverse
43141 readers
1826 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
- Posts must be on topic.
- Be respectful of others.
- Cite the sources used for graphs and other statistics.
- Follow the general 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
Huh?? It's not up to the admin, that's my point, the list is implemented by the dev and every instance that ran tesseract ran the same blocklist. My point is that it should be up to the admins of an instance, not the dev of software that gets deployed on multiple instances...
Okay. I see where the disconnect is. We’re both saying the same thing. In my earlier comment I said “as long as the Dev is open about it and it’s configurable by the admin”. What the tesseract dev did was wrong, what I was saying though is that a dev creating and managing a list is fine as long as those other conditions are met.
But then the admin isn't managing the list the dev is! You have one guy managing a list across multiple instances, that circumvents the public modlog, where users do not know how they got on, or how they could get off, and the power to shadowban across multiple instances is concentrated in the hands of just one guy!