@oaklandprivacy Has any state made serious efforts towards outlawing the data broker industry outright?
As in, rather than forcing individual residents to opt out of data collection, mandate that as soon as you become aware someone is a California resident they implicitly treat that as a deletion request.
And banning the operation of data brokers within state lines (even if not handling CA resident data) including employing CA residents, selling data to CA companies, etc.
California residents now have a real tool against the data broker industry.
The state has launched DROP, a single portal to demand deletion of your personal data from 500+ registered data brokers in one request, for free.
To start: https://consumer.drop.privacy.ca.gov/
“Move fast and break kings.” I love @pluralistic and his rallying cry: https://pluralistic.net/2026/01/01/39c3/
Bonne année 2026 à tout le monde !
N'oubliez pas que l'appel à soumission est en ligne et que la date limite pour envoyer vos articles est le 18 janvier.
Now those gpg.fail people made me find similar vulns elsewhere (console control character injection). By "elsewhere" I mean... my own code.
Opinions wanted: should "input can inject console output with ansi and control chars" always be considered a vuln/CVE?
(I'll fix it in any case, I'm just wondering if I should do all the "security release/advisory/request CVE/..." stuff.)