Someone Forked Systemd to Strip Out Its Age Verification Support

The project removes the birthDate field systemd added last week in response to age verification laws.

It's FOSS
@itsfoss the headline is misleading, systemd did not add age verificiation support: https://blog.bofh.it/debian/id_473
systemd has not implemented age verification

@jxvvt @itsfoss There seems to be more concern about this than what you're asserting is being done by 'Nazis' here.

Why should systemd have this field at all? Why is it necessary?

@clonedhuman @jxvvt @itsfoss they already have your real name, email, room number and phone number, so why not also bithdate?
Ah and of course you can just not put any data into those fields just as it is today 🤷🏼‍♂️😁
@clonedhuman @jxvvt @itsfoss I'd bet that because user sessions are handled by logind, and that is a natural place to keep data about the user.

@jxvvt @itsfoss
this is slightly more complicated.

one uploader did introduce a age patch, and it got approved,

systemd reverted those changes.

itsfoss should do better reporting though.

my disclaimer: age verification is still a bad idea.

https://www.sambent.com/the-engineer-who-tried-to-put-age-verification-into-linux-5/

https://github.com/systemd/systemd/pull/41179

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
@zetabeta @jxvvt @itsfoss The age field addition was merged. You linked the reversion which was closed. It's definitely still in there. Please follow up.
@jxvvt @itsfoss
short and correction:
revert has been blocked, not the changes. birth date field is in systemd. my mistake.
@jxvvt Respectfully, that is incorrect. The latest PR to revert the addition of DOB field was blocked by Poettering and locked while he hides behind the corporate fig leaf of 'still deciding'. Still deciding, while the hated functionality is being added by his minions.

While on the subject, Canonical has a flurry of PR's merging compliance in advance with these surveillance laws whilst spokespersons from Canonical deny it's their devs and also hide behide the corporate fig leaf of 'still deciding' as the functionality is merged anyway.

It's quite clear the giant US defence contractor known as IBM/Redhat is leading and Canonical is capitulating .. as usual.

* Poettering is technically employed by M$ these days but he is deeply associated with IBM/Redhat.

@itsfoss so they're going to maintain that fork or is this just for show? What a shit show.
@itsfoss good for them but it’s end goal = sysops are stuck with sysd. Fork harder; devise something sane.

@itsfoss

A systemd fork has set out as a fu*k you to age verification.
Good
Better: use a NO Systemd distro.

antiX-26 comes with runit, sysVinit, dinit,
s6-rc and s6-66

s6-rc my favorite, boot and shutdown very fast and reliable.

@itsfoss Let’s see how fast someone secretly associated with M$ or Meta etc will try to commit a malware functionality to defame it.
@itsfoss I can already in my mind’s eye see the title… “malicious code found in the liberated systemd fork… better stick with the original project (they promised the ageID API will be optional and easily disabled…)
@itsfoss yeah great, I think the correct response however is to start the arduous process of migrating away from systemd-only distros, because this most recent debacle has proved beyond a reasonable doubt that it is in fact cancer
@deutrino @itsfoss It'd be better if distros started migrating away from systemd. Debian for example used to support other init systems, but as of Trixie that's pretty much gone. This needs to be reversed.
@itsfoss damn fucking right.