this post was submitted on 02 Mar 2026
654 points (97.3% liked)
Technology
82227 readers
4585 users here now
This is a most excellent place for technology news and articles.
Our Rules
- Follow the lemmy.world rules.
- Only tech related news or articles.
- Be excellent to each other!
- Mod approved content bots can post up to 10 articles per day.
- Threads asking for personal tech support may be deleted.
- Politics threads may be removed.
- No memes allowed as posts, OK to post as comments.
- Only approved bots from the list below, this includes using AI responses and summaries. To ask if your bot can be added please contact a mod.
- Check for duplicates before posting, duplicates may be removed
- Accounts 7 days and younger will have their posts automatically removed.
Approved Bots
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
From TFB:
First, from the LEGISLATIVE COUNSEL'S DIGEST
That's not an encouraging start. Of course, that's not the bill itself just the official summary, so we will need to dig in deeper.
At the beginning of the bill proper, there are some definitions, emphasis mine.
Section 1798.500
There are no business threshold or network capability requirements for the application (though there is one for the computer, sorta). It's simply anything that may run on a computer. 'ls' definitely qualifies as an application per this definition. This is a pretty reasonable definition of 'application', even if it is a bit circular. We could also have quite a conversation about what counts as a “other general purpose computing device”, but it isn’t defined here.
PyPI, a Debian mirror, crates.io and GitHub qualify as a "covered application store". Pip and cargo are an "software application" that "distributes and facilitates the download of applications from third-party developers to users of a computer" so they are as well. Depending on case law curl, rsync and scp might also, though the 'distributes' qualifier may exempt them. Oddly, browser add-ons are probably exempt due to (e)(2). And there may be a grey area around things like VMs. A purely personal website that only has software developed by that person probably doesn't qualify due to the 'third-party' qualifier. Again, there is no business threshold listed.
Again, a fairly straightforward definition, that would apply to anyone who maintains any "software application that may be run or directed by a user on a computer, a mobile device" per 1798.500.c.
So, we've got that developer is a simple definition that basically matches what one would expect, as does application. Covered application store is probably broader than one would expect, and has an odd carve out, but covers most modern software distribution channels. I guess it might not cover sending CDs in the mail.
Then we get to a single simple sentence:
Section 1798.501
It's a really simple sentence that can be really easy to gloss over. But read it again. Maybe you could argue that it only applies the first time an application is run. But it absolutely applies when it is downloaded. There are no exceptions listed, no threshold tests, no "social media applications only". This applies to all applications, all developers, and all "covered application stores". Now CA jurisdiction doesn't cover downloads from outside of CA, but it does cover anyone downloading something inside of CA, or someone living in CA. So if a kid in CA downloads something from a outside of CA, the developer is in violation even if they are outside of CA. CA may not have the resources or desire to track down every developer outside of the state, but if they so choose they would be able to file a claim in the same way that CA can file claims on foreign people who violate other laws that involve CA victims, such as fraud.
Finally, there is this bit: 1798.504
So, it looks like it doesn't apply to CDs in the mail.
Edit:
Of course, I forgot to talk about the penalty. Maybe there is something in there?
1798.503
Nope, no exceptions or commercial clauses. It just applies to anyone. And paragraph b?
Well, an OS provider or covered application store isn’t responsible for someone lying to them, tech failures, or the actions of a rogue developer. But developers have no such waiver.