• BartyDeCanter@lemmy.sdf.org
    link
    fedilink
    English
    arrow-up
    1
    ·
    edit-2
    18 hours ago

    But it actually does require that. Read section 1798.502.b. Every developer of every application has to ask for your age bracket through this mechanism. The open source developers behind ‘ls’, ‘cp’, ‘rsync’ are all suddenly required to ask my age category of face a $2500-$7500 fine per time my kids run apt upgrade. That is utterly absurd.

    Hell, I’m suddenly liable if a kid downloads my pong example project that I put up on crates.io or PyPI?!?

    • Archr@lemmy.world
      link
      fedilink
      English
      arrow-up
      1
      ·
      16 hours ago

      Yea they have to ask for your age bracket. That’s not the same as an ID.

      I agree, the definition of an application is much too broad. And should be revised. But the difficulty is how do you restrict it without also creating a multitude of loopholes for businesses to exploit. At the very least we should restrict it to applications whose primary purpose is to interact with the internet.

      And before you say it, yes I am aware that that still leaves many apps like curl, wget, ssh being covered. But it could be a start.

      Or maybe just restrict it to social media applications. I am not a lawyer, I definitely don’t have a great grasp of how to create the type of language that is appropriate for laws.

      • BartyDeCanter@lemmy.sdf.org
        link
        fedilink
        English
        arrow-up
        1
        ·
        16 hours ago

        But why are you even accepting this something like this should exist? What is the threat model that this is protecting against? How would it offer any protection against that threat? Why should everyone who is making any program need to ask about the age of their possible users?