> Parents buy those phones, phones could easily have a "user is a minor" setting (and a flag sent to all the sites that want one)
That's basically the California law! I hope other states adopt the "ask nicely for age but no online verification." OS setup asks for birthday, but you can just say January 1.
I also thought it should just send the flag, but I've heard there's good reasons not to. There's normally an affirmative prompt from the user to agree to send the age bucket data.
Thanks for sharing that nuance. It seems one court weighed in that Claude chat wasn't accepted:
> In February 2026, Judge Jed S. Rakoff of the U.S. District Court for the Southern District of New York ruled that a defendant who pasted information—including details conveyed by his lawyers—into a public, consumer-grade AI chatbot (specifically Anthropic's Claude) completely waived his attorney-client privilege.
But maybe if you are using a transcription tool that happens to send your audio through the Anthropic APIs, the ruling would be different?
A production app with customer data needs a data backup/restore strategy. I'm guessing a random app server writing to a local sqlite file isn't doing that either.
In my USA high School, they started requiring graphing calculators in the 9th grade math class. You would fail most quizzes/exams without the ability to run the calculations that scientific calculators couldn't do.
I'm struggling to remember using my TI-84 in college though.
Our team of 8 SDE and 5 SDET became a team of 8 devs who also owned tons of QA frameworks. It was awful, except each tiny we deleted a test suite for not being valuable; that was awesome!
If the Azure org was flooded with senior engineers who did not have senior-level experience architecting production software... That explains a lot.
There's a CLI tool that writes the agent skills into the right folder. The other option would be to have everybody manually unzip a download into a folder which they might not remember.
Jenkins CI has a clever feature where every password it injects will be redacted if printed to stdout; `enveil run` could do that with the wrapped process?
Of course that's only a defense against accidents. Nothing prevents encoding base64 or piping to disk.
English is flexible; almost any combination of words can start to have meaning.