See this as an opportunity
I've started putting "GDPR Compliant" on my resume and I've been getting a lot more calls back.
17 posts • joined 20 Nov 2017
The issue is not the availability of the records. Right to be Forgotten does not, as is popularly believed, compel this data to be purged from the internet. It compels that this data is removed from any *profile* that companies hold on you (public or not). Google's search engine and strong capability to summarize information means that when you search for a person's name, you receive a compiled list of information and links that are, taken together, essentially a profile. When the search result includes spent convictions, that's when RTBF springs in action.
According to RTBF, a spent conviction is no-longer-relevant information, unless there is a good reason it isn't. Good reasons could be for example exceptionally notorious, serious or heinous crimes, or crimes committed while in a public office. This is information that people *should* reasonably have access to, even after the conviction is "spent".
But, after such results are expunged as part of RTBF, an important thing to note is that this information stays available. More specifically, a targeted search is allowed to turn up this information with no qualms, as it can no longer be considered a general profile any longer. So "convictions ABC" is a search term that is perfectly allowed to serve these "censored" results. (IANAL so this explanation is a product of my own, limited, understanding of a complex piece of legislation.)
You hit the nail on the head. I'm an electronics/IT engineer and I'm friends with quite a few industrial designers. So many of their ideas and concepts are so entirely detached from physical plausibility that could be rectified by just having one person on board who vaguely remembers using a RasPi a long time ago. I have the impression that they're educated in a complete vacuum, unaware that engineers or practicality even exist.
Just don't do it. It's not worth it. We're seeing reports now nearly every day that third-party scripts, usually ad platforms, get hijacked and that high-profile websites start dropping malware or running coin miners.
Besides, I question the practice of government websites connecting to third-party domains. If you're running a gov site, security is a top-tier priority. This time we had a script being hijacked for coin miners, but what if it got hijacked by credentials-stealing code? Gov sites deal with highly sensitive information, and as such shouldn't run any code that its maintainers aren't 100% what it does. Concretely, what this means, is that they should host their own instance of the service and serve the scripts from their own domain. That this isn't already established policy amounts to sheer lunacy.
Whenever I pay with my Belgian prepaid mastercard, the payment processor refers me to my bank's verification page, where I need to perform a challenge-response routine with my TAN generator, card, and PIN. I've only ever encountered exceptions with Amazon, but I don't remember if they asked a verification for the first payment (and are only exempt for follow-up purchases), or if they never asked at all.
So I would assume that crooks, when trying to pay with my card details, would encounter the same verification wall. Thus making my bank details safe. Is that right?
The fact of the matter is that whoever posted these pictures didn't stop to think "hey, I'm posting child porn on facebook". Same thing goes with teens exchanging nudes they get from their teen hook-ups. When I was a kid, edgy as I was, I liked to browse 4chan's /b/. And tried as they might to prevent it, at one point I discovered some sick fuck posted child porn on there. Even though the girl in the picture was probably around my age and thus not very distinguishable from current-day teen nudes, my first reaction wasn't "cool I should share this with my friends", it was more like "OH FUCK NUKE THE DRIVE".
People of all ages are posting private pictures of hook-ups, girlfriends, ex-girlfriends, wives, ex-wives around with impunity, without regard for personal integrity, without understanding it's now on the internet forever, because everyone is doing it and no one ever faces consequences. Start treating even just tangential participation in sharing these intimate pictures as a serious crime, and it will cease being a mainstream issue. Once the sources of these pictures dry up (the people sharing what ought to be private), the only things left to repost will be those pictures shared with consent. No one's going to risk burning themselves on highly illegal pictures when there's plenty of promiscuous people who like having their pictures shared. People will see those who share those pictures as the scum they are.
It's a big mentality shift, but it's possible. Mainstream Western attitudes to women's rights and racism have undergone similar changes.
Literally no one of the daily Linux users I know, all Debian, Ubuntu, Fedora and even Arch/Gentoo users, really pays attention to distrowatch (or even knows what it is). Mint being popular on distro watch says just one thing, which is that it's popular with distrowatch frequenters.
The most popular distro on 4chan's /g/ is Gentoo but you don't see me peddling that as some kind of proof that it's the most popular distro _out there_.
Also still on OPO, but it's starting to show its age. Stuck on CM13 (jgcaap build) because that's the last version you could get the superior camera blobs to work. Performance is noticeably choppy by now. Battery only lasts a day on moderate use. I'll be switching to something new in 2018, but the OPO got a hell of a run. Hope the replacement is going to survive the regular drops I put my phone through.
Biting the hand that feeds IT © 1998–2019