1,906 karma · joined April 29, 2012
IRC can be part of a solution but it's not a solution on its own.
There are ways to create anonymous datasets, but they generally involve aggregation, not just removing the identifiers.
It's unfortunate that general lay person understanding of the concepts at work here doesn't tend to extend to this distinction. It would help drive privacy conversations if this were more commonly understood.
Yes, actually, people do this all the time. They find new things to be passionate about if being passionate about something is too painful.
It does, actually: https://www.php.net/manual/en/intro.password.php
Partially demonetized videos may show ads, but from a reduced set of advertisers - those videos will make money but possibly not as much due to less desire for the ad space on that content.
The third can be a flag flip instead of a code push, but it still needs to be a discrete event to start generating the new value that triggers new behavior.
The linked page portrays it as e.g. CA moving to "MST" but that doesn't actually accurately represent what's proposed, because the lack of a DST switch is meaningfully different from just moving to the same timezone as current Mountain time states.
So with that caveat in mind, let me see what I can help answer.
I'm not entirely sure what nuance you're implying when you say "different deletion policies" - while for instance Cloud might have a different timeline or set of triggers for when and what data is deleted, when it happens "deleted" still generally means "deleted". Some products like GSuite have the ability for administrators to say, disable accounts, which removes them from use but doesn't delete the account, but that's transparent to the domain administrator.
It's definitely nontrivial to track data propagation within large systems, but standardizing infrastructure, having central documentation of data handling plans, and having comprehensive privacy reviews for any new functionality that launches helps keep people on the same page.
Edit: oh, and regarding "retraining every model a data point touched" - the easiest way to do this is to just always be regenerating your models on a frequent basis. If you retrain your models once a day or once a week on a fresh snapshot of your data, they'll only ever be that stale.
Perhaps browsers need to expand the potential effects of access-control-allow-origin.