https://buy-zithromax.online buy kamagra usa https://antibiotics.top buy stromectol online https://deutschland-doxycycline.com https://ivermectin-apotheke.com kaufen cialis https://2-pharmaceuticals.com buy antibiotics online Online Pharmacy vermectin apotheke buy stromectol europe buy zithromax online https://kaufen-cialis.com levitra usa https://stromectol-apotheke.com buy doxycycline online https://buy-ivermectin.online https://stromectol-europe.com stromectol apotheke https://buyamoxil24x7.online deutschland doxycycline https://buy-stromectol.online https://doxycycline365.online https://levitra-usa.com buy ivermectin online buy amoxil online https://buykamagrausa.net

More "Right To Be Forgotten" silliness

Google offers some pertinent notes on issues around the European "Right To Be Forgotten" discussion:

'We generally have to rely on the requester for information, without assurance beyond the requester’s own assertions as to its accuracy. Some requests turn out to have been made with false and inaccurate information. Even if requesters provide us with accurate information, they understandably may avoid presenting facts that are not in their favour. As such, we may not become aware of relevant context that would speak in favour of preserving the accessibility of a search result. An example would be a request to remove an old article about a person being convicted of a number of crimes in their teenage years, which omits that the old article has its relevance renewed due to a recent article about that person being convicted for similar crimes as an adult. Or a requester may not disclose a role they play in public life, for which their previous reported activities or political positions are highly relevant. We have also seen examples of data subjects who indiscriminately submit many URLs that are displayed as search results for their name, even though some URLs are actually about another person with the same name.'

Determining the justification (and scope) of such a request is a labor-intensive effort.  If Google is simply handed such requests (over 90K of them, regarding 300K pages) en masse, then either it need to devote substantial time to each one, or reject them if the verification seems sketchy (except that the verification would be coming from the requester), or just accept them and let the results fall where they may. None of these seems reasonable. If Europe thinks this is a fundamental right, they need to provide a more substantive process to give Google (and Microsoft and other search vendors) verified data.

And even that's goofy, because, as the request to omit an editable Wikipedia page suggests, the issue is not about search indexing, but about the content being indexed. If the EU wants a true Right To Be Forgotten, then they need to have a process to take down the offending content, and then request Google recrawl it.

Embedded Link

Google Struggling To Deal With Right To Be Forgotten Requests — Will Now Delete Wikipedia Page From Search Results | Techdirt
Late last week, Google responded to the concerns raised by some EU regulators regarding how it is implementing the new “right to be forgotten” rules. Google’s full response is well worth reading going into a fair bit of detail…

45 view(s)  

One thought on “More "Right To Be Forgotten" silliness”

  1. Based upon Google's usual method of dealing with requests, I suspect that "just accept them and let the results fall where they may" could be the possible answer.

    Except that in this case, accepting a request adversely affects Google's core business, advertising, so perhaps they're less likely to act on them.

Leave a Reply

Your email address will not be published. Required fields are marked *