Nix project: ban? What ban?
Nix project: ban? What ban?
samueledr has left the project in response and their parting message pretty much sums it up
the most important thing a moderator on this hostile network has to take responsibility for, above and beyond all technical concerns, is ensuring that fascists and their absolute bullshit do not have carriage on any system they control. I’m fucking done pretending this isn’t a basic expectation. anyone who has the ability to remove fascists from their community and doesn’t is responsible for what will happen.
I have about a fuckload of Nix code I need to release. awful.systems still runs on NixOS after all, and I’ve gotten very good at writing Nix — and far too reliant on it. I’ve been neglecting finishing those projects and a fair few infrastructural tasks for our instance because my gut and my heart won’t let me contribute to an ecosystem that has repeatedly gone out of its way to empower fascists and abusers, to the detriment of a frankly ridiculous number of extremely talented contributors who got pushed out of the project — which is what happens to every community, every time the folks trusted with the ability to moderate decide to give the fascists a pass.
I’m still chewing it over, but it feels like samueledr’s got about the right idea. I’ll release my code here for our (very vocally anti-fascist) purposes, but I’ll take steps to make sure it’s poisoned against being integrated into the current form of the Nix ecosystem. if Aux, Lix, or any other anti-fascist Nix offshoot finally wants to step up and start an ecosystem worth contributing to, my projects will be available to them.
I guess it’s better shown through my actions. What would it take for me to come back? The answer is relatively simple. Have the moderation team actually empowered to act, without having to dance on the eggshell broken by the continued FUD of people allowed to sow division in the community. And go back to the people banned, and RFC 175 supporters, and (1) warn the supporters (2) ban the people directly involved with this farcical clown that is harassment in disguise. Then I’ll consider it. ...
I’ll release my code here for our (very vocally anti-fascist) purposes, but I’ll take steps to make sure it’s poisoned against being integrated into the current form of the Nix ecosystem
I’ve been trying to background-ponder what measures could work for this sort of thing. classical hindrance methods such as code obfuscation are counterproductive to debugging and dev work, and strongly tying code to its runtime has other problematic implications. licensing alone isn’t sufficient because you need the ability to actually do something from those terms (whether lawyers or …), and doubly so because these fucking awful human beings do not actually care and will treat over any license terms as long as they benefit, and will use power to defend their actions.
oldmanshakesfistatcloud.bmp for trusted computing still being so damn nascent -_-
wish I had more fucking spoons to research this shit properly :|