• 0 Posts
  • 295 Comments
Joined 1 year ago
cake
Cake day: October 16th, 2024

help-circle






  • It’s a reference to Chappelle Show about how Rick James disrespected Charlie Murphy by getting his muddy boots on his white suede couch, and Rick James is like “Fuck yo couch! You’re rich, buy another one! Fuck yo couch!” while spreading mud on the couch. It’s about disrespecting you, but also dismissing complaints rather than actually admit you did anything wrong.





  • This bill, beginning January 1, 2027, would require, among other things related to age verification with respect to software applications, an operating system provider, as defined, to provide an accessible interface at account setup that requires an account holder, as defined, to indicate the birth date, age, or both, of the user of that device for the purpose of providing a signal regarding the user’s age bracket to applications available in a covered application store and to provide a developer, as defined, who has requested a signal with respect to a particular user with a digital signal via a reasonably consistent real-time application programming interface regarding whether a user is in any of several age brackets, as prescribed. The bill would require a developer to 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.

    I’m not sure how this is going to be enforceable. So, in essence:

    • The OS should have an accessible API that returns the age bracket of the user, presumably for the purposes of eliminating a lack of compliance on apps using children’s data for advertising. That’s not necessarily a massive problem, though I don’t like the idea of age brackets, I’d prefer it if it’s just a “Adult” vs “Child” bracket.

    • It doesn’t seem to be asking that the age be verified through some external provider, so simply stating the age of the user is enough.

    • App developers are expected to always request that information on launch/installation, which is simply not going to work because how would you enforce it for software made before this law came into effect?

    • The definition of “covered application store” is way too broad and covers basically anywhere you can download software, including things like public docker hubs or Github, so no that’s never going to work out. Apple and Google can maybe include the request for age brackets and provide that information by default as part of the SDK, but legacy software? Good luck getting WinRAR to request that information. You’ve essentially banned all software made before 2025.

    So… The OS-level stuff isn’t a huge deal, but the requirements on app developers are way too strict and would be unworkable. If I were to re-write the bill, I’d make it so the age bracket must be available at the OS level, but not required by the app developer to actually use it. I would then add more strict requirements on sites to not use children’s data for advertising, with the reasoning being that they could have asked for the age bracket from the OS at any time, and the fact that they didn’t even bother means they actually wanted to use children’s data.