

Interesting choice to give the developer who already violated user trust by imposing a secret blacklist the benefit of the doubt on their bigotry.
I never did that, sorry I kind of suggested I did in my last reply, when I meant in general to devs that don’t break peoples’ trust. In a vacuum, a configurable blocklist with biased defaults is acceptable, even if I wouldn’t set it myself that way. Their work, their choice. However, it is specifically the concealment of the biased defaults that is the breach of trust which calls into question the dev’s motivations.
Requiring users to enable “toxic mode” in order to access queer spaces isn’t evidence of bigotry to you?
Alone, no, that would be mere speculation, if combined with the shady practice or if you have antiLGBTQ quotes then yes, I could say that fact potentially supports that conclusion. Consider that blahaj.zone is not the only LBGTQ+ safe space on Lemmy (see beehaw !lgbtq_plus@beehaw.org). Any admin or dev could have beef with Ada, not with queer folks, that could be motivation to block blahaj.zone. I never gave the tesseract dev that grace, because that blocklist with blahaj was never publicized, until the clandestine filter list was discovered and decoded.

Following best practice would be ideal, I agree with you, but for FOSS projects I can settle for best effort, and ability to configure/correct any serious errors if it is brought up constructively. Every dev has their own biases and they make tools to fit their needs, not necessarily everyones. Like if it was by accident that a personal filter was pushed to all instances, and then immediately fixed when made public, personally, I could forgive the dev for the mistake. But available evidence shows this was not a mistake, and intentionally hiding things this dev didn’t like, pushing the upstream changes without telling anyone.