The default web interface doesn’t do it and the images are not tagged in a way that you could easily fix it with CSS. You could possibly do it with a greasemonkey script (see your local LLM).

I’m here to engage with reality, and not create science fiction scenarios to worry about.

But what if they passed it as a pretext to pass a different law later to kill your nan.

Hot takes and creative fiction is more entertaining than boring reality and that behavior is enforced by social media systems (like likes). It isn’t fun to read ‘they passed a law that’s largely symbolic’ as ‘The end of the Internet is upon us’.

It’s disappointing to see the lack of good conversation around this isn’t due to tool limitations or reddit being terribly moderated, but rather there are a lot of people who genuinely just want to invent stuff to get mad about and if you point out that isn’t what’s happening they’ll just yell slippery nipples the sky is falling!!! Over and over.

Outrage and self-righteousness feel good and appearing cynical is a cheap way to look intelligent.

Alternatively, something like half of social media traffic was shown to be bot-sourced and a goal of adversarial influence campaigns is often to simply stir up conflict so I keep my sanity by believing that a good portion of them are not actual human people, just evil LLMs trying to piss everyone off (and a lot of the rest are simply people who’ve been fooled by the false consensus into aping those same bot tactics and/or literal children)

Some topics, like discussions around AI, are so heavily toxic that I find it hard to believe that it isn’t being signal boosted in some way.

I’ve been slippery sloped already in one of these conversation threads.

Literally nobody: https://en.wikipedia.org/wiki/List_of_the_verified_oldest_people

AFAICT even the oldest unverified person was born in 1900 https://en.iz.ru/en/node/2061564?main_click

Someone in the future may be born before 1900, we can’t know for sure.

Sorry in that case, I’m juggling a few threads

e: lol don’t downvote them! People come to the meme community with no sense of humor, smhing my head.

That’s system76, not systemd.

Yeah oops, I’m just dumb.

Meanwhile systemd already has the commits ready it seems, no questions asked.

Because it’s a trivial addition that was requested by a large user of systemd.

I don’t like these laws either, but they do exist. Go after the politicians who’re making them. Don’t go after the, volunteer, developers for not making a political stand on your behalf.

It’s an optional field, unverified, unenforced and in the worst case, this is open source software so you can simply revert that PR and build it yourself without the extra field or if you feel super strongly about it you can fork the project.

Heaping ire on the development team is the part that I’m taking issue with.

Based on my years of community experience, whichever you pick is wrong and you’re a bad person for thinking that it was the right choice.

Oh yeah, this is totally a can of worms that I don’t think we should be opening.

I just channel that into yelling at politicians, the FOSS devs are on our team they just have to make the best of a dumb situation.

Psh, I use GOS without Storage Scopes. I simply only take flattering photographs of my Adonis-like form (they’re swiping left anyway, smh)

I think the issue outside of capitulation is the matter of systemd’s obligation or lack thereof to make this change.

Most of what systemd does isn’t based on an obligation, it’s based on creating a system that fulfills the needs of the users of the software.

xdg-desktop-portal was adding age verification and the logical place to store that information is in the user’s records. systemd is the project which xdg-desktop-portal looks to for storing user records and so systemd added a field to support xdg-desktop-portal’s requirements.

Like I’ve said elsewhere, I don’t agree with the age verification laws… but they do exist. The software developers in the various projects are attempting to comply with them (or not, as in the OP) in their own ways. Nothing that systemd is doing here will affect you unless you want it to. The field is optional and not verified by systemd in any way (other than ensuring that it’s an ISO 8601-compatible date).

Ultimately the PR was closed and for this very reason:

The contention was that the field would only work for complying with a single state’s law and the data wouldn’t be useful to comply with other laws. For example, if a state defined an adult as 18 and another state defined an adult as 16 then simply storing ‘Adult: [True|False]’ would require individual fields for each legal jurisdiction. So it doesn’t meet the specifications globally.

To fix this, the PR that was merged stores a birthdate and leaves it to the application to determine how to use that information for compliance. Here’s the merged PR:

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

This is something being created in response to laws being passed by politicians, it’s not a secret plot by systemd and distro maintainers to… whatever it is that you’re implying.

This is about as scary as the realName, emailAddress or location fields. They’re completely optional and not validated in any way. You can call yourself Linus Torvalds set your e-mail address to gaben@valve.com and your location to Mars… nothing about the system is going to check or care if you’re lying. Similarly, now you can set your birthdate to April 20th 69BC if you’d like. It doesn’t mean anything.

e: I lied, it has to be ISO 8601 compliant so anybody born before 1900 is ineligible for Linux, smh

I understand the arguments against systemd. It isn’t just an init system and it fulfills multiple roles, which goes against the Unix philosophy.

That being said, systemd does store user information. Since this issue requires the storage of additional user information, in order to comply with the law, the systemd team are making their software compatible with complying with the law.

Ultimately, it’s the end user who gets to determine how the software is configured. You can ignore the birthdate field and systemd will not do anything to prevent you from doing so. systemd doesn’t require the data in order to operate, it doesn’t verify the data and it doesn’t prompt you to enter the data. The consequences of ignoring this addition are exactly zero.

It’s simply there because a law exists and users of systemd (like xdg-desktop-portal) require a location to store the data.

I hate the age verification laws and think they’re going to cause more problems than they claim to solve. I’m not cheering on these laws, I’m simply pointing out that attacking systemd for adding an optional field in order to allow compliance isn’t rational.

Aim the ire at the people making the laws, not the volunteer developers who are following laws even if they don’t like them.

Industrial sites are dangerous and that’s why workers receive safety training and equipment.

These are not intended to interact with the public, they’re intended to replace manned security patrol routes. They’re protected from being a danger to the public by chain link fences and locked doors. The workers who operate them and work around them receive safety training.

In addition to the tens of thousands of dollars of proximity sensors, there’s also a giant red button on their back which shuts them down immediately:

Having robots lets the human workers not go into dangerous situations unnecessarily. Having to patrol inside of an area where halon fire suppression systems are used is inherently dangerous and is more of a common occurrence than having a random untrained and unescorted member of the public enter into a secure area and trip.