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.
What’s crazy is they could have simply:
- Apologised
- Explained the intent to reduce toxicity
- Agreed there was a lack of transparency
- Refactored their existing “enable toxicity mode” feature into a clearer, toggleable blocklist feature
Yes, I think there is genuinely an audience for what he was doing (or something akin to it), and it would genuinely have been a useful onboarding tool for getting a certain type of person to consider dipping their toes in the Fediverse.
But first of all it absolutely has to be separated from the safety/anti-spam filters. Bundling it with those is very malicious.
Second it must be opt-in.
Third, it must clearly say somewhere that "this anti-toxic setting is a curated block list based on my personal preferences". There should then have been an option to use a personal blocklist instead of the developer default.
And fourth, I guess ideally this type of filter should maybe have been maintained by a somewhat more... well-balanced individual.