License Plates, Vin Numbers clearly available on the dash, Tire Sensors, Bluetooth MAC, WIFI MAC, Cellular IDs for most even if you don’t pay for the service.

It’s an interesting thing to point out, but we’re mostly driving around with much higher power sensors than the pressure sensors.

I already read it. That’s how i came up with what I wrote man.

You go re-read it and tell me

What counts as “minimum”

How necessity is measured

Whether “minimum” refers to data fields, granularity, frequency, or retention

They don’t cover shit about ANY of that.

It says that OS developers must track users or be fined, so they will track users.

Explicitly bars OS devs from sending more data than explicitly necessary to meet 1

The statute does not define:

What counts as “minimum”

How necessity is measured

Whether “minimum” refers to data fields, granularity, frequency, or retention

Whether metadata (e.g., device ID, timestamp, API call logs) is included or excluded

This legislature calls App Providers and developers to track people and barely even gives lipservice to what is allowed.

We don’t want our OS’s tied to our identities. This does not explicitly forbid that

You’re identifying yourself lock-step to the government to run your computer. That telemetry is now theirs. Everything you ever do on that computer is now tracked or trackable to you and stored in a giant data center, probably eventually into a trained model of you.

You look at news about protestors, you leave a scathing review about a business supporting ICE, you post anonymously on a web forum that you’re displeased with the administration, All that needs to happen in the current climate is an executive order and the next time you go to update your passport or hop on a flight, you’re being detained as a terrorist.

Giving them this all willingly is a horrible idea and they will eventually use it against you.

The idea is you give it shell access. Say use super coder agent bob johnson to write a thing that does x using this [framework], separate files by best practice for x y and z features, ask security agent OSO to look over the code and suggest changes, ask agent U.N.I.T to make unit tests, when the code looks good, run through the unit tests. If anything fails keep fixing and iterating until every thing passes. Create a README.MD for everything that was done, Create a TODO.MD for any future suggestions.

I’m simplifying, but this actually works to an extent. Each of the agents keep the context windows small, the whole thing stays sane and eventually nets some project that works. The downside is you end up giving it quite a bit of leeway to get the job done or you sit over it watching and authorizing it’s every move.

Kinda strange to see a safety director do that…