

is it really still the same system if it’s a radically divergent userland? (see: android as a linux distribution)
wiki-user: Aatube
Now mostly on @Aatube@kbin.melroy.org . I use this account as a backup.


is it really still the same system if it’s a radically divergent userland? (see: android as a linux distribution)


Ubuntu has also gotten a lot better and promising in recent years, too.
Except Snap shenanigans. Snap always shenanigans. The Snap pushing is eternal… Though Entrop is right that it’s mostly just a power-user worry.


exactly, users should disable the optional birthDate field
a headless interface is still an interface
being accessible headless is still accessible
Yeah I see your point. I feel like it’s entirely reasonable, though. Like those who went to the PR, they saw something in the news and decided to do something about it with their abilities, throwing aside whether that’s good for a moment. I certainly would not call the optional JSON schema for user records a critical component especially as no existing fields were modified, just new ones.
(And FWIW it’s systemd, very different from the kenrel, though I do feel like you know what you meant to talk about. systemd’s code quality is relatively notorious anyways.)


Your point is true, but I’m saying its impact is also optional.
Coming out of nowhere just for this contribution is hecka sus though.
I’m fairly sure this is the first systemd pull request that many here have viewed. I wouldn’t say we’re coming out of nowhere.


That is the purpose, but the field is implemented as optional and modifiable with admin privileges.


ever wonder why every coin says “liberty” in some random spot? the coinage act of 1792 mandates that all coins must depict liberty because the US framers did not like “too monarch-like” effigies, so the people in the 1900s just called it a day by slapping onto Amerindians and historical figures the word LIBERTY
/j


(same for the birthDate field)


I agree with you but repeating your arguments in mass replies does not make it stronger.


That’s the Minnesota bill. The PR does not comply with that. You can read on how to the California law and NY and Colorado bills basically say to give the user a drop-down to select their birth date.


I don’t see what’s wrong with implementing it as an add-on to the https://en.wikipedia.org/wiki/Gecos_field as the PR in question does. It’s the most logical place as the location to store user information and is even easier to opt out of—you just edit a file—than choosing whether to compile Linux with/add to DKMS a kernel module.
Edit: One can see https://github.com/systemd/systemd/blob/8878df45c1a58afdfb500fdc53ec50e057a240ce/docs/USER_RECORD_BLOB_DIRS.md?plain=1#L103 for an example of a user record file and its path. Further documentation you can read at https://github.com/systemd/systemd/blob/8878df45c1a58afdfb500fdc53ec50e057a240ce/man/systemd-userdbd.service.xml#L36 and https://github.com/systemd/systemd/blob/8878df45c1a58afdfb500fdc53ec50e057a240ce/docs/USER_RECORD.md .


nah as an anarchist i am against silence. i’m just saying that in our capitalist society open source maintainers do not in fact have responsibility to the community, only to their market share, and this works slightly less dysfunctionally than proprietary because come what may the opposition may fork it. but that and the transparency and the ability to volunteer your labor for them are the only things that open source does guarantee.


Test your understanding of the Dylan Taylor age verification story and what it reveals about open source infrastructure
I’m very suspicious of whether one would create 10 questions for nearly every blog post of zirs by hand.


I think what ze’s saying is https://mikemcquaid.com/open-source-maintainers-owe-you-nothing/ . the nature of open source—atl in accord with the hacker ethic—is that everything is just a passion project, there is no responsibility to not make bad decisions, and bad decisions result in decreased adoption and lost trust. after all, open source has always been about making a new alternative because existing solutions are bad.


not even said laws have an expectation that the date of birth provided would be accurate. the colorado bill just says “require[] an account holder to indicate” and never defines “indicate”, the ny bill says “request an age category signal” and never defines “signal”, so i assume they’re like the california law which has been verified to be just “enter your date of birth in this text field/dropdown and we’ll trust you girl”. i don’t think any of that involves biometrics
there’s no alien intelligence or protocol specification in systemd that ensures or says the dob field must be accurate either
Debian as more mainstream than Arch?