20, they/she, math+CS student

  • 0 Posts
  • 3 Comments
Joined 3 years ago
cake
Cake day: June 17th, 2023

help-circle
  • You can read into how you like the presence of certain instances/words/users on the blocklist, but putting BZ on a blocklist = bigot seems to me like a jump to conclusion.

    I will, and I consider you willfully ignorant for not doing so. Consider the probability distribution of likely motivations for drawing up a secret blacklist that specifically targets queer communities and anyone to the left of “let’s hunt immigrants for sport”. The majority of that distribution is gonna be bigotry.

    Like I said, I afford FOSS devs lots of grace and benefit of doubt, that’s just me, if the issue was solely over the choice of instances being blocked by default, I’d excuse it, but that isn’t the main issue. Call me too charitable, sure, it’s in my nature and you don’t have to be me.

    Interesting choice to give the developer who already violated user trust by imposing a secret blacklist the benefit of the doubt on their bigotry. Seems like that would lose them the benefit of the doubt if you were being intellectually honest.

    It was the trust that the so-called “Toxic mode” could remove all filtering, but it didn’t, and the trust that connection errors were simply configuration problems and not intentionally obfuscated filtering routines, these formed the trust that was broken.

    Requiring users to enable “toxic mode” in order to access queer spaces isn’t evidence of bigotry to you?



  • Trust that if they’re a piece of shit it won’t take long for them to confirm it (again) loud and clear. Not saying this isn’t a whole big bunch of bullshit, just that they should at least get a small opportunity to respond with their side.

    Given the fact that he deliberately targeted trans/queer people with this list, I am uninterested in giving him the benefit of the doubt, and very much hope everyone switches to the db0 fork and he loses his whole project over his bigoted hubris.