Simon Richter
@GyrosGeier@hachyderm.io
Geek.
9C43253495E4DCA837945F5BEBF67A846AABE354
0
Followers
0
Following
Joined December 13, 2022
pronouns:
he/him
github:
Posts
Open post
In reply to
@GyrosGeier@hachyderm.io
·
1d ago
@EricAlper @lritter a candelava!
0
0
0
0
Open post
@GyrosGeier@hachyderm.io
·
Apr 07, 2026
What I wrote elsewhere about the California age verification law:
If this is meant as a security system, having it default to "fail-open" is insufficient.
The Unix APIs don't have age information. The systemd project has graciously decided that they are willing participants in this, and have accepted a patch to add a dbus API, and subsequently refused to revert that commit. So, dbus API it is.
If I start "env -u DBUS_SESSION_BUS_ADDRESS firefox", does that mean that the browser must pretend that I'm in elementary school and only present "age-appropriate" material, or will it default to "full access"?
Likewise, will curl/wget be required to implement a dbus query? Do we mandate that build chroots now become full containers with a running dbus instance that has an age information service connected, so they can access the entire Internet, or do we allow bypassing the filter by doing a recursive curl/wget download of an URL and then displaying it locally?
The bits that were added to systemd (and which we cannot remove without creating evidence that we mean to disregard the California legislation) are not sufficient for the stated goal, so we must expect that further enforcement infrastructure becomes mandatory.
This entire law assumes that people are using managed infrastructure exclusively, i.e. with an Apple or Microsoft cloud account, and accessing cloud based services.
There is simply no niche for user-managed infrastructure here, because it circumvents all these enforcement mechanisms. I don't even see it being legal for a sixteen year old to be root on their own computer, like it was for me when I started out, because that would give them access to age-inappropriate material, and we cannot have that.
I fully expect that we will soon reach a point where we have to decide between following US or EU law, with no option to remain compliant with both. A requirement to include the user's age bracket in browser queries is already likely to be in violation of EU data protection legislation.
(1/2)
If this is meant as a security system, having it default to "fail-open" is insufficient.
The Unix APIs don't have age information. The systemd project has graciously decided that they are willing participants in this, and have accepted a patch to add a dbus API, and subsequently refused to revert that commit. So, dbus API it is.
If I start "env -u DBUS_SESSION_BUS_ADDRESS firefox", does that mean that the browser must pretend that I'm in elementary school and only present "age-appropriate" material, or will it default to "full access"?
Likewise, will curl/wget be required to implement a dbus query? Do we mandate that build chroots now become full containers with a running dbus instance that has an age information service connected, so they can access the entire Internet, or do we allow bypassing the filter by doing a recursive curl/wget download of an URL and then displaying it locally?
The bits that were added to systemd (and which we cannot remove without creating evidence that we mean to disregard the California legislation) are not sufficient for the stated goal, so we must expect that further enforcement infrastructure becomes mandatory.
This entire law assumes that people are using managed infrastructure exclusively, i.e. with an Apple or Microsoft cloud account, and accessing cloud based services.
There is simply no niche for user-managed infrastructure here, because it circumvents all these enforcement mechanisms. I don't even see it being legal for a sixteen year old to be root on their own computer, like it was for me when I started out, because that would give them access to age-inappropriate material, and we cannot have that.
I fully expect that we will soon reach a point where we have to decide between following US or EU law, with no option to remain compliant with both. A requirement to include the user's age bracket in browser queries is already likely to be in violation of EU data protection legislation.
(1/2)
17
0
8
0
Open post
In reply to
@GyrosGeier@hachyderm.io
·
Mar 19, 2026
1
2
0
0
Open post
In reply to
@GyrosGeier@hachyderm.io
·
Feb 22, 2026
@jguillaumes @cstross I believe not even Lexx:The Dark Zone went there.
0
0
1
0
Open post
In reply to
@GyrosGeier@hachyderm.io
·
Feb 21, 2026
1
0
0
0
Open post
In reply to
@GyrosGeier@hachyderm.io
·
Feb 03, 2026
@shantara @RueNahcMohr two zeroes, so it's NAND GATES in a BGA package, probably with a pinout that allow you to create complex logic with this even on a two layer board.
0
2
0
0
Open post
In reply to
@GyrosGeier@hachyderm.io
·
Nov 22, 2025
@helenczerski @nosfe this is absolutely a thing, but with nail salons.
0
0
0
0
Open post