Avid PC gamer, Linux convert, SCP fan.

Love Science Fiction, Cyberpunk, post-apocalyptic settings; Fan of the games of the defunct Arkane Studios. Listening to (Power-, Speed-, Thrash-)Metal, Gothic, Deathrock, EBM, Vaporwave, Lo-Fi; Classic and Musicals are fine too. Can’t stand Hip-Hop.

Owned by two cats, recently divorced, blessed with a personality disorder (AVPD) - pensioned (even the state has the opinion I’m a total wreck lol). This causes me to be unable to keep up personal connections and makes me ghost literally everyone, so if it happens to you, sorry in advance.

Chronically online.

Pro GenAI, but Anti-GenAI-Corpos; this technology should be available to everyone, which would only be fair since we all contributed to it. Datasets and Models should be under the jurisdiction of UNESCO, since they are literally the distilled cultural output of humanity.

  • 0 Posts
  • 5 Comments
Joined 7 months ago
cake
Cake day: September 5th, 2025

help-circle

  • Most of the laws aim for social media, so the 2 bit solution should be enough for most legislation. I would propose an “Birthday” field for legislations where an exact date is needed (which shouldn’t be, because it’s allowing every tracker to identify the DoB) and the “2 bits” for the rest. In my country the ages are 16 for drinking beer/voting and 18 for “mature”/hard liquors/tobacco.



  • I am very anti-age-verification laws, because they tend to be pro-identification-laws. But adding a simple field signifying the age of the current user is probably as good as it gets, although i would have preferred a single-bit-solution (of age/not of age) or at max 2 bits (<14, <16, <18, of age). Using this to go after Systemd again is a) not gonna work, because it’s here to stay and b) i am very interested in how others will implement the legal requirements.