Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.debian.devel > #121028

Re: On the unfortunate need for an "age verification" API for legal compliance reasons in some U.S. states

From Aaron Rainbolt <arraybolt3@gmail.com>
Newsgroups linux.debian.devel
Subject Re: On the unfortunate need for an "age verification" API for legal compliance reasons in some U.S. states
Date 2026-03-01 22:50 +0100
Message-ID <MtWPL-4iWf-3@gated-at.bofh.it> (permalink)
References <MtUXE-4hGf-15@gated-at.bofh.it> <MtWwp-4iPk-17@gated-at.bofh.it>
Organization linux.* mail to news gateway

Show all headers | View raw


[Multipart message — attachments visible in raw view] - view raw

On Sun, 1 Mar 2026 22:04:35 +0100
Gioele Barabucci <gioele@svario.it> wrote:

> On 01/03/26 20:48, Aaron Rainbolt wrote:
> > At its core, the law seems to require that an "operating system"
> > (I'm guessing this would correspond to a Linux distribution, not an
> > OS kernel or userland) request the user's age or date of birth at
> > "account setup". The OS is also expected to allow users to set the
> > user's age if they didn't already provide it (because the OS was
> > installed before the law went into effect), and it needs to provide
> > an API somewhere so that app stores and application distribution
> > websites can ask the OS "what age bracket does this user fall
> > into?"  
> 
> Hi, thanks for starting this conversation. The text of the bill is
> quite clear and I think it is easier to read it than to paraphrase it.
> 
> The bill not only imposes obligations on «operating system
> provider[s]» (section 1798.501. (a)) but also on «[application]
> developer[s]» (ibid (b)).
> 
> The main obligation for the developer is:
> 
> > 1798.501. (b) (1) A developer shall request a signal with respect to
> > a particular user from an operating system provider or a covered
> > application store when the application is downloaded and launched.  
> In my reading this means that, at least:
> 
> 1. the developer of `cp` (as in coreutils' `cp`) must add code to
> `cp`, 2. so that `cp` fetches age-related information of the current
> user from the OS,
> 3. every time a user runs `cp`.
> 
> I don't see in the bill's text anything that would exclude the 
> developer(s) of `cp` from the need to at least make a request for
> this age-related information.
>
> (Obviously I'm using `cp` here as a silly example to make a point.)

It's a good point though. One could make an argument that `cp` is an OS
component rather than an application, and I *think* the OS provider
isn't held liable if something that is considered an application fails
to follow the rules properly (though admittedly section 1798.503b
doesn't mention conduct by developers who fail to request a "signal",
it only mentions conduct by developers that do receive a signal, which
raises the question of if operating systems are expected to send
signals to applications that don't request them, and what that would
even look like on a technical level. Given that this is the same bill
that seems to indicate users won't ever be 18 or older, I'm hoping this
was an accident).

--
Aaron
 
> Regards,
> 

Back to linux.debian.devel | Previous | NextPrevious in thread | Next in thread | Find similar


Thread

On the unfortunate need for an "age verification" API for legal  compliance reasons in some U.S. states Aaron Rainbolt <arraybolt3@gmail.com> - 2026-03-01 20:50 +0100
  Re: On the unfortunate need for an "age verification" API for legal  compliance reasons in some U.S. states "Vincent F. Heuser Jr." <vheuser@heuserlawoffice.com> - 2026-03-01 21:40 +0100
    Re: On the unfortunate need for an "age verification" API for legal  compliance reasons in some U.S. states Aaron Rainbolt <arraybolt3@gmail.com> - 2026-03-01 21:50 +0100
      Re: On the unfortunate need for an "age verification" API for legal  compliance reasons in some U.S. states "Vincent F. Heuser Jr." <vheuser@heuserlawoffice.com> - 2026-03-01 22:50 +0100
      Re: On the unfortunate need for an "age verification" API for legal  compliance reasons in some U.S. states Aaron Rainbolt <arraybolt3@gmail.com> - 2026-03-01 23:20 +0100
      Re: On the unfortunate need for an "age verification" API for legal  compliance reasons in some U.S. states Jamie Null <lav@lavender.earth> - 2026-03-01 23:30 +0100
      Re: On the unfortunate need for an "age verification" API for legal  compliance reasons in some U.S. states "Vincent F. Heuser Jr." <vheuser@heuserlawoffice.com> - 2026-04-06 21:20 +0200
  Re: On the unfortunate need for an "age verification" API for legal  compliance reasons in some U.S. states David Edmundson <david@davidedmundson.co.uk> - 2026-03-01 21:50 +0100
    Re: On the unfortunate need for an "age verification" API for legal  compliance reasons in some U.S. states Aaron Rainbolt <arraybolt3@gmail.com> - 2026-03-01 22:00 +0100
  Re: On the unfortunate need for an "age verification" API for legal  compliance reasons in some U.S. states Aaron Rainbolt <arraybolt3@gmail.com> - 2026-03-01 22:30 +0100
  Re: On the unfortunate need for an "age verification" API for legal  compliance reasons in some U.S. states Gioele Barabucci <gioele@svario.it> - 2026-03-01 22:30 +0100
    Re: On the unfortunate need for an "age verification" API for legal  compliance reasons in some U.S. states Aaron Rainbolt <arraybolt3@gmail.com> - 2026-03-01 22:50 +0100
  Re: On the unfortunate need for an "age verification" API for legal  compliance reasons in some U.S. states Stephan Verbücheln <verbuecheln@posteo.de> - 2026-03-02 08:10 +0100
    Re: On the unfortunate need for an "age verification" API for legal  compliance reasons in some U.S. states Aaron Rainbolt <arraybolt3@gmail.com> - 2026-03-04 01:40 +0100
  Re: On the unfortunate need for an "age verification" API for legal  compliance reasons in some U.S. states Henrik Ahlgren <pablo@seestieto.com> - 2026-03-02 08:20 +0100
  Re: On the unfortunate need for an "age verification" API for legal  compliance reasons in some U.S. states Aaron Rainbolt <arraybolt3@gmail.com> - 2026-03-04 01:50 +0100
  Re: On the unfortunate need for an "age verification" API for legal  compliance reasons in some U.S. states Moritz Schlarb <moschlar@debian.org> - 2026-03-04 09:10 +0100
    Re: On the unfortunate need for an "age verification" API for legal  compliance reasons in some U.S. states Soren Stoutner <soren@debian.org> - 2026-03-04 23:50 +0100
  Re: On the unfortunate need for an "age verification" API for legal  compliance reasons in some U.S. states Aaron Rainbolt <arraybolt3@gmail.com> - 2026-03-06 02:50 +0100
  Re: On the unfortunate need for an "age verification" API for legal  compliance reasons in some U.S. states Aaron Rainbolt <arraybolt3@gmail.com> - 2026-03-10 03:20 +0100
  Re: On the unfortunate need for an "age verification" API for legal  compliance reasons in some U.S. states Lucas Holt <luke@foolishgames.com> - 2026-03-10 03:50 +0100
  Re: On the unfortunate need for an "age verification" API for legal  compliance reasons in some U.S. states Artur Manuel <amadaluzia@disroot.org> - 2026-03-10 04:40 +0100
  Re: On the unfortunate need for an "age verification" API for legal  compliance reasons in some U.S. states Jamie Null <lav@lavender.earth> - 2026-03-11 05:20 +0100
    Re: On the unfortunate need for an "age verification" API for legal  compliance reasons in some U.S. states Otto Kekäläinen <otto@debian.org> - 2026-03-25 02:20 +0100
      Re: On the unfortunate need for an "age verification" API for legal  compliance reasons in some U.S. states Aaron Rainbolt <arraybolt3@gmail.com> - 2026-03-25 02:30 +0100
        Re: On the unfortunate need for an "age verification" API for legal  compliance reasons in some U.S. states Simon Richter <sjr@debian.org> - 2026-03-25 11:30 +0100
      Re: On the unfortunate need for an "age verification" API for legal  compliance reasons in some U.S. states Pierre-Elliott Bécue <peb@debian.org> - 2026-03-25 13:10 +0100
        Re: On the unfortunate need for an "age verification" API for legal  compliance reasons in some U.S. states Bastian Blank <waldi@debian.org> - 2026-03-25 14:00 +0100
        Re: On the unfortunate need for an "age verification" API for legal  compliance reasons in some U.S. states Pierre-Elliott Bécue <peb@debian.org> - 2026-03-25 14:00 +0100
        Re: On the unfortunate need for an "age verification" API for legal  compliance reasons in some U.S. states Jeremy Stanley <fungi@yuggoth.org> - 2026-03-25 17:00 +0100
        Re: On the unfortunate need for an "age verification" API for legal  compliance reasons in some U.S. states Alexandru Mihail <alexandru.mihail2897@gmail.com> - 2026-03-25 20:50 +0100
          Re: On the unfortunate need for an "age verification" API for legal  compliance reasons in some U.S. states Rob BC <kardain@mailfence.com> - 2026-03-26 03:20 +0100
            Re: On the unfortunate need for an "age verification" API for legal  compliance reasons in some U.S. states Simon Richter <sjr@debian.org> - 2026-03-26 04:00 +0100
  Re: On the unfortunate need for an "age verification" API for legal  compliance reasons in some U.S. states Aaron Rainbolt <arraybolt3@gmail.com> - 2026-03-17 00:40 +0100
  Re: On the unfortunate need for an "age verification" API for legal  compliance reasons in some U.S. states Toni Mueller <toni@debian.org> - 2026-04-06 17:50 +0200

csiph-web