complying with a relatively inconsequential law
This downplays the impact to privacy these laws can have but sure, personal harassment is bad.
complying with a relatively inconsequential law
This downplays the impact to privacy these laws can have but sure, personal harassment is bad.
I’m going to bullet my thoughts on this whole thing because I’m annoyed by the general response, and the implementation as well:
This reminds me of when Guillermo Rauch from Vercel praised Trump multiple times. Bro, you’re not Tim Cook. You’re not Ellison, Zuck, or Musk. You’re not even on their level. You’re not going to get on their radar. I have PTSD from fellow tech folks being weirdly aligned with fascism and this whole dumb thing is giving me that vibe again. I don’t think this is that 1:1, but this is like the metal scene. You have to dodge the fascists that seem to weirdly permeate corners of the culture. People that refuse and get annoyed by right-wing labels, but still help right-wing grifters, are their own unique brand of pathetic.
Don't collaborate with fascists.
systemd maintainers rolling over and complying in advance somehow isn't even that surprising.
I don't get the "complying in advance" argument here. What would be an appropriate date for something like this to be accepted?
Well, the law doesn't come into effect until Jan 1st 2027, so you could delay until then at the latest. Or you wait a bit longer to see what the enforcement looks like and make the companies/politicians at least sweat a bit from any potential fallout. With GDPR some companies took a long time of dragging their feet to become compliant (partially because initial enforcement was lenient to give them time).
Right. I thin you are ignoring some complexity here. This developer added a field to store some optional data in systemd. That code needs to be tested, reviewed, debated, and eventually needs to be merged in. Those merges, at least with large projects, don't typically get added directly to main they get added to a release branch. That release branch then needs to be completed and merged where it will then be packaged. Then different distributions/installers need to add that field as a requirement to their code which typically goes through the same process. Then all those changes need to be packaged for release by the distros themselves.
So I'll ask again. Assuming that distros do not want to risk being fined and financially ruined. What is a appropriate time before January 1st 2027 to open this pull request in systemd?
This would also assume that we would like to propose a solution (for the data storage) early enough that distros do not all come up with their own implementations and leave PII strewn across the system.
Never. Let shit hit the fan if it has to. Fight back instead of swallowing the whole boot.
Legitimately the way various porn sites addressed similar laws is the way to go. Verification required in this state? "Well we're no longer serving this state's traffic at all, and conveniently here's the contact info of the government officials to blame, enjoy!"
Hi. Are you a maintainer of one of the distros that might be affected by this law? If you aren't then you have no standing to blindly tell them that they should not follow the law and risk fines that would ruin the funding for their project(s).
Bringing up porn sites is a false equivalency. Many of these laws do not require verification of ID or face scans as some are incorrectly claiming. They require a birthdate be entered during installation. The laws surrounding porn sites required 3rd party age verification which many of these sites said would not only crater their traffic from these states but also introduce a privacy nightmare which would also work against their business interests.
I imagine it feels quite righteous to drop maxims like this. I too am reminded everyday how glad I am not to have to live in a fascist state.
That said I think this sort of superficial dismissal is really unhelpful.
I think the vast majority of Linux users will agree we don't want to have to work with these laws but the reality is that we do. Far better we focus our efforts on minimising harm and promoting alternative mechanisms (e.g. zero-knowledge proofs).
Further I fear this righteousness actually serves to foster a toxic culture in the free software movement. And do you know what we call belligerent people who want to stifle dissent? Fascists!
I think the discussion we should be having instead is engineering ethics.
I think Dylan's letter clearly showed he isn't really involved in "FOSS radical" circles and has the usual engineering mindset (that was described in the Sam Bent blogpost). Not that I personally blame him, engineering schools raise students for this, and the corporate structure further enforces it with the strict hierarchies where you do whatever management orders you to do. What's important is that there are many devs who clearly aren't tied into the ethics discussion part of engineering. There's even research on engineers' attitudes afaik, and its conclusion was that freshly graduated engineers' first response was to implement changes without thinking about the ethics part, and after further prompting and discussion, they could be convinced that this change was bad and they need to push back.
I'll leave a two links here so when people iwsh to read, they know where to find good stuff.
git clone it and read it without browserOn a completely unrelated, off-topic note. Here is the same person talking about Google's new "advanced workflow" for "sideloading apps" on Android.
The title of his blog post is "Google's New Android Sideloading Flow Is a Fair Trade"...Figures.
You mention the title but not the content of the essay. Did you read it?
Edit: At first glance, the article seemed actually well-meant. Didn't have the context of how bootlickery it was.
TL;DR is that he says his initial reaction was "frustration" but then he goes on to parrot everything Google said to justify this.
For example,
57% of adults worldwide experienced a scam in 2025
It is to protect people from scammers. It isn't aimed at power users (Sounds very much like "It is to protect the children. This isn't aimed at power users").
There is no mention of https://keepandroidopen.org/ and what it means for developers of free and open android applications.
There is no mention of statements made by developers of applications like F-droid, Obtainium and Newpipe who have openly said that they do not agree with this step from Google.
There is no mention of how this can potentially demotivate individual android app developers and drive them away from the platform entirely (here is an example of this).
There is also no mention of how most of these malware, adware and nagware infested apps used by scammers are ironically on Google's own Play Store.
Other that that, no. I'm sure I did not read the content of his essay carefully enough. More importantly, my opinion doesn't matter. I'm just a reactionary idiot. But I wonder what the developers of those free and open source applications on F-droid, applications that cannot be installed via the Play Store (but their scammy fake versions can be), will react to this being called a "fair trade".
57% of adults worldwide experienced a scam in 2025
Sure. I experienced a scam and I told them to "fuck off".
That's not 57% fell for a scam, or 57% of android users got scammed by "side loaded" software. It's cherry picking a stat just justify a monopolistic practice.
Wow. Thanks for clearing that up. That was the first time I heard about the "advanced flow" and the criticism surrounding it.
Sure seems like a useful idiot at best.
Typical it doesn't effect me so why are they doing it. You said your selff 57% is a huge number. And they hopefully can reduce that. People on here secerly underestimate the average person let alone the half of the people who are below average.
Why so many fucking bootlickers??????????
actions done collectively by SystemD
Nope. It only needs one maintainer to do the PR
It'll discourage people from becoming open source developers
You know what will discourage Them more? Id verification
relatively inconsequential law
Give me your Id. Seriously, go and give me your ID with nothing blurred.
That's not what they asked
I also want to see your passport and your original birth certificate
That’s not what they asked
Wrong. That is all that is asked in the Californian legislation.
You are right that it was a loaded question, and you had a smart answer, but the implication of this "inconsequential" change represented by the current birthdate is of course more invasive identification later.
Otherwise why would they bother, because as it is now it is useless or inconsequential.
They don't want to be correct, they want to be outraged.
This is the same Reddit-brained nonsense that ruined those communities.
I don't think enough people realize that this is catastrophically bad. It'll discourage people from becoming open source developers, it'll discourage people from using Linux, and it'll discourage legislators from taking the Linux community seriously.
Sure, but personally, I don't want a linux community that's driven by corporate needs and governments that have been paid off by them. I don't view it as a catastrophe, if that's the version of "the linux community" that we lose.
None of that is to say that harassing devs is correct. It's not, and never is. Harassing anyone with death threats and dogpiling is not on. But if we take that out of the picture, negative pushback that drives away devs that would otherwise have helped implement universal age gating isn't something I'm terribly upset over, because I don't want the version of community they're taking us towards
this version IS the community and they're not taking us anywhere where we weren't already going.
linux is a much a product of our society as are other things like pop culture and capitalism. corporations of all sizes and reaches (ie red hat, ibm, google, facebook, etc.) have always steered the path and decided upon the development trends that linux has always taken and the only people who could have prevented or mitigated further centralized enshitification (aka the linux kernel developers group) bent over backwards to comply with the american government's overreach when they kicked out russian developers.
age verification is just the next step into this overreach and it too is being driving from the same corporate/government source that forced us all to accepting things like systemd or libvirt/kvm (facebook for the former and red hat for the latter) to service their profit motives.
like american politics, it's still possible to reverse the trend; but also like american politics; it requires a greater deal of collectivist action that westerners are unwilling to risk out of fear of losing their own tiny piece of the pie.
[the linux kernel developers group] bent over backwards to comply with the american government’s overreach when they kicked out russian developers.
I though that was mostly due to Linus being a typical Russia-hating Finn, but I never investigated.
a typical Russia-hating Finn
Russia seems to have that effect on their neighbours (until those neighbours get invaded, annexed, and the population dispersed, so the area can be called Russia. See Karelia and Ukraine for some recent and ongoing examples). So sure, could be that.
i also wouldn't put this past him given the reactionary tendencies he's demonstrated in the past; but i suspect that a threat of non-compliance == treason from the federal government probably had a bigger impact.
and if you've ever had the displeasure of working for the federal government; you'll hear horror stories of how capricious and draconian the selective enforcement of treason can be.
He sure was a big ol' dick about it I will admit. Saying anyone who disagreed was a bot or Russian troll really pissed me off at the time.
Its supposed to be open.
top 91 comments