28
Nix project: ban? What ban? (discourse.nixos.org)

They invited that guy back. I do have to admit, I admire his inability to read a room.

top 30 comments
sorted by: hot top controversial new old
[-] antifuchs@awful.systems 18 points 5 months ago* (last edited 5 months ago)

https://discourse.nixos.org/t/constitutional-assembly-statement-on-jon-ringer/47393

“average nix contributor is removed from project 3 times a year" factoid actualy just statistical error. average contributor stays on the project. Mod Actions Jon, who lives in cave & becomes a contributor 10,000 times each day, is an outlier adn should not have been counted

[-] froztbyte@awful.systems 14 points 5 months ago

"we are recommending"

the fact that everyone has to suggest things instead of being able to fucking take action is..... so many parts of what's wrong in all of that

and by all indications, it's no accident

[-] self@awful.systems 17 points 5 months ago

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.

[-] froztbyte@awful.systems 9 points 5 months ago* (last edited 5 months ago)

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 tread 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 :|

[-] corbin@awful.systems 7 points 5 months ago

You don't have to release anything. Most of my flakes are on private storage in my homelab, including my homelab configuration, and I don't feel any obligation to contribute anything upstream right now.

Don't let them take the Nix language from us. Focus on what's important: nixpkgs can be forked trivially and everything will continue to work, because that's the point of Nix. They can't disempower us other than by insisting that we don't have voices on their committees.

[-] self@awful.systems 5 points 5 months ago

You don’t have to release anything. Most of my flakes are on private storage in my homelab, including my homelab configuration, and I don’t feel any obligation to contribute anything upstream right now.

that is true! there’s a ton of Nix stuff I’m keeping entirely personal now too. my projects fall into roughly three categories:

  • awful.systems infrastructure and its offshoots. this is the stuff that really needs to be released, because the administration of this instance should be as public and replicable as possible.
  • projects that use Nix as a build and environment setup tool. these should see the light of day too since they have value outside of Nix, but unfortunately most of them don’t build without Nix, and (because Nix is technically excellent) there’s usually no easy replacement for it. this particularly includes some of my hardware projects: I use Nix to keep modified embedded firmware, cross compilation tools, and userland images in sync, and it fulfills a similar role (from the ground up) for my lambda calculus reducer project, but there it manages HDL dependencies too. as far as I know there’s no tool* that does what Nix does here.
  • projects that pertain to how I use and deploy NixOS systems. these shouldn’t see the light of day. these include personal deployments, usability libraries, embedded system flakes, and flakes that deploy reusable Nix appliances. the biggest part of this is the NixOS sub-distro that I use on my desktops and laptops; it features a doom emacs UI, a ton of fixes to make EXWM work more reliably, and a few other services that make NixOS work generally more like a lisp machine (and which make elisp work more like Nix). a lot of these systems have upstreamable fixes I haven’t bothered with. again, this is an area where it feels like there’s no* real substitute for NixOS.

[*] guix would work fine (and for the sub-distro it’d have an advantage in that everything would speak Lisp), but given the sheer fucking number of GNU shitheads I’ve seen supporting Jon, switching from Nix to Guix feels a lot like moving out of your abusive parents’ house so you can rent out your abusive parents’ guest house

and the fridge in the guest house has a lock on the freezer so you can’t have ice cream, but don’t worry, nobody will notice (for now) if you remove the lock with some bolt cutters

I’m willing to be wrong about guix — I really want a reasonable out from the current Nix ecosystem — but this doesn’t feel like a healthy choice

[-] antifuchs@awful.systems 4 points 5 months ago

Agreed that releasing stuff isn’t necessary, especially stuff propping up the ecosystem.

Unfortunately, I think the rest of your statements are exactly inverted: the nixpkgs repo is pretty difficult to fork (moves fast, needs expensive CI/caches to properly operate), and while we may still have the nix expression language (and hey, lix is a good implementation of it!), I’m getting more and more convinced that it is not such a blessing.

The phd thesis though, that one is pretty good (currently reading it for realsies); lots of good ideas in it, regardless one’s thoughts about the expression language (:

[-] self@awful.systems 7 points 5 months ago

beyond anything technical, the question that’s been burning up my hope is:

why in fuck was this such an easy win for the techfash shitheads operating in the open?

seriously. these fuckers employed the most obvious tactics imaginable to damage the Nix community beyond repair, and it worked. it wasn’t even hard for them to come fuck up the only enjoyable tool I use.

and hardly anybody even managed to tell them no in a way that fucking mattered. the Nix governance changes were an obvious ploy that everybody fucking bought into! and I thought I was being fucking unfair for thinking this’d be the exact outcome!

and somehow, after all this bullshit happening in the open, there’s no viable fork? Aux got right to the edge of it — one of my systems ran auxpkgs without much trouble — then they let a bunch of bad faith assholes steer the project away from that, and now I don’t know what Aux is, but it’s not focused enough for me to contribute to.

the only ones who successfully said no were Lix, so the Nix language will survive! and as you pointed out, as it is right now that’s not great. it’s a lot like elisp — it’s janky as fuck but there’s a couple things it does uniquely well. unfortunately, the folks in control of nixpkgs control the Nix standard library, and they’d prefer the language remains obscure and janky. in short, these fucking jackasses want Nix to become as hard to use as Urbit, because it’s very easy to turn a priesthood of experts with obscure knowledge into a right-wing think tank. I’m sure it works even better if, unlike with Urbit, the underlying technology actually fucking works.

[-] ntm@awful.systems 5 points 5 months ago

the nixpkgs repo is pretty difficult to fork

For this reason, Tvix (a modular Nix implementation) cites compatibility with nixpkgs as one of their goals:

The package collection is an enormous effort with hundreds of thousands of commits, encoding expert knowledge about lots of different software and ways of building and managing it. It is a very valuable piece of software and we must be able to reuse it.

https://tvl.fyi/blog/rewriting-nix

[-] antifuchs@awful.systems 4 points 5 months ago

Yup, there are a few efforts out there like that, I would group aux and lix in with them, as ecosystem-compatible parts.

My feeling these days is that the ecosystem is kinda screwy on a fundamental level, and I’m willing to blame the unhealthy focus on “purity” (both the word and the concept) for a good part of that. The language you use to define packages and systems doesn’t need to be lazily evaluated and purely functional; nothing needs to be, that is a lesson freely available to be learned coming out of the early 2000s.

Anyway, here I am slowly reading through the doctoral thesis, picking out the (several) grains of corn that make up the really good and solid ideas that make it a useful system; maybe a thing can be made that adds a bit of pragmatism… and then a lot of effort can be poured into that, unpragmatically.

[-] barsquid@lemmy.world 15 points 5 months ago

I was browsing around trying to find background on this and some dimwits have put up wiki pages documenting a "woke takeover of NixOS."

I have not seen a single use of the word "woke" (as pejorative) or the word "wokeism" (at all) which has not been from an overtly racist bigot. The existence of such a wiki page explains everything I need to know. Typical bigotry, including the bigots pretending the situation is the opposite of the reality.

[-] antifuchs@awful.systems 11 points 5 months ago

Of course - it’s all part of the cancel culture grift economy. I look forward to us being able to hate-read Jon’s self-published autobiography in a few months.

[-] sue_me_please@awful.systems 4 points 2 months ago* (last edited 2 months ago)
[-] barsquid@lemmy.world 4 points 2 months ago

Right? What the actual fuck. Some people need to touch grass.

[-] self@awful.systems 3 points 2 months ago

holy fuck that’s fucking embarrassing. I guess I’ve got one link I can paste when I’m asked for an example of the Nix community being a Nazi bar, cause they’ve kindly implicated themselves in their own words. and this is the NixOS wiki that was our only non-blog source of docs for shit like flakes and various NixOS options and facets of the language for years! this is where most of the text on the (extremely recent) official wiki came from! and here it is, screaming about marginalized people being woke like a drunk uncle at Thanksgiving

[-] sue_me_please@awful.systems 3 points 2 months ago* (last edited 2 months ago)

Blows my mind that this exists on what seems to be the official wiki and no one has distanced themselves from it lol

I feel like such a mark for adopting Nix in the first place

[-] froztbyte@awful.systems 4 points 2 months ago

the "totality" of the fash takeover is fairly recent, but the groundwork has been put in place over some time prior. same play as they do in all the other places they've been trying to take over

at this stage I think the best hope is for lix/aux/guix to continue growing and gaining firm ground, and for people to start moving over, with origin-nix atrophying over time until something is forced to change or it dies off. which is an entirely other pile of problems too :|

[-] froztbyte@awful.systems 12 points 5 months ago* (last edited 5 months ago)

they finally banned him, permanently, from all official spaces (link)

which leaves me to wonder how much he’ll try in other areas

[-] FRACTRANS@awful.systems 9 points 5 months ago

Well, that’s one way to assuage my self-frustration over never getting around to actually learning Nix.

[-] froztbyte@awful.systems 9 points 5 months ago

I spot another couple of big core-foundational-infrastructure projects in that list, at least a few of which are now also maintainer-less

nixos will be able to still coast on momentum for a while (because that's how well-built infrastructure operates) but it looks like the deep cuts will start to eventually impact them in pure maintenance/upkeep burden alone. whether it'll be enough to really "kill" it, dunno. I want to believe there's not enough ops-clued chuds that they could find and hire, but I don't know what the numbers really look like..

(not that I blame samueledr for their choice at all, more remarking in general)

[-] Soyweiser@awful.systems 9 points 5 months ago

The reply before this is also quite something, all angry somebody is saying they will leave if this carries on. I assume they would also be just as mad if somebody just started to ghost the project and just left because of this.

[-] froztbyte@awful.systems 9 points 5 months ago

wow, sure is a strong community member there. you just know you can trust their takes on community participation!

(idly: lol, didn't know discourse made those stats public, but hilariously useful for muh sneer)

[-] Soyweiser@awful.systems 2 points 5 months ago

Wow doing a dive on somebodies post history is a bit creepy, not sure how I feel that every site now keeps (and makes public) that much info about everybody.

Otoh, from the 'top categories (posts/replies)' part:

lawl. (I'd assume a github profile is more important in this case, but I'm not going to dig into that, I already feel filthy).

[-] dgerard@awful.systems 14 points 5 months ago

nah, not going to allow "looking into the chud's extensive comet tail of receipts is bad" as any sort of discourse norm

[-] Soyweiser@awful.systems 5 points 5 months ago

No that is fair, it was a personal expression of disgust. A combination of being a bit of a private person and disliking how everything has public gamification and searchable logs now. That and I do not think what they said was that bad (just dumb, and the context made it worse) to warrant a full investigation ;).

[-] froztbyte@awful.systems 10 points 5 months ago

nothing particularly wrong/dirty/whatever about this imo. hell, it's just about an essential skill for researching in general, whether researching chuds or otherwise

[-] froztbyte@awful.systems 11 points 5 months ago

also fwiw this was, like, "clicking their name in the forum to see who the hell they were". I barely even started digging :D

[-] Soyweiser@awful.systems 4 points 5 months ago

Yeah it just feels dirty to me, I usually try to set those kinds of features to private the moment I become aware of them. (And I certainly have digged into peoples posts here before and then kept the info to myself as while what I found wasn't great I think doing a sort of helldump (I think that was the term) even on chuds is a bit eurgh. Esp when the people themselves are just random people with a hundred followers. (Of course this depends on the type of person, neo-nazi types I'm a lot less friendlier to than other random meh people, like this attempt above at trying to put the 'our community blew up' back into the bottle tone police guy (that is the type of person they seem to be on reading my initial comment, didn't dig further)).

[-] hrrrngh@awful.systems 8 points 5 months ago

"Helldump" is my new favorite term for that

Sometimes you find really crazy stuff in people's histories. This year, I've found a Black neo-nazi, an alt-right plural system, and a Thelemist who is just so beyond the pale I literally cannot paraphrase what they said and have to quote it in full: https://www.reddit.com/user/Nexist418/comments/i6is83/banned_reddits_and_the_reasons_if_known/

/r/animememes :: Did not use the banned word "trap" but explained how banning the word was an empty meaningless gesture. Also, demonstrated how Communism is a failure (in the private messages with the mods). Despite doing as they asked, and despite not having broken the rules, they have not bothered to adhere to their end of the deal. Not surprising Communists never seem to do what they promise.

I just follow the prime directive with these people, but I think it's mostly because I'm not good enough with words to accomplish anything by confronting them. I remember this one impassioned thread on like, /r/HarryPotter or maybe /r/books about HPMoR and all the crazy TREACLES stuff. And I understood them completely, but I felt bad because it had like, two comments, and neither really got what OP was trying to communicate. They were like, "I love HPMoR, it's so upsetting that bad people online co-opted it! That's crazy. Thanks for the heads up!"

[-] dgerard@awful.systems 10 points 5 months ago

Also, demonstrated how Communism is a failure (in the private messages with the mods)

...

this post was submitted on 21 Jun 2024
28 points (100.0% liked)

FreeAssembly

75 readers
1 users here now

this is FreeAssembly, a non-toxic design, programming, and art collective. post your share-alike (CC SA, GPL, BSD, or similar) projects here! collaboration is welcome, and mutual education is too.

in brief, this community is the awful.systems answer to Hacker News. read this article for a solid summary of why having a less toxic collaborative community is important from a technical standpoint in addition to a social one.

some posting guidelines apply in addition to the typical awful.systems stuff:

(logo credit, with modifications by @dgerard@awful.systems)

founded 7 months ago
MODERATORS