@wwahammy @k3ym0

As someone who was once noted on Wikipedia for maintaining a fork of systemd, I think this is a really silly reason for wanting to fork systemd.

@wwahammy @k3ym0

So that's clearly (scumbag) Dylan M. Taylor's intent and belief. But I think it is valid to separate them for the purpose of evaluating folks-other-than-Dylan; I don't think bluca did anything wrong by merging it (nor poettering for lgtm'ing it). I don't think it's valid to say "welp, systemd added age verification, I have to switch to a non-systemd OS now to avoid age verification."[1] I think it's totally valid for bluca and poettering to look at the PR and think "the author's motivation is bad, but this specific change is fine."

"They build the tracks and plead innocence as to what is in the trains." I feel that way about a lot of stuff, but... this is even more removed than that? There's no policy engine. "They approved a standard for the width of train tracks."?

[1]: There are plenty of valid reasons to prefer other init systems, but I don't think "birthDate" showing up in a json schema is one of them.

@wwahammy @k3ym0

So the age verification stuff is beyond terrible. But the systemd PR specifically seems like a weird one to get worked up about?

It does 2 things:
1) The schema-docs for the the userdb JSON, which already allows you to add arbitrary user-defined fields in addition to the pre-defined fields, now define an optional "birthDate" field to be to be a "YYYY-MM-DD" string.
2) Added a flag to `userdbctl` (edit: `homectl`, actually) to be able to set the field from that command, instead of having to edit the JSON some other way.

Like, I already deal with multi-user systems where "hobbies" is a field in there. I don't see the harm in saying "If you wanna add a birthDate field, it should be 'YYYY-MM-DD' and not seconds-since-epoch or something".

The polkit stuff? Makes my gut churn.