News for hackers. Stuff that matters.
Re:Insights on the First Three Years of the Right to Be Forg... by ocdtrekkie on Monday February 26, 2018 @11:29PM (#16471078)
I am not sure how much they need to worry. Bear in mind, they only need to act if they get a request. Consider how successful your startup's search engine would have to be before individuals and companies would start submitting RTBF requests to them!

People are worried about how they appear on Google because Google is people's default. (In Europe, Google's somewhere in the 90% of search range, I think, you'd know better than I.) People don't want the first impression people get of them in the world's index to be unfair. That's why RTBF doesn't really even bother removing the original content from the web, they just want Google's index cleaned out.

I think if the startup you're advising ever has to seriously worry about RTBF, that startup has already succeeded.

(And, as an aside, pass on my best wishes to them. We need more choices in the search space!)

Re:Insights on the First Three Years of the Right to Be Forg... by greglindahl on Monday February 26, 2018 @11:31PM (#16471085)
I'm not so sanguine -- lots of RTBF requests come from aggregators, same as copyright take-down notices. So it's easy to imagine that a startup could start to get a large fraction of the ones sent to google/bing.
Re:Insights on the First Three Years of the Right to Be Forg... by ocdtrekkie on Monday February 26, 2018 @11:36PM (#16471104)
Yes, but you have to be on that company's radar, before they add it to the list. (Something unlikely to happen en masse before your startup is large enough to handle it appropriately.) And in the case of copyright takedowns, the extreme volume comes in part from the fact that Google and other companies of that size have even implemented bulk reporting tools explicitly designed to permit requests of that type and volume that the average user, or even corporation, doesn't have access to.

I don't know the answers to these, but I'd wonder if RTBF would allow for you to set restrictions on who can submit requests on behalf of who, or the volume permitted by a given reporting entity, or the level of automation permitted in reporting. Presumably the EU would much rather than you make reasoned, well-thought responses to carefully considered and submitted removal requests, over a bulk import/bulk decision process that leads to a lot of incorrect behavior.

Re:Insights on the First Three Years of the Right to Be Forg... by greglindahl on Tuesday February 27, 2018 @12:03AM (#16471194)
Do you have a concrete reason why you think it's unlikely? I have a different opinion about how large a search engine company would have to be before being able to "handle it appropriately", but maybe you have a good argument that trumps my experiences.
Re:Insights on the First Three Years of the Right to Be Forg... by ocdtrekkie on Tuesday February 27, 2018 @12:24AM (#16471267)
I don't think I could offer anything solid, no, beyond the general view that the litigious folks generally don't approach a platform before it's significantly large. (Most piracy on smaller mediums goes unharassed, for example, while The Pirate Bay and YouTube gets most of the attention.)
Re:Insights on the First Three Years of the Right to Be Forg... by greglindahl on Tuesday February 27, 2018 @12:34AM (#16471299)
A friend of mine runs a video copyright enforcement company. He provides the ammunition that Hollywood uses to send takedowns to a large number of small video platforms for content posted on them.

For a web-wide search engine, it's even easier: you can send a search engine a takedown for any url anywhere, because search engines index the whole web. RTBF requests are similarly relevant to any web-wide search engine.

Re:Insights on the First Three Years of the Right to Be Forg... by flipbrad on Tuesday February 27, 2018 @08:26AM (#16473116)
Strictly speaking, the EU's Court of Justice was just applying the EU Data Protection Directive's rule that organizations mustn't process more personal data than necessary, for longer than is necessary. That's a freestanding obligation that exists regardless of whether someone makes a request or not. It just so happens that in practice courts/regulators tend to view act/enforce it when someone has had to remind a company that they're failing to comply with that obligation, and the company hasn't complied. Hence it looks like something that companies only need to act on if they receive a request. Practically, if you're a search engine, that's the only pragmatic outcome anyway - how are you supposed to know, for each and every entry in your database, whether or not they satisfy the criteria for them to be "forgotten"? Better to have people flag potentially problematic ones, for you to then evaluate.