Forking is easy. Maintaining the fork is the hard part.

Yah, there was some bullshit like this that had people start “Ageless Linux” that was basically a script for people to change their sources on a Debian install to their version, and they haven’t done any sort of updates in over 2 months, to the surprise of nobody.

What a tempest in a teapot.

Fucking sweet. Honestly, we could just have one with and one without, build the OS making the selection, and have both available if it solves the issue. Put the burden on parents to make sure kids are using the OS with verification and leave everyone else alone.

But kudos to these folks!

the issue is not the presence or absence of any one json field. the issue is this random bootlicker with a history of foss-antithetical “contributions” being let anywhere near the decision tree in the first place., poettering the benevolent dictator adopting this idiocy and then, faced with a fucking tsunami of push-back and negative sentiment along every step of the process, doubling down on the decision to include it anyway because fuck you that’s why. unnecessarily, as it turned out but that is beside the point.

point is, none of the things above indicate there’s a healthy system in place for something that’s becoming an integral part of what we consider linux and can’t so easily be ripped out no more.

There are other system inits too

Like there are many issues with systemD and it is by design

Protest forks never last in my experience

Yeah maintaining a fork that seems like it’s going to be illegal to work on in many countries definitely will solve the problem.