phraktalz
RetAll together now: fuck systemd
First to tongue the boot when it comes to this age verification shit I see.
Revert "userdb: add birthDate field to JSON user records (#40954)" by paramazo · Pull Request #41179 · systemd/systemd
This reverts commit acb6624, reversing changes made to ba1caf0. Revert "userdb: add birthDate field to JSON user records (#40954)" After extensive community discussion, legal review and c...
It's an optional field in the userdb JSON object. It's not a policy engine, not an API for apps. We just define the field, so that it's standardized iff people want to store the date there, but it's entirely optional.
Lie by omission here. Clearly the reason for this being added is AV. Imagine it was a "sexualOrientation or "ethnicBackground" field that just got added because $government suddenly made that sort of thing a hot topic... "oh it's just part of the JSON schema, it's not up to us to decide how people use those fields! Fuck off. systemd should have no knowledge of any of that. It's irrelevant to the operation of the system.
Playing into the hands of fascists and he knows it and doesn't want it discussed or highlighted.
I also hate project owners and maintainers that close down discussion like this full-stop. It's not like it's taking place in your front room, Lennart. If people want to discuss it and decide whether they agree or not, let them.
Soulfire The Wolf 
rk: it’s hyphen-minus actuallyAnd while I don’t want to anthropomorphize an LLM, he didn’t even say please.
I’m not sure that he should, but like…I’m the kind of person who feels bad for NPCs in video games so. And being polite even when it literally doesn’t matter still helps you practice being polite.
Plus saying please costs the LLM providers more money.
Lukas Rotermund
Eichi🐺@ret I joked about this yesterday, but doesn't this change technically mean that any "you must provide data xy" law now needs to get merged into systemd?
Now what if another state, nation or whatever decides you must not collect that data?
Now what if another state, nation or whatever decides you must not collect that data?
@ret Unless systemd is a company located in cali I really don't get why this specific law has to be complied with.
Spork ✌️
Simon I Groove@SimonIGroove @Eichi @ret Ah, yes, I'm a fascist because I think people should focus their attention on the bad laws themselves instead of a user-editable date field in an init system that was immediately reverted.
Fluffy Kitty Cat
Alexander Bochmann@ret The road into surveillance and dictatorship is littered with engineers who just added an optional feature without thinking about the consequences and taking a stand. He could have just said "not in my systemd".
nicole mikołajczyk@ret Made a better PR. https://github.com/systemd/systemd/pull/41247
userdb: remove birthDate field from user records to preserve AI-readiness and privacy-by-design guarantees 🚀 by mkljczk · Pull Request #41247 · systemd/systemd
This reverts commit acb6624, reversing changes made to ba1caf0. Following extensive community deliberation 🤝, independent legal review ⚖️, and a collaborative privacy impact assessment across multi...
Niko
maaneeack
patter
Phil M0OFX@patterfloof @ret I thought this was a "oh they turned down a dumb idea" thread until I read the rest of it.
I concur: what the fuck is this doing in the initrc?
I concur: what the fuck is this doing in the initrc?
RawiWoof@ret
On one hand, it drives me insane that FOSS projects, who would always pick up pitchforks and torches the moment anything even vaguely smells as unfree (to a point of promoting negative freedom as if it was a new strain of cocaine), are now rushing to give a blowjob to any LibFash shit-for-brains with AV.
On the other hand, when I think about the power dynamics, what can they do?
One option is go to the court. How many projects have resources to go into a legal battle with a state? Not many. Not to mention, who enforces the law? And where does one guarantee the state actor will obey the law anyway, especially in a fash-trasheap like the US?
So the only remaining options are comply or die. Because if the project would have had the legal power to take the idiotic law down, they'd have already gone for a fight assuming they're not a doormat.
So while want to rearrange Poettering's face for doing this shit (something I wanted to do even before that because he's an arrogant dick), he doesn't really have much choice in that regard.
On one hand, it drives me insane that FOSS projects, who would always pick up pitchforks and torches the moment anything even vaguely smells as unfree (to a point of promoting negative freedom as if it was a new strain of cocaine), are now rushing to give a blowjob to any LibFash shit-for-brains with AV.
On the other hand, when I think about the power dynamics, what can they do?
One option is go to the court. How many projects have resources to go into a legal battle with a state? Not many. Not to mention, who enforces the law? And where does one guarantee the state actor will obey the law anyway, especially in a fash-trasheap like the US?
So the only remaining options are comply or die. Because if the project would have had the legal power to take the idiotic law down, they'd have already gone for a fight assuming they're not a doormat.
So while want to rearrange Poettering's face for doing this shit (something I wanted to do even before that because he's an arrogant dick), he doesn't really have much choice in that regard.
@rawenwolf just ignore it? what are they going to do? Poettering isn't a U.S. resident, let alone a California resident (this is state law, not federal law). As an aside, not even sure the law compels the storage of date of birth at all. They have just chosen to do that to make it easier for future implementations.
@ret
The residency part is an important detail and it'd make enforcing the law complicated on a personal level. And yes, state laws don't have the massive legal overreach like federal laws where everyone shits themselves even if they're nowhere near US jurisdiction (wouldn't enforcing one country's law in another technically amount to an act of occupation/war?)
"Just ignore it" can only be done for so long because, depending on how the law is formulated and enforced, any non-compliant system could be limited in accessing critical stuff (see alt. Android systems and their neverending cat-and-mouse game with banking and government apps). And once those laws reach a critical mass in adoption (UK-OSA, EU AV laws, AUS AV laws etc.), they'll be pretty much cornered. Direct attack isn't necessary. All these laws need to achieve is make noncompliance too inconvenient. Kind of like in CyberSec one can't make the system 100% hack-proof but one can raise the bar of breaking in so high that overwhelming majority of people won't want to put in the effort.
Hence why this stuff must be stopped before it even reaches any form of law because once it does, the battle becomes million times harder. This stuff is one nasty version of "David vs. Goliath" except this Goliath has massive popular support (for some unknown reason) and isn't prideful. And yes, it drives me mad that many are complying in advance, failing the first lesson of "On Tyranny".
jn (big endian energy)> what can they do?
Refuse to engage in anticipatory obedience, organize with the EFF or similar groups who have lawyers to resist in a longer-lasting way
nLupo 
Baloo Uriza@rawenwolf He could and should have chosen either not to or to resign and let an adult in the room take over.
@BalooUriza
I'm sure a lot of people, myself included, would like it a lot if he chose the latter 
Colin@ret @creideiki Init Freedom folks: “Finally!! Say it louder! For those in the back of the room!”
jamesb (MW1CGG)@ret
Agent Poettering never fails
Agent Poettering never fails
Gender David Copperfield@ret systemd isn't even an operating system. WTF are they doing???
Pippin@old_angry_queer @ret It's getting its fingers into so many pies I'm pretty sure it desperately wants to be an OS.
🇺🇦 haxadecimal 🚫👑@ret
As soon as I have a distro that I includes that BS, I'll write a service that runs earlier, and randomizes the birth date storage on every boot, within a specified range. I think I'll call it "fucksurveillanced".
More often than every boot, if the systemd crap will allow it. Ideally, every minute.
As soon as I have a distro that I includes that BS, I'll write a service that runs earlier, and randomizes the birth date storage on every boot, within a specified range. I think I'll call it "fucksurveillanced".
More often than every boot, if the systemd crap will allow it. Ideally, every minute.
Simon Zerafa (Status: 
😊)See Ageless Linux for the ultimate solution to this, and maybe other related issues.
As an approach, it has a lot of merit, as a protest it's priceless.
Spitfire
fcalva
Mark Hughes