Not to mention that they locked the unpopular pull request from reactions.
You must log in or # to comment.
Systemd has finally croaked. Time to remove that garbage.
It already late i think too many years gone and so big legacy depending on it
No they haven’t, they added a field where a user can store their birthday, as required by law in parts of the US.
Or do you recommend them to ignore the law, and jeopardize the whole project? Do you want linux get banned in California? You are mad at the wrong people
Yes, they should in fact just state that Californian users are not allowed to use it.
Basically that’s the other option. But considering a lot of the maintainers live there, it’s just easier to comply with the stupid law until it’s reversed.
Following clown laws legitimizes them.
Ok, who decides which law is clown and which isn’t? You? Or Sam Altman? I guess he has a different idea what laws he wants to follow. See, it’s a slippery slope you recommend.
Change your clown laws, and don’t bully projects who just wants linux to become viable alternative to common people. Don’t make perfect enemy of good.
False equivalence as privacy is a human right. Article 12 of the UN declaration of human rights.
People have the right to switch projects and criticize the actions of the developers.
So it’s the legistlation’s fault again, why aren’t you mad at them, why only systemd? In other jurisdictions you don’t have to use this field. And I don’t see anything in the PR about the verifability of the date. It’s just an optional number it stores in a db, offline.
Programmers have to become lawyers now?
Also a lot other projects has a birthday field, e.g. last time I worked with was LDAP: https://ldapwiki.com/wiki/Wiki.jsp?page=Birthdate I guess it’s there since the 90s.
No they haven’t, they added a field where a user can store their birthday, as required by law in parts of the US.
That’s an obvious foot in the door. The law is going to get worse. And we users expect the services we’ve been trusting all this years to see that too and act accordingly in response. As long as the critiscism remains civil, it’s perfectly valid.
Do you want linux get banned in California?
There is no single Linux. Each distro should have the agency to decide for themselves how or if they want to operate in California.
@infeeeee@lemmy.zip @Sunshine@piefed.ca @privacy@programming.dev
Or do you recommend them to ignore the law, and jeopardize the whole project? Do you want linux get banned in California? You are mad at the wrong people
IMHO, having Linux Foundation and the organizations behind Linux components (such as systemd) to follow the same steps that of IBM back in 1930s (similarly, IBM was just “following orders”, amirite?) wouldn’t be wise, either.
Oof, I might have to figure out another distro that doesn’t use Systemd, given that it is very common to find on most Linux distros. I wonder if I will jump the shark to FreeBSD or perhaps learning NixOS to declare the banishment of Systemd from my system.
NixOS is very tightly coupled to systemd, though there are efforts to change that
I’ve been reading about that myself…There are people trying to build an alternative init system for NixOS, looks like that effort is a long battle. FreeBSD could be a very hit or miss prospect for me, as I’d need to confirm the hardware support before making the jump. I have a 2021 PC, my general hardware would be supported in theory…The NVIDIA and Wayland support would make or break my choice, as I don’t want to use smelly X11. It’s time to move on from that antiquated display server.
There’s always TempleOS.
Likely the easiest course of action will be forking systemd. At least we can also stop the AI slop the main contributor also likes, rewrite it in some more maintainable language (not necessarily Rust - languages more close to C like D or C3 could ease porting and make C devs happier), etc.
Why fork, when there are better inits?
Many things rely on systemd way too much…
Then upstream instead:
Diversity is strength ✊🏿
Would it be possible to add a layer on top that shows you when an app requests it, and shows you a checkbox about what you want it to report? Or just block the call as not supported.
Faking it to be child (or just random with each request) until you need a higher number could mess up with advertisers and in general fingerprinting.
I think it is accessed through xdg-protal, and the usage tracking and permission etc. likely happen at that layer.
The xdg-desktop-portal project is adding an age verification portal (flatpak/xdg-desktop-portal#1922) that needs a data source for the user’s age. userdb already stores personal metadata (emailAddress, realName, location) so birthDate is a natural fit.
California… Are we already ignoring Brazil, for example? Or the fact that the rest of the U.S., Europe, Canada, etc., are pursuing these same plans as well?
Now I am wondering how many distros will use another init after this.
Why is the new field to enter your age worse than the already existing fields to enter your full name and home address?
The road to fascism (and enshittification) is paved with people telling you to stop overreacting…
