Fight the laws. The laws are bad and if they get worse, they will have real negative consequences instead of potential negative consequences. Fighting systemd is making a symbolic scapegoat out of the wrong target.
Yes, i would have hoped a more vocal statement from systemd or lennart. Yes its virtue signaling but it would communicate clearly whether theyre for or against this bullshit. You can comply and yet lodly disagree, or you can just comply and stay silent…
You’re not demanding that those be ripped out of NixOS, I presume. So you really should ask yourself, why are you focused on the systemd piece?
I both see your point and @IvanaX86’s, systemd is a critical component that some people think we should have never created a hard dependency on. You may or may not disagree, but the reality is that systemd is irreplacable on NixOS. Its not optional like a browser is, (im thinking of eww, no freedom restriction there /s) or like Steam is. You cannot run nixos without systemd or significant pain and effort.
The difference is, those components are not a central part of the operating system, systemd is.
systemd runs on PID 1, literally everything runs from it. If age assurance becomes mandatory then systemd can simply block the OS from booting. It is also possible that systemd could later on decide to make it more and more difficult to patch the age-assurance out by making more and more of the codebase dependent on it to function.
You also cannot “rip out” productivity software or browsers out of the base OS. They’re not a part of the OS. They’re optional packages that you may or may not choose to install.
Your gangrene point is inaccurate, gangrene is removed by cutting said part off, like I said. “We can patch it out” is a great argument until it becomes too difficult to patch out. I believe it was the dropline gnome project that stopped supporting the gnome environment in 2020 exactly because it became too much work after gnome decided to implement hard dependence on systemd.
Regardless, the precedent itself spreads. The laws and implementations tighten, and suddenly the blocking of adult sites is normal and age assurance also becomes the new normal. The gangrene analogy is accurate. Removing an idea or “the way its done” is difficult to roll back once the precedent has been set. You can keep your “other than it frightens you” to yourself. You’re assuming things about me whilst knowing utterly nothing and it’s completely irrelevant to the argument.
“Fight the laws” yes I am already doing my best to spread the issue with these laws, I even wrote an article about it. But it doesn’t mean that I shouldn’t address every single possible avenue where these issues stem from. It’s false equivalence from your end.
in systemd, then I will work to protect NixOS users from that change. If it becomes mandatory somewhere else, I will do the same. Until then, I wish you peace and happiness in life.
I take your 2 cents that are wrong. I know what finix is, i wrote NixNG myself. I also know that it is possible to replace systemd, but I also know how hard NixOS depends on it. And writing a compatibility layer is a pain the arse. It can be done, like windows programs can run on linux, but equating a web browser to systemd is wrong
Please do elaborate. Finix is a nixos replacement, not a nixos patched to worked without systemd. Can one import a unchanged nixos module into finix? Can i take my existing nixos config and replace systemd with finit or dinit? Thats what were arguing here. One can write a OS using Nix which runs on top of emacs as pid 1, doesnt mean nixos can suddenly do that.
And dont get me wrong, i appreciate the effort that went into finix, i better since again i wrote nixng. But neither are nixos but without systemd, like void linux isnt debian but without systemd. What im arguing here, is devuan, not void. In any case, i dont have that much of a problem with systemd on a technical level anymore. Nor am i too offended by their lack of a push back against age verification, im just disappointed and concerned.
And @aanderse to be 100% clear fimix is great, i wish you all the luck i do have a slight amount of NIIH syndrome, but finix overtaking nixng is purely my fault should have ivested more time into it
Then it’s up to the individual to reify the remediation in the form of flakes or overlays or whatever. I think a critical bit is the delineation of poisonous changes, which could be collaborative. How far we care to drive this is open to discussion. Documenting where the mandated detriment is within NixOS is just that, documentation. It’s not refusal to comply. It’s just normal OPSEC docs.
The remediation itself needn’t be a central NixOS thing. But it could be a community thing; or a distributed sub-community thing.
Also, I think it would be wise to prioritize transparency and observability from the perspective of the individual. When is a “signal” being transmitted? What “application” requested it? What was the contents? Etc. One thing I find disturbing about these legislation is the implicit nature. That the user is taken out of the loop.
BTW, anything that accesses pkg repository (the “covered application store”) will take on the responsibilities of the “application”. This sounds quite impactful.
Great fleas have little fleas
upon their backs to bite 'em,
And little fleas have lesser fleas,
and so on ad infinitum.
And the great fleas themselves, in turn,
have greater fleas to go on;
While these again have greater still,
and greater still and so on.
/s) or like Steam is. You cannot run nixos without systemd or significant pain and effort.
i do have a slight amount of NIIH syndrome, but finix overtaking nixng is purely my fault 
should have ivested more time into it