This one isn’t very privacy-friendly or open. And that raises all the previous questions again. Should they maybe have learned something about clandestinely fucking with people’s systems?
1,833 karma · joined March 27, 2009
This one isn’t very privacy-friendly or open. And that raises all the previous questions again. Should they maybe have learned something about clandestinely fucking with people’s systems?
1. being completely transparent about all the mechanisms that data or code can be pushed to or pulled by the browser, or pushed from or pulled from the browser; and
2. having a toggle for all of them, yes every single one, in Privacy & Security.
The fight is not over yet. The directive needs to be written, and ideally in a way that prevents this from being brought back to the table again.
But that’s slightly different because it could be seen to change the dynamic form performance over a season to fewer best out of N events.
Also, just use a code formatter that rejects any incorrectly styled code.
In practice (and with some experience) most decisions do not prevent revisiting them later.
(Except for your own benefit.)
(And also not subject basic rights like healthcare to market forces, but that’s a bridge a little farther.)
Any changes are related to the expected value of the stock, not the company itself.
You have what’s called “survivor bias”, and you need to get past it to understand systemic issues.
I’m not an expert in visual science, but I suspect it is easier to tell _multiple_ ships apart when they have fewer lights.
ETA: https://www.marineinsight.com/marine-navigation/understandin...
(Edit: without addressing your questionable definition of what it means to control one’s data.)
The GDPR gives _individuals_ power over their data. It’s not “big government oversight” (whether you think that’s good or bad).