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

[–] nullify3112@lemmy.world 1 points 21 hours ago (1 children)

Was the blocklist App wide or was it only in the app for the tessaract adjacent instances? I am struggling to understand how far the block list was effective.

[–] ICastFist@programming.dev 2 points 10 hours ago

It affected everyone using the app, no matter the instance. For example, if me, a resident of programming.dev, tried to look for the mod_abuse or power_tripping communities of any instance, I would see no results. If you tried to connect as a user from any of the blacklisted instances, the app wouldn't even work

When you use tesseract to connect to one blacklisted such instance , you just get a message informing you that Tesseract is “incompatible with that instance” which leads one to think of a technical issue, like an API mismatch, rather than the dev being an opinionated coward. - https://lemmy.dbzer0.com/post/72685299

Regarding the frontend, seems it also worked "behind the scenes" on the browser, which is stated in the post I linked in that quote. Unfortunately, the github links are all 404 now.