BartyDeCanter

Sorry, I see that I was unclear.

Yes it fucking does require sending the data somewhere, specifically to every "application store", which by their definition includes such things as Github, PyPI, Crates.io, Debian mirrors, apt/rpm repos, and personal websites that have hobby projects from more than one person.

Except that’s not all it is.

Go read the bill, particularly section 1798.501.b, 1798.502.a and b. Every developer of every application that can be downloaded from every package system MUST request your age bracket every time it is downloaded. And possibly every time it is launched. Basic utilities like ‘ls’ and ‘cat’, that pong example I pushed as a test two weeks ago, everything.

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?

In addition, the law requires that every developer of every application, commercial, FOSS, student, hobbiest, professional, or whatever verify the age bracket of every person who downloads and runs their program every time. Every time it is downloaded, every time it is run. Yes an API for this would be trivial to implement, but that’s not the point. The point is why the fuck should I have to face a $2500-$7500 fine every time some kid downloads my pong demo? Why the fuck should PyPI, GitHub, or crates.io have to get the age bracket of every user? Why should every apt request include an age flag? Because that is what the bill requires.

Personal: DOS -> Win3.1/95 -> BeOS -> WinXP -> MacOS -> Win10 -> Ubuntu -> Debian

There was definitely some dual booting in there, particularly in the BeOS (to Windows for Games) and Win10 (to Ubuntu for work) eras.

Professional: Debian -> RHEL -> WinXP -> Win7 -> Ubuntu -> gLinux/ChromeOS -> Ubuntu -> MacOS -> Ubuntu -> MacOS/Ubuntu

I had a college professor that I worked for who was basically the Emacs Enthusiast. So I gave it a try, learned about a half dozen commands and never really moved past that. Later, I was told to give vi a try, so I did and had basically the same experience. Built-in discoverability is/was non-existent for them and I never had a real need to pick up any more or spend hours reading man pages to figure them out. Time past, I went through a few different phases of GUI text editors/IDEs but could always pull out just enough vi or emacs commands when I needed. I did see my colleagues and friends who were all in on vim/emacs with 1000 line configs and thought they looked pretty cool, but I just didn't have the time or inclination when I could be doing other things.

Then in the last year I needed to go all in on a text mode editor for a variety of reasons. I looked around, gave Helix a try, and loved it from the beginning. My few vi commands worked, there is actual discoverability built in, and the select->action grammar makes way more sense to me than the others I've tried.

Helix is not as extremely customizable or configurable as vi or emacs (yet, plugin system coming soon(tm) ) but it has a good default out-of-the-box configuration, enough configuration options for what I want, good lsp support, and discoverability.

Hiding the file system is Good Actually because…

Phones have always been locked down, all the way back to when you could only use a phone that AT&T sold you attached to a landline.

Basic cell phones were generally very locked down, or at least there was no documentation on how anything worked. I do remember using a photo and contact syncing tool that had the protocols for a bunch of “feature” phones reverse engineered. IIRC the dev gave up because he kept getting sued because the phone manufacturers and carriers made money off of charging for that.

When smartphones came around, Android was actually very open. My first Droid was completely open, no need to even unlock anything. Applications could be installed and run from anywhere, including the SD card. Custom ROMs were common and easy to install.

But the carriers were not happy, due to the proliferation of malware running on their networks and a general fear of hackers. Plus the “Hey, we want to charge for that like we do on the feature phones!” Back then, the carriers were all powerful because they could and would kick out any device they wanted. Users were also pretty unhappy due to the lack of security and malware. So they started by adding a boot loader lock and eventually locked down more and more.

The iPhone was locked down from the beginning. It was seen as more of an iPod or other accessory device by most people, so no one really cared.

And, that’s basically been it.

Really, the fact that PCs are as open as they are is pretty amazing and mostly due to different companies reverse engineering each other and a lot of court decisions. I’m sure looking back that IBM really wishes that their cases had gone differently.

I think I managed to skip the ndiswrapper era. I was using Ethernet on desktops and my laptops were Macs. Nowadays my desktop has both wifi and Ethernet, and my laptops run Linux but nmtui just works.

From TFB:

First, from the LEGISLATIVE COUNSEL'S DIGEST

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. This bill would punish noncompliance with a civil penalty to be enforced by the Attorney General, as prescribed.

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

(c) “Application” means a software application that may be run or directed by a user on a computer, a mobile device, or any other general purpose computing device that can access a covered application store or download an application.

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.

(e) (1) “Covered application store” means a publicly available internet website, software application, online service, or platform that distributes and facilitates the download of applications from third-party developers to users of a computer, a mobile device, or any other general purpose computing that can access a covered application store or can download an application. (2) “Covered application store” does not mean an online service or platform that distributes extensions, plug-ins, add-ons, or other software applications that run exclusively within a separate host application.

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.

(f) “Developer” means a person that owns, maintains, or controls an application.

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

(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.

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

(f) This title does not apply to any of the following: (3) The delivery or use of a physical product.

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

 (a) A person that violates this title shall be subject to an injunction and liable for a civil penalty of not more than two thousand five hundred dollars ($2,500) per affected child for each negligent violation or not more than seven thousand five hundred dollars ($7,500) per affected child for each intentional violation, which shall be assessed and recovered only in a civil action brought in the name of the people of the State of California by the Attorney General.

Nope, no exceptions or commercial clauses. It just applies to anyone. And paragraph b?

(b) An operating system provider or a covered application store that makes a good faith effort to comply with this title, taking into consideration available technology and any reasonable technical limitations or outages, shall not be liable for an erroneous signal indicating a user’s age range or any conduct by a developer that receives a signal indicating a user’s age range.

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.

Yeah, the fact that I can wave to a cop walking out of a store where I just bought some pot, but might face massive fines for not doing age verification for a pong game I wrote is insane. I mean, I still want to be able to smoke my pot legally, but I also don't want to have to care about who plays pong.

I definitely remember having to futz with audio a looooong time ago, but honestly getting xf86config to work with my video card and monitor was much more difficult.

Hey! I’m not 50 yet!

Though not far off TBF.