There’s a lot that can be said about the ineffectiveness of age gates or the problems of rating systems but those are better directed at legislators rather than open source maintainers working to ensure that distros are in legal compliance with flawed legislation by the deadline, especially with regards to laws like New York’s with serious privacy issues and that are pretty much unworkable by any open source projects
And also a lot to think about in terms of why educating parents is ineffective and the nature of the societal problems motivating these laws and how to address them in the real world with actual parents

@erincandescent default date, 1/1/1970
If there absolutely have to be a date there, also hoping for an ISO date, 1970-01-01
@erincandescent @trwnh Besides, Guix provides a hint of the solution for this.
The binary bootstrap seed.
Distribute everything as text, speech, that is to say, and provide the bootstrap as an image or shirt or something.
Then provide a very minimal boot image the user can use to enter the seed manually and overwrite the start of a disk (a very old school kind of editor isn't it?), with the next partition over (or a USB disk) containing the source for everything else, and now the blocking of such a distribution is a Free Speech issue.
UEFI provides most of the tooling necessary to make this require an absolute minimum object code (little enough to be auditable reasonably without source if need be).
@seachaint systemd maintains a standard for a user database format, because /etc/passwd is incredibly limited and lacking many fields you might want to store on a modern system.
It contains optional fields like a user’s e-mail address, “real name”, or details like identifiers of security tokens they might wish to use to unlock their account.
In this case they’re adding a definition of a dateOfBirth fields to a JSON map, and nothing more. In particular you will not find any particular age confirmation method here; it’s entirely up to self reporting by the system administrator(s)
@jripley @seachaint it could be in a separate package called userdbd and you’d be complaining that Lenart’s 30 interconnected packages were taking over the Linux system 🤷
It’s not even actually a user database, it’s a replacement/alternative for the NSS interface that lets you query various properties of a user that multiple backends can plug into including several external backends (I’ve written my own! It’s trivial!) and several backends that e.g. provide synthetic users inside the systemd package itself.
@jripley the thing is that these things can’t be disentangled. One of the userdb backends is provided by pid1 itself, for example (to support the DynamicUser feature)
It’s very difficult to disentangle these things because so many of the things systemd touches are cross-cutting concerns that affect the whole system, and the reason it keeps touching them is that having them historically spread across so many packages has ossified so they are stuck in the 70s
@navi @jripley which is exactly an example of how you can just take the userdb interface and reimplement it.
I don’t know what point you’re making. They could have implemented it in a separate project? Sure, at the cost of circular dependencies (systemd -> userdbd or at least the protocol definition -> libsystemd), or you split it into more projects and now you’re continually having to do commits across 7 separate repositories to implement simple features, bumping dependencies all the way.
You don’t like the implementation choices, you can reimplement it. Heck I’m pretty damn sure that systemd would work perfectly with gardnerdb (as long as you let pid1 itself provide the io.systemd.DynamicUsers service as it needs to do)
@erincandescent "only ever going to be filled in on the machines of children administered by parents who want such restrictions enforced"
You say this as if it's not a huge problem in itself. We should not be building or shipping tools for abusive parents to use to surveil or control their children.
@erincandescent That doesn't justify being part to it and essentially forcing distros to ship an abuse-mechanism unless they actively patch it out (thereby having to make a highly charged political statement).
Yes a determined parent with technological know-how can always find a way to put such malware onto their child's machine. We should not be making it an out-of-the-box feature of "Linux".
RE: https://social.treehouse.systems/@mgorny/116274748222570834
@erincandescent Combined with other things, yes. See for example:
@erincandescent Right now, there is no standard place for a DOB field to be stored or for applications to know how to access that information or use it to enforce rules blocking access to information.
By creating standard places to store it and standard APIs to access it, you setup the infrastructure needed for these abuses to be something available out-of-the-box rather than requiring a ton of custom hackery by the abuser to setup.
@dalias i’m not sure what your actual argument is here.
Is it
@erincandescent @dalias that's fine, but don't make it easier for evangelicals to murder people along the way.
btw, when you say CNC I assume you don't mean computer numerical control, unless you want to block access to all of the precision machining content on YouTube.
@erincandescent @emma Nobody "accidentally wanders into pornography". That's an excuse.
If you're really worried about this, you mandate that porn sites have a splash page that says "this is a porn site. what you're about to see is sexually explicit. do you want to continue?"
Children who are not actually looking for porn are going to hit the back button stat.

@erincandescent None of the above.
My position is not that there is nothing harmful on the internet, but that for both fundamental reasons and reasons of political capture by people who wish harm to any children who are not straight cis neurotypical, any attempt to gate access to information will both block critically important non-harmful things and fail to block the most harmful things.
I could go into my views on how parents should deal with these truths, but I don't believe that "how else are we supposed to PrOtEcT tHe ChIlDrEn??????" is relevant.
Protecting children is not on the table here.
Doing harm to children and harm to people who need to be anonymous are what's on the table.
@robryk @dalias One of the things I see being discussed on the xdg-desktop-portal pull request is that the Age Verification service will provide the minimum viable API required to comply with the California/Coloradan/etc law, and that an entirely separate API would allow queries around specific content descriptors which would allow a much more capable decision system.
(In fact you could imagine such an API providing a way for you to configure for yourself that you don’t want to see certain things or that they should be hidden by default)
@robryk @erincandescent No, the direction we've always had is that *nobody has control* except someone who's hovering over them.
Government - pushed by industry, who wants to shed legal liability for the harms they are encouraging and amplifying on their platforms - is attempting to force us to participate in building a system of parental controls that's always there.
On top of that being bad enough in itself, it's a requirement they could change into "governmental controls" whenever they like.
@erincandescent @robryk Seriously? You think this agenda just popped up worldwide all the sudden without someone funding it all? 🙄
The receipts purporting to pin it on Facebook haven't been verified yet, but I thought it was widely understood that they're doing this to avoid blanket bans, hoping instead of herd underage users onto reduced-harm versions of their platforms while keeping all the maximal-harm stuff in place for adult users.
@dalias @robryk This popped up all of a sudden? It’s been building slowly for years now. It’s a long term political trend if you read the news.
I don’t think social media bans will actually do anything useful. I also think that it’s hard to think of any regulation that would mitigate the real harms here and not just open a different can of worms.
I mean, except for maybe legislating the abolition of Meta Platforms Inc and all associated companies.
@erincandescent @dalias @robryk It's likely less of "we really care about age info" and more "we care about liability and we want biometric data as it's just generally useful"
combined with
"the us government in this particular instance isn't supposed to collect this data and share it widely between departments /but it can buy it from third parties just fine/" kind of silliness
(disclaimer: I work at FB. I have no idea of what's actually going on internally here.)
@dalias @erincandescent The thing I am worried about is when the first bit of software tries to use that API, even when I am located outside of the demanded age restrictions. And it does not really matter if that software is a web browser to provide fingerprinting, a media player to verify that I am not playing an R-rated movie or Steam to collect statistics.
I don't believe/trust this stays opt-in and if I don't provide anything, (1) nothing will complain and (2) nothing will use even the negative information against my will. I don't believe in adding an API that is supposed to not be used based on where I am geographically located.
(And I don't trust an API that emerged as a result of this geopolitical climate.)
I don't want such an API existing on my device, even if “the API itself is harmless” and the harm may come from “just” from the applications that utilise it.
@ledoian @dalias it’s Linux, you’re root, you can just change the code to simply lie or do whatever you want, you have that capability.
Unless someone legislates that you can no longer actually control your own computer (and yes, people are trying to do that), or systems are legislated to collect some kind of proof but that’s a completely different legislative problem