They seem to be ready for this:

> Q: What if the AG actually fines you?

> Then we will have accomplished something no amount of mailing list discussion could: a court record establishing what AB 1043 actually means when applied to the real world. Does "operating system provider" cover a bash script? Does "general purpose computing device" cover a Raspberry Pi Pico? Can you fine someone "per affected child" when no mechanism exists to count affected children? These are questions the legislature left unanswered. We'd like answers. A fine would be the fastest way to get them.

I am predicting it now: They will not be sued or fined.

The truly aggravating part is that if they really wanted to thumb their noses at the Attorney General's office and get away with it there's a pretty straightforward way to do it: Fork every single project they want to offer through their operating system and thereby become a first-party developer-distributor thereof. AB 1043 is worded in such a way that it really doesn't apply if the operating system developer doesn't provide a covered application store (see 1798.501(a)(1)). This should apply in every other such app store accountability act in every other state (save Texas, since this is the text they seemed to adopt after the Texas law was challenged). Instead, all they're going to accomplish is getting pimpslapped by the Attorney General's office.

Maybe they're interested in performative noncompliance, but I'm not. I'd rather engage in creative and effective noncompliance.