914
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
914 points (99.1% liked)
Fediverse
43141 readers
1590 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
My favorite part of this was in the "elephant in the room" post.
One of his faq questions was something about if the list is a perma-ban. His answer was somewhat incoherent but basically if you stop being toxic you can get off it. But nothing about how. So either he's actively monitoring thousands of accounts that he's also secretly hiding from everyone else, or we were supposed to, I don't know petition him with our last 50 comments to prove we had changed and ask nicely to not be on a list we weren't supposed to know existed in the first place.
i'm still mad i didn't make the list for my poetic smelling of farts comment. I worked hard on that imagery!
I did not follow this drama, and I don't know about this list everyone is mentioning. Is this something that hides specific users posts and comments from the Tesseract UI ?
Basically, yes.
Tesseract was downloading at runtime an obfuscated blocklist of users and instances. One that the dev didn't tell anyone about, and didn't give an option to disable/modify.
db0 was trying to update Tesseract and was unaware that the whole dbzer0 instance was blocked in this way. And because the Tesseract dev is a spherical bastard, rather than saying "this is blocked", it said there was an API mismatch, which sent db0 down a troubleshooting rabbit hole that ended with him blowing the whistle on the whole thing.
And you can see how mature and wise the developer is for how he responded.
I only learned out about it when someone posted an stl badge of honor to the 3d printing community and during my "what is this even about" investigation found that I was on it.
But, yeah. BSOD summed it up pretty well.