The Engineer Who Tried to Put Age Verification Into Linux
-
@Khrys Please tell me the age of the "root" user?
-
The Engineer Who Tried to Put Age Verification Into Linux
The Engineer Who Tried to Put Age Verification Into Linux
Dylan, useful idiot with commit access, pushed age verification PRs to systemd, Ubuntu & Arch, got 2 Microslop employees to merge it, called it 'hilariously pointless' in the PR itself, then watched Lennart personally block the revert. Unpaid compliance simp.
Sam Bent (www.sambent.com)
The lasting damage was knowing it could happen at all: that a single contributor with no stated organizational backing could submit compliance infrastructure for surveillance law directly into the software that boots your computer, get it merged by two Microsoft employees, and have the creator of systemd personally block the removal.
@Khrys let's kill this guy with hammers. tbh tbh -
The Engineer Who Tried to Put Age Verification Into Linux
The Engineer Who Tried to Put Age Verification Into Linux
Dylan, useful idiot with commit access, pushed age verification PRs to systemd, Ubuntu & Arch, got 2 Microslop employees to merge it, called it 'hilariously pointless' in the PR itself, then watched Lennart personally block the revert. Unpaid compliance simp.
Sam Bent (www.sambent.com)
The lasting damage was knowing it could happen at all: that a single contributor with no stated organizational backing could submit compliance infrastructure for surveillance law directly into the software that boots your computer, get it merged by two Microsoft employees, and have the creator of systemd personally block the removal.
@Khrys this is why Lennart isn't allowed to submit code to the kernel
-
The Engineer Who Tried to Put Age Verification Into Linux
The Engineer Who Tried to Put Age Verification Into Linux
Dylan, useful idiot with commit access, pushed age verification PRs to systemd, Ubuntu & Arch, got 2 Microslop employees to merge it, called it 'hilariously pointless' in the PR itself, then watched Lennart personally block the revert. Unpaid compliance simp.
Sam Bent (www.sambent.com)
The lasting damage was knowing it could happen at all: that a single contributor with no stated organizational backing could submit compliance infrastructure for surveillance law directly into the software that boots your computer, get it merged by two Microsoft employees, and have the creator of systemd personally block the removal.
@Khrys for someone who uses the phrase "microslop" the whole thing reads like slop -
The Engineer Who Tried to Put Age Verification Into Linux
The Engineer Who Tried to Put Age Verification Into Linux
Dylan, useful idiot with commit access, pushed age verification PRs to systemd, Ubuntu & Arch, got 2 Microslop employees to merge it, called it 'hilariously pointless' in the PR itself, then watched Lennart personally block the revert. Unpaid compliance simp.
Sam Bent (www.sambent.com)
The lasting damage was knowing it could happen at all: that a single contributor with no stated organizational backing could submit compliance infrastructure for surveillance law directly into the software that boots your computer, get it merged by two Microsoft employees, and have the creator of systemd personally block the removal.
-
The Engineer Who Tried to Put Age Verification Into Linux
The Engineer Who Tried to Put Age Verification Into Linux
Dylan, useful idiot with commit access, pushed age verification PRs to systemd, Ubuntu & Arch, got 2 Microslop employees to merge it, called it 'hilariously pointless' in the PR itself, then watched Lennart personally block the revert. Unpaid compliance simp.
Sam Bent (www.sambent.com)
The lasting damage was knowing it could happen at all: that a single contributor with no stated organizational backing could submit compliance infrastructure for surveillance law directly into the software that boots your computer, get it merged by two Microsoft employees, and have the creator of systemd personally block the removal.
Also, #fuckedCompany
" .... name is Dylan M. Taylor, a Senior DevOps Engineer at Credit Genie, a Khosla Ventures-backed fintech startup in Durham, North Carolina."
-
The Engineer Who Tried to Put Age Verification Into Linux
The Engineer Who Tried to Put Age Verification Into Linux
Dylan, useful idiot with commit access, pushed age verification PRs to systemd, Ubuntu & Arch, got 2 Microslop employees to merge it, called it 'hilariously pointless' in the PR itself, then watched Lennart personally block the revert. Unpaid compliance simp.
Sam Bent (www.sambent.com)
The lasting damage was knowing it could happen at all: that a single contributor with no stated organizational backing could submit compliance infrastructure for surveillance law directly into the software that boots your computer, get it merged by two Microsoft employees, and have the creator of systemd personally block the removal.
@Khrys@mamot.fr needlessly dramatic for what was an entirely unsurprising development. wake me up if they do anything beyond a glorified text field, something almost all other OSs have had for decades.
I mean I agree that the sentiment is bad. but do we need the entire linux community to explode over this? hardly
-
I don't understand what the fuss is about. This is exactly the right way to comply with that law: an optional birth date field. You don't want to have to submit an idea to your OS or implement facial recognition, and you certainly don't want to tie account creation to external services for those things, but now parents can fill in the birth date for their kids, and everybody else can ignore it. This kind of thing needs to be in the hands of parents, not external companies.
So I don't really see the problem here.
-
The Engineer Who Tried to Put Age Verification Into Linux
The Engineer Who Tried to Put Age Verification Into Linux
Dylan, useful idiot with commit access, pushed age verification PRs to systemd, Ubuntu & Arch, got 2 Microslop employees to merge it, called it 'hilariously pointless' in the PR itself, then watched Lennart personally block the revert. Unpaid compliance simp.
Sam Bent (www.sambent.com)
The lasting damage was knowing it could happen at all: that a single contributor with no stated organizational backing could submit compliance infrastructure for surveillance law directly into the software that boots your computer, get it merged by two Microsoft employees, and have the creator of systemd personally block the removal.
@Khrys let’s be completely honest here. The choices are:
- Non compliance resulting in everyone complaining that your device is “broken”
- Non compliance (this option)
- Full compliance with outside verification (a horrible option)If a mandated API is made called, then easiest option is just to return “adult” and move on, rather than the millions of people complaining that “it doesn’t work”
I really don’t get what the point of this hit piece is.
-
@Khrys let’s be completely honest here. The choices are:
- Non compliance resulting in everyone complaining that your device is “broken”
- Non compliance (this option)
- Full compliance with outside verification (a horrible option)If a mandated API is made called, then easiest option is just to return “adult” and move on, rather than the millions of people complaining that “it doesn’t work”
I really don’t get what the point of this hit piece is.
@jonathankoren @Khrys The point is that you don’t just give away your freedom because it’s easier. You *at least* say ‘fuck you, make me’ first.
There are way more people for who this is NOT law than for who it IS. So much for the land of the free and the home of the brave.
-
@jonathankoren @Khrys The point is that you don’t just give away your freedom because it’s easier. You *at least* say ‘fuck you, make me’ first.
There are way more people for who this is NOT law than for who it IS. So much for the land of the free and the home of the brave.
-
@Khrys (disclaimer: IANALAIDEPOOTV)
One remark and one comment:
Remark: the title says "tried to", the article says did -- and Poettering blocked a revert.
Comment: in countries where the GDPR applies, the feature appears contrary to article 5 as overbroad, even probably purposeless *per se* ; maybe also contrary to recent European decisions against generalized citizen data collection, too.
-
-
@Khrys is it just me or is the article a bit weird? Weird repetitions, weird (fully animated) graphics and a weird quiz at the end. It smells vaguely like slop, but is it?
@eobet @Khrys Based on the rest of the articles on the platform, the ones I've peeked over are written in a similar style: They are technically true, I'm not sure if the framing is known or even intentional. As if somebody fed research into an LLM, seriously proofread the outgoing article and also generated "top facts" as well as the graphics out of it
-
@eobet @Khrys Based on the rest of the articles on the platform, the ones I've peeked over are written in a similar style: They are technically true, I'm not sure if the framing is known or even intentional. As if somebody fed research into an LLM, seriously proofread the outgoing article and also generated "top facts" as well as the graphics out of it
@eobet@oldbytes.space @Khrys@mamot.fr I'm split on how to tackle the overall situation. This is, effectively, a rage bait and a hit piece violating the ages-old rule of "attempt collaboration and dialog before engaging in conflict" as the stage of trying to educate or letting the PR author explain their perspective is straight up skipped. Possibly this is unknown to the author who just wanted something that attracts attention
-
-
-
I don't understand what the fuss is about. This is exactly the right way to comply with that law: an optional birth date field. You don't want to have to submit an idea to your OS or implement facial recognition, and you certainly don't want to tie account creation to external services for those things, but now parents can fill in the birth date for their kids, and everybody else can ignore it. This kind of thing needs to be in the hands of parents, not external companies.
So I don't really see the problem here.
Say there's a law requiring collection of people's ethnicity. Or of their gender, allowing only two options. Or of their religion. Or legal, government issued names and id numbers. Oh, they're all optional in most jurisdictions and in fact defined in ways that are noncompliant with other laws. But what's the big deal? We'll just add an optional field name to standardize the schema. There's no mandatory mechanism or verification. Just making the data cleaner.
@mcv @Khrys -
-


