Next they will mandate a “race” field, and the same kind of imbecile will implement it.
Fuck this guy.
I’m so confused he adds a JSON field and corporate linux (who fund 95% of Linux development) need some sort of age auth mechanism for enterprise deployments. What do you guys want instead?
Like its not even enforceable, when the hardware attestation comes sure but before that why does anyone care (thats not going to stop you from changing a json field in systemd lmao)
I love the level of disdain the linux community has for this kinda bootlicking.
Be careful now! His coworkers will act most silently.
Collaborator
to all y’all with the “it’s just a text field”: what if the field is “race”? “sexual orientation”? “jerks_off_to”? what the fuck has a system managing daemon got to do with any of that? and why would you preemptively put it in there without even a pretense of a fight?
fuck you make us! make linux illegal, in Cali of all places. guess how long that will last?
Yeah, scary.
What about some other scary fields like:
- Real Name
- Office Address
- Office number
- Office telephone number
- Home telephone number
- external e-mail address
I mean if those fields were stored, could you imagine the danger that Linux users would be in?
You don’t have to imagine, because those fields have been stored in UNIX/Linux since 1962. https://en.wikipedia.org/wiki/Gecos_field
Your argument is an informal fallacy called Whataboutism.
I invite you to educate yourself by reading about it on Wikipedia
You should read the article and understand the difference between a comparison and Whataboutism.
Those are also entirely optional and not having them filled in doesn’t cause other software to stop doing what the user wants.
(same for the birthDate field)
Not true. Because the stated purpose of the laws at play is to enable that to be queried so that sites can decide what is appropriate for you to see.
That is the purpose, but the field is implemented as optional and modifiable with admin privileges.
Depends how these new laws are written.
The same with the birthDate field.
… unless someone merges a PR making it required, which is the discussion of this thread.
What if someone makes a PR making your real name and address being required? Damn…
You’re right.
“What if <insert dystopian scenario that hasn’t happened>?” is a silly argument.
And then you can input a random date from before 1940 and forget about it…
Stored “because law”, right?
Who cares why it is stored, these fields exist for every user in every Linux system and they have existed for decades.
Either birthDate the field is dangerous or it isn’t. If it is, how?
It is no different than data fields that ask for way more identifiable and personal information such as Real Name and Office number which have, again, existed for decades without issue.
Ah, but this time the government wants it to be able to be queried so that applications and web sites can decide what to do with you. That’s the difference.
The government’s wants are not in the PR. The PR is an optional JSON field.
The field isn’t dangerous, you’re conflating two different things.
The age verification laws are the threat, not an optional text field or the developer who added it.
I care. One thing is “you know, fields with this name have been around since before you were born”, another thing is “some idiots passed the law half the globe away, now we are preparing your system to comply. Someone has to ©”. The field is not the danger, the thinking, attitude and act is
Edit: some local law, for fuck’s sake
Half a world away where do you live since this is happening everywhere. To be half a world away from any place doing this would be hard.

Being half a world away from Americas is pretty easy, don’t ya think?
That’s a fair argument.
Is it fair to say: The field is benign but there is contention about if it should be added or not and users of the software are concerned that their voices were not heard on the issue. That can be handled in the normal project framework, perhaps by suggesting a publicly stated policy about these issues around legal compliance so the community can determine if they want to support the project or not.
My argument is that I don’t think that the damage that was done justifies the hitpiece in the OP which is, almost literally, painting a target on the developer with the mugshot photograph and loaded language.
So, if you’re not one of the people then we’re having different conversations. In that conversation, I do agree with what you just said. I’d like to see the very large projects, which affect a lot of users, such as systemd, have a more formal way to accept public comment and respond on contentious changes and feature requests.
It is not a hit piece. No call to action was stated.
It paints him as an active danger, puts his picture on a wanted poster, includes his full name, workplace and the city and state where he lives and then writes up an article like an after action report of a cyberattack.
It then implies that he’s going to do it again and that he can’t be persuaded and so will be ‘harder to stop’.
Taylor believes what he’s doing is right, which makes him harder to stop than someone acting for money. Taylor already has the resume line and knows the codebase well enough to try again. That’s the true believer pattern. The argument is ideological, so persuasion is off the table.
So if he’s done a bad thing, he’s going to do it again, and you can’t persuade him.
If you can’t read the implied call to action then you’re being deliberately dense.
To be fair, I am bit split on this. On one hand, name and shame is an effective strategy and should be used. On the other hand, “put age verification into Linux” is a hilarious stretch. And yes, it feels strange that I have yet to see any kind of response from other systemd maintainers and managers - after all, the man authored a pull-request, not merged into into upstream. I have not been looking for that kind of response myself though, which also serves your point: putting all the blame and anger on this one man (I purposefully omit name) is too much
Is it fair to say: The field is benign
It is benign if it is optional, remains 100% local and under the user’s control and doesn’t prevent other software from functioning as expected.
It is optional, 100% local, under the user’s control and does not prevent other software from functioning as expected.
If it ever is not, then you can simply fork the project at or before that change.
deleted by creator
I think back then it was generally assumed this simply assisted with office communication.
Imagine telling a UNIX engineer in the 70’s how almost everything you enter into a machine would eventually be used to manipulate or entrap you by the State and surveillance capitalism.
Imagine telling a UNIX engineer in the 70’s how almost everything you enter into a machine would eventually be used to manipulate or entrap you by the State and surveillance capitalism.
This isn’t a hypothetical. North Korea uses a version of Linux which does exactly that.
It still doesn’t make these fields inherently dangerous, and that same argument applies to birthDate. Even if systemd build a verification system that required photo identification and a DNA sample it wouldn’t be a problem.
The community would just fork the project before the totalitarianism update. The FOSS world already has a process to avoid massively unpopular changes. This change isn’t massively unpopular, this is a vocal minority who is stirred up by web articles leveraging clickbait and outrage to drive ad revenue.
The age verification laws are unpopular, I’m personally completely against them. However, they do exist and adding an optional field in order to allow project, who choose to do so, to store that data is not a red line or the start of a slippery slope.
In the future, if there was a red line that was crossed, we would fix it with a fork and not with a harassment campaign.
You think you can just make up lies about countries far away from you and no one will notice? Think again, whisu.
Sorry Chairman Kim, congratulations on your 99.8% victory
https://en.wikipedia.org/wiki/Boiling_frog
That’s you. You have no issues giving anyone an inch and then wondering why you’re being lined up on the street afterwards once they’ve taken the mile.
https://en.wikipedia.org/wiki/Slippery_slope
That’s you. You have no issue embarking on a creative writing exercise, painting the scariest possible scenario and pointing at that piece of fiction as if it were reality.
You must be off by a decade. Your reference mentions no OS and Unic was developed around 1970.
Your reference mentions no OS

You want the user to put their age somewhere?
Have a simple script that asks for a number and echos it into a file called “age”. Done.
And they can only run the script if they want to.
I disagree with age verification as well, but attacking a person like this is gross.
This article is all but brigading people into harassing this guy.
No, he chose to do this and deserves all the vitriol coming his way.
If you don’t want people to retaliate for fucking them over, then don’t fuck them over. Simple concept.
Looks like you’re trying to fuck someone over too.
Would you care to post your real name, place of work and the city and state where you live? I mean if you don’t want people to retaliate for fucking them over, then don’t fuck them over.
Or, do you understand the danger of having unhinged people on the Internet paint you as a target?
If I screwed someone over, I wouldn’t be surprised if they did something to screw me back. I don’t start it, but I damn well finish it. The moral of the story is to not screw people over. If he needs to learn that the hard way like so many others, so be it. They shouldn’t have to sit back while they get fucked.
You need to stop projecting your own lack of a spine onto everyone else.
He got a huge amount of criticisms and negative comments from the community while he was working on this on GitHub; look at the comment thread of his implementation on GitHub. Essentially the community was telling him “we don’t want this”. And who are you working for in a FOSS project, if not for the community? Yet he disregarded the comments and went on.
On top of this, he appeared out of the blue with this implementation. He had not made any pull requests to this git before now. Nobody had assigned this task to him.
So the situation is not that this is some employee who was asked to implement something, and did it without knowing what the feedback would have been.
Spreading his face around doctored as if it were a mugshot in a community where people are calling him a traitor and other things is a recipe for someone to be hurt or killed.
This thread isn’t a community discussion about implementing a feature, it’s people trying to whip up a mob to attack a person. It doesn’t matter how much you dislike the field name he added to a JSON document, you don’t stir up a mob that can lead to people getting hurt.
In principle I agree with you, pacific discussion and democracy should be the way to go. But it seems that “discussion” doesn’t lead anywhere these times. Politicians do whatever they like (or what lobbies tell them to do), without checking if the majority of the population really agree with some decisions. A developer does whatever he likes, without bothering about the more or less pacific feedback he gets on github. Nobody really seems to want to have a discussion. Well guess then what the “mob” does at some point: they don’t care about discussions anymore either, and they do as they please too.
I fear that riots will start on a larger scale. Even if the context today is different, the situation reminds me somewhat of what happened with the 1981 riots in Toxteth, in Brixton, and other previous riots. Unjust or misused laws; deafness of authorities about discontent; innocent and not-so-innocent people getting hurt.
A developer does whatever he likes, without bothering about the more or less pacific feedback he gets on github. Nobody really seems to want to have a discussion. Well guess then what the “mob” does at some point: they don’t care about discussions anymore either, and they do as they please too.
It’s pretty cliche but: Two wrongs don’t make a right.
In the FOSS world, there are many ways to handle this kind of situation. A mob-led harassment campaign is not one of them.
If you disagree with how a project is going then you can fork it. LibreOffice disagreed with the direction of OpenOffice and forked it, NextCloud and OwnCloud forked from one another when there was major disagreement.
At no point should volunteer developers have their face plastered on a mugshot and their personal information blasted to a mob of angry people.
Be angry at the politicians and mega corporations who are voting and funding these initiatives, not the developers who are caught in the middle.
No
Keep up the good fight Don Quixote
Yeah, Its is sickening and goes against the spirit of open source. We work around restrictions in creative way to give people the freedom to control their software and have access to the source. We don’t deny people trapped in shitholes with bad laws access to open computing. Force them onto Windows and Apple. I don’t get what is wrong with people these days. They have lost all reason.
Yes, many people can work around the laws in various ways. And some of them can’t. Its not for us to judge. We offer possibilities. Everyone knows many distros will patch this field out. Many will just ignore it like we do the GECOS fields. And where it is unfortunately required it is still going to be better than running Windows. Its completely orthogonal to political participation and fighting these laws.
Those writing boot licking compliance are NOT your friends.
deleted by creator
A spade’s a spade. This is malicious compliance. The law might be the problem here but it’s on us to resist and try to make a change. Every last one of us. After all, the surveillance state workers in China and Russia are all just doing their jobs right?
Why the heck would we ever want a DoB field in systemd, optional or otherwise?
The systemd PR also referred to a flatpak PR who said they had wanted that to allow for parental controls even before the law came. That’s a somewhat reasonable use case, in my opinion.
deleted by creator
Why the heck would we ever want a DoB field in systemd, optional or otherwise?
There is a field for your REAL NAME and LOCATION also. Who would ever want that?
Both of these fields contain way more identifying information about a user than birthDate. Do you feel the same way about them? Because they’ve been in systemd since the beginning.
and the GECOS field (https://en.wikipedia.org/wiki/Gecos_field) containing fields for your real name, work address, which room in the building you work in, your home and office telephone numbers and external e-mail have been in UNIX/LINUX since 1962
This is manufactured outrage, the article is doxxing a person and painting a literal target on their head by photoshopping their picture to look like a mugshot in order to drive traffic for ad revenue.
It’s one thing to be against the laws, I’m against the laws. It’s another thing to personally attack a developer, that’s way beyond anything that is acceptable.
Timing’s a bit shit to add a DoB field don’t you think. I also don’t think you can compare computing in a professional setting in the 1960s to modern day surveillance states. I can also say as a parent there’s only one thing protecting your kid from the internet and its not whatever poorly standardized notion of Linux parental controls that exist today. Only actual parenting can.
As for the developer’s publicly observable commits and the following publicly available criticism of it, you can call it painting a target but I think even that’s a bit of a stretch. What’s most outrageous about the institution that is the United States of America in 2026 is how all of it was even allowed to get so far. So yeah, expect some activism.
I also don’t think you can compare computing in a professional setting in the 1960s to modern day surveillance states.
My point was that the fields themselves are no more dangerous than we make them. The GECOS fields are not a thing that used to exist in the 1960s, they exist in your system in 2026.
My point was that the criticism here isn’t about the field, because there are way ‘worse’ fields that have existed for decades. The criticism is about the law and this is a kind of misplaced activisim. Where it goes wrong is deliberately targeting one person for harassment as if they are the scapegoat for all of these age verification laws.
I can also say as a parent there’s only one thing protecting your kid from the internet and its not whatever poorly standardized notion of Linux parental controls that exist today. Only actual parenting can.
I completely agree. These laws are worthless for their stated goals because, as you’ve said, it is a parenting problem.
As for the developer’s publicly observable commits and the following publicly available criticism of it, you can call it painting a target but I think even that’s a bit of a stretch.
They photoshopped his face on a mugshot like he’s a criminal and in the article they list his full name, job title, place of work and the state and city where he works. They also list his personal blog.
In addition to all of the personal details, the wording and framing of the article make it sound like an after action report on a cyberattack:

Here’s some select quotes. This isn’t about activisim about a law, this is about painting a person as evil, bad, etc (and if you look at the comments in this post, that framing worked.
He hit three separate projects in one week.
Taylor believes what he’s doing is right, which makes him harder to stop than someone acting for money.
The argument is ideological, so persuasion is off the table.
“He’s going to be hard to stop and you can’t persuade him”
The word for what that is sits somewhere past malice, something more insidious:
Taylor already has the resume line and knows the codebase well enough to try again.
“He’s going to do it again!”
This kind of framing against a person is dangerous. If you stir up enough people on the Internet you’re going to stir up some people who are unstable and willing to act on this violent framing.
I agree that the laws are wrong, but this kind of personal attack is far, far more immediately dangerous.
Ask yourself, if it was your picture in the mugshot and your personal address being plastered all over Reddit would you feel safe?
Removed by mod
Yeah no how about fuck that. Politics is personal.
If you’re participating in a lynch mob then I believe you’re responsible for what happens.
If you don’t see a problem with this, please provide us a picture of your face, full name and place of work.
How about you do so first, you who would defend such vile actions.
Ah, so you do understand the danger of having your face and full name made public.
Removed by mod
Have you?
Personally, I do think it’s a useful exercise to decide what your red-lines are when it comes to OS level age verification.
For me: Having a field in a database that could contain my DoB is acceptable. Having a prompt to populate it during first time set up is very concerning. Requiring that data to be validated by a third party is the red line.
If you don’t want to be boiled like a frog, bring a thermometer.
I have two red lines.
- Retaining my personal information.
- Giving it to Peter Thiel.
If I had to give my photo ID to Mullvad to access a VPN, I would do it. I trust they wouldn’t retain it nor give it to Peter Thiel.
NO!
Jesus fucking Christ guys. Regardless of your thoughts on age verification, hunting down someone just for complying with the (currently) rather inoffensive law is nuts.
Posting his face here is absolutely going to get him doxxed, and going to cause someone to actually hunt him down and hurt him.
Focus your anger on the people who actually passed and push for this law. Not the person who drew the short straw and had to implement it.
EDIT: Yeah, this whole discussion is toxic now. Suggesting that someone shouldn’t be lynched for making a change in a piece of software is equivalent to me agreeing with that change. I don’t like the push for age verification. It gives me a lot of stress. But I don’t think some random software developer should be hurt for it.
Reading the room wrong when writing software is not worth a life.
You’re part of the problem and I look forward to the day when you’re ashamed of it.
Regardless of your thoughts on age verification, hunting down someone just for complying with the (currently) rather inoffensive law is nuts.
No one has been hunted down. I’ve not read an article anywhere showing that’s happened, have you? Also, this wasn’t complying, this was being complicit. The law IS offensive, both to ones sensibilities and in that it literally attacks Linux by attempting to criminalize it. No one is taking a life, but maybe educating those in charge of open source projects and employers who work closely with the open source community, that this person should not be granted contributor access to such projects.
Systemd is NOT an operating system provider, so they didn’t have to do absolutely anything.
It was their choice to do what they did, not the law, especially since it won’t be active and enforceable before next year.
Witch hunts are despicable indeed but lets not use that an an excuse to justify what they did.
- He didn’t draw any straw. Nobody asked him to work on such an implementation (or maybe Meta did?).
- In fact, he appeared out of the blue to do this implementation. This was his very first pull request on the Systemd git.
- From the very start he received a huge amount of critical comments from the community on GitHub, while he was working on this. He neglected their criticism and plowed on.
So he already had a warning that the majority of the community didn’t agree on what he was doing. Nobody asked him to. He chose to continue – he could have imagined the consequences.
And the whole context on why and why now he did this is fishy.
Please stop with the personal attacks on open source maintainers.
He didn’t have to do this. If he wants to do his part to make everyone else’s life worse, then he will have to face the consequences for it.
Another collaborator.
Seriously. Lemmy is kinda gross with this stuff.
This change is shit but I’m not a fan of personal attacks on the guy.
Developers are not a protected class. They do not get special social protections when they do ignorant things.
Any criticism should be directed primarily at the laws, not the person who suggested adding a birthdate field to the user.json.
Open source is dependent on volunteers contributing their time. The developers at SystemD have been receiving death threats over this. This article includes his name, face, workplace. I know that information is publicly available but the Geoguessr experts aren’t the people we need to worry about.
He did not just suggest it. He went on and implemented it. All while the community was telling him “we don’t want this”, “stop with this” – look at the comments on GitHub. Yet he neglected all this feedback.
As an open-source volunteer, you work for the community, right? If you go ahead while the community is telling you “we don’t want this”, then whom are you working for?
As an open-source volunteer, you work for the community, right?
- They don’t work for anyone.
- Even if they did, it sure as hell wouldn’t be for you.
- Even if they did work for you, they are under no obligation to even think about breaking the law for you.
Of course there are no obligations and he’s’free to do as he pleases. Likewise, the community or I are under no obligations of not criticizing him for what he chose to do.
This isn’t criticism.
Taking a person, photoshopping their picture to look like a dossier on a criminal and writing a hit piece which includes all of their publicly available information is doxxing for the purpose of harassment.
Lemmy is a small community, read some of the comments in this post and you’ll see people using violent language, calling him a traitor, etc.
I didn’t even have to go far to find an example, literally the comment under my reply:
https://lemmy.world/post/44550728/22802099
A mistake without regret must be punished. They are not kids acting silly. I don’t feel comfortable with a foot on my neck, even when that foot isn’t pressing very hard.
Expand that to the tens or hundreds of thousands of people on Reddit (where this exact article is also posted) and the chances of some crazy person going out and doing harm to this man increases.
This is why public doxxing is wrong and anyone participating in this is morally corrupt.
The correct word is collaborator, btw. Sticking up for him doesn’t look good, either.
Stop trying to make what he did ok. It is not ok.
So maybe next time when someone sees a pull-request like this, they think before merging it?
*provided no one gets hurt. I sympathise with the uproar, but physically hurting the guy is definitely too much
The key phrase is Personal Attack.
If the law was the only thing stopping you doing that, it reflects on you.
This whole article/blog post reads as “How dare this person follow the law. ;(”
I really don’t understand the pushback on this one person for submitting the change request. When it is the lawmaker that put this law into place that we should be criticizing. The post repeatedly uses how the contributer said that the change was “hilariously pointless and ineffective.” As some sort of gotcha as to why the merge should not have been accepted but does not explain why the maintainers should not follow the law other than “law bad”.
It also consistently calls out the various peoples’ places of work and experience as some sort of boogeyman for why they should not be allowed to contribute to open source. If these people were universally accepted to be bad actors in the community then they would not be accepted as reviewers for these projects. This just attacks their character to try to prove a point.
“It’s just a harmless field; what’s the big deal?”
The big deal is that it’s on the heels of age verification bullshit that fascists are pushing through with the help of tech bros, so that they can eventually push all of us into a scenario where we have zero privacy.
It’s not the adding of the field itself or the fact that it can be filled with nonsense. It’s the reasoning backing it.
“But it’s the law!”
Yeah, fucking and…? It’s a stupid mass surveillance law disguised as a protection, and per usual, it’s written like vague dog shit. This is the smallest part of the wedge. More will come of this and if developers like this keep volunteering themselves to help the fascists, we will all be fucked. Here’s an alternative approach: just don’t add this. You can fight back by not fucking implementing this. Easy.
Agreed. To elaborate:
Sure, the developer is a bit of a Judas for complying in advance, but our anger should be aimed at the people with power and reach promoting these laws in the political sphere (the metaphorical Pharisees).
To those saying “it’s just a field”, please consider that the timing is a more significant statement than the addition of the field itself. Why now? If you don’t support fascism, don’t build the frameworks that support it and don’t let fascists use YOUR platforms or software to make THEIR point, make them fork it and let them fail. I don’t think many members of the senate or house would be capable of adding this themselves. I’d be surprised if they could code hello world in TI-83 BASIC. If they ask you to do it, stub your toe and call in sick. Make it really shitty. Leave in a bunch of bugs that crash the program then blame the age attestation feature to turn users against it. Use copywrited code that they’ll have to remove later due to license incompatibilities. Report your boss to HR for every indiscretion that you might have normally overlooked. Or do nothing; that’s still better than complying in advance.
We have to break the narrative that this is inevitable. There’s enough of us, with concentrated enough knowledge and influence (aka, you folks are a bunch if nerds and I love it!), that if we collectively stop, the whole train stops or derails.
You don’t understand.
The alternative to device based private attestation which is what this is or could be part of is constant online verification by Palantir.
Is every time you want to view porn or adult content you have to verify your real identity so evil corporations and the government who pays them know exactly what your fetishes are and can blackmail you. So they know exactly what you’re posting online because you have to face-scan and ID-scan to set up an email account, a social media account, any account with anything that allows posting content online. Is training the population not to enter a date for their kids or themselves when setting up a computer or device account for the first time, once but upon demand scan their face, scan their ID, comply, sit meekly in fear because everything they do online is known.
What does this know? Your birthday. That’s nothing. As it stands it you can enter anything you want. Fight them when they come to add a verification system to this and point out parents would be in a position to set this up for their kids anyways and its just spying. Fight on stronger ground.
We’ve already lost the maximalist position. The internet scanning and ID verification has already been enacted in several states and countries and we risk a world where it becomes the norm and hosting companies drop anyone who doesn’t implement it because they’re made liable as well. This stuff won’t be repealed. People don’t live in democracies. They live in a dictatorship of the wealthy and the corporations. Your dissent doesn’t matter and it cannot reach most tech illiterate people who have far more pressing concerns than to riot over this.
This is a compromise solution and I wish more people would see it. If you can bend you don’t break. If you don’t bend and your enemy is the government they are stronger than you and they will snap you like a twig.
Linux desktop market share is too small to matter. And if you make this push fail then the only alternative, the only viable solution these politicians who are being cajoled and urged to implement this will see is online live-scan face and ID verification and it’ll sweep everything. You’ll have destroyed the internet and having saved Linux won’t matter. After that it’ll be a quick move to ban encryption that the government cannot break and ISPs will block traffic they can’t inspect. Game over. A simple maneuver from the place you force them to by refusing to cooperate and enact this compromise, privacy-preserving solution. We need strong defensible positions to protect privacy and the internet and free software and to understand that the old ways have been lost, they’ve died, they’ve been strangled and a compromise position must be taken up to endure and avoid a total loss.
why is it always the .ml users coming in to defend the most tyrannical shit ever while claiming we dont truly understand it
Finally a sane take.
To take things further this whole outrage reads as a Karen screaming at a starbucks cashier and threatening to boycott the store because they asked for her name. It’s an overreaction to a minor issue, by someone who overestimate their power, directed at someone who has no real power, while the Palantir surveillance system runs on the cameras behind them.
They can already put it on the parents to verify if they want. Just buy age compliant devices. Stop shilling this nonsense and forcing fear and hopelessness down everyone’s throat. This is bullshit and you know it. We already have a defensible position.
It is defensible in this kind of community, but I doubt it’s defensible in a board voter base. For instance people see billionaires and are saying the government should step in and do something, because as individuals we are somewhat helpless. In this instance we’re like we can fork/we can revert so the government ideally just needs to back off. But if you ask a non-tech savvy voter (and a parent in your example) they will just see big tech and say the government should step in and do something. Has this method of governance been compromised? Sure, is this law an example of that? Sure. But what can we do? The government… Well until people can agree on that, I think we are just trying to find a compromise so that most people can easily dismiss the perspective that parenting tech is too hard. And if people can believe that typing in an age for their child and see big penalties for big tech if they ignore that age, that seems to me the placebo this situation needs.
Am I the only one that is sick and tired of explaining to clueless people why this type of legislation should be shot down. This has been going on since SOPA and PIPA in the US around 2010 or whatever. I feel like I’m blue in the face.
Parents can get child compliant devices if they want. They need to leave our shit alone. How hard would it be to fork a child resistant Ubuntu or have Mac and Windows do it so these Karen’s can protect their own damn kids. But forget the guns and pedophiles running every country in the world. Let’s just fuck with the passions of the FOSS community and open the door for more surveillance.
“But it’s the law!”
I was just following orders!
this same person would be chuckling to themself about how pointless this all is as he locks the door on the gas chambers.
He’s adding age verification for the internet, not sending people to gas chambers. You really need to touch grass, urgently, because clearly your dependence on the internet is not healthy.
manuallybreathing is making an analogy, not saying they’re the same thing.
You really need to read a book and stop projecting on the internet, it can’t be healthy.
Twenty Lessons For Fighting Tyranny
- Do not obey in advance. Most of the power of authoritarianism is freely given. In times like these, individuals think ahead about what a more repressive government will want, and then offer themselves without being asked. A citizen who adapts in this way is teaching power what it can do.
https://www.carnegie.org/our-work/article/twenty-lessons-fighting-tyranny/
THIS! Those that do obey in advance, especially trying to help impose it on the rest of us, are collaborators!!! Treat them as such!
Also, they will use it as a means to lock content they don’t want. Like in some jurisdictions it’s already forbidden to share any kind of LGBTQ information even medical with minors… Even in EU, like Hungary. Clearly this age verification will be used for this too. And people not willing to age verify will be locked out too.
It’s part of their campaign of forcing conservative ‘values’ onto everyone.
wasting 32 or 64 bits for absolutely no reason is also pretty offensive in itself
wasting 32 or 64 bits for absolutely no reason is also pretty offensive in itself
Storing 64 bits, in this hard drive economy? smh
More will come of this and if developers like this keep volunteering themselves to help the fascists, we will all be fucked. Here’s an alternative approach: just don’t add this. You can fight back by not fucking implementing this. Easy.
Only thing you get out of this compared to the alternative of malicious compliance is opening yourself up to attack. You can still fight this without painting a big target on your back.
Defenders and writers of the evil code are the ones being targeted. You have this backwards and need a mirror.
Is there any evidence that they would go after random FOSS projects that aren’t hosted or developed in the relevant jurisdictions? Don’t comply in advance.
Yep, then using linux will be illegal, great fucking idea boss
You’re welcome to be a spineless muppet trying to obey unethical laws, but I won’t be.
Nope, I am a muppet whose livelihood depends on them respecting the law. If you are from one of the godforsaken regions doing stupid laws you should vote against them, I need to comply with your laws because I need to work to feed my family.
You can call me a spineless muppet all you want but I am not the cause stupid laws exists, take it on the californianas for that crap, they elected the idiots doing this. I vote our own idiots and until now they made it clear this bullshit is not on their table, thank you wery much but I did my part.
Another collaborator, “just following orders.”
“then you should vote against them”
Oh you think they asked if they could implement these? And btw, it’s coming to your country soon too. This is a global movement
Then i sure hope linux will not be illegal in my country too
Only in California and Brazil. And I suspect neither has a shortage of people able to add this field.
Exactly, make your own fascist distro with a fork of systemd and leave the original landscape alone
Then he said Arch Linux should implement it anyway because the law requires it. archinstall PR #4290
Well, it’s not “the law”, it’s your local law. To most people on the planet, it doesn’t apply any more than for example North Korea’s laws. As far as I can find, Arch Linux is not owned by a foundation or similar legal entity (i.e. which could have been located in California), but the lead developer appears to live in Germany.













