ovh? Isn't that one of those "You'll be blocking them sooner or later so why not now" places?
Matter of fact, detour to notes tells me I've got both 184.22. (NOC) and 92.23 (OVH) blocked :) Don't know how long ago, or what the trigger was. Generalized robotitude, looks like.
184.108.40.206/16 OVH is listed on RIPE as an ISP in Paris. Just a note for people who might rely on visitors from the area to maybe block agents rather than IP.
Had them blocked for years.
HostNoc Virtual Servrs
220.127.116.11 - 18.104.22.168
OVH Dedicated Servers
22.214.171.124 - 126.96.36.199
(The /16 includes the ISP)
Over 1200 scrape attempts from 227 distinct IPs from all over of 188.8.131.52/16 dating back as far as 2009-01-14 18:52:07
Including 1 bumb-*** competitor who tried to scrape product descriptions from an IP that is translated to a hyphenated .com & .net version of our domain registered to an actual B&M Store in Paris. Nailed by DMCA to all SEs.
The sad part is they actually had a pretty good inventory of widgets, quality stuff too.
The fun part is everybody from that range get a generic version of "90% off - Going out Of Business!" message since 2009.
Ha.., just checked that site: Site actuellement indisponible!
Comes on guys, admit that a site protecting itself by identifying, bagging and tagging scrapers automatically is cool. I only block ranges to be preemptive because so far the technology stops almost all of it cold. However, some of them get a few free pages before they get blocked if they're really good which is where blocking ranges helps prevent any leakage.
|scrape product descriptions from an IP that is translated |
Exactly why I put tracker bugs in my text, another reason anyway, because the trackers don't translate so codes like XXYYZZ-3287520629 (code plus long IP) make it thru unscathed into auto-translated text, scrambled text, etc. and I can easily find them in Google, Bing, etc.
I'd recommend everyone do it but I'm afraid the scrapers would figure out how to filter them out if I put out some tracker bug module.
...or you could just block all translators like I do. Why let some translator service scrape your content, replace your ads with their own, and publish it from servers with none of your blocking techniques?
|...or you could just block all translators like I do. |
Content can be scraped first and then translated or translated from cache if you don't use NOARCHIVE, or from the Internet Archives if someone allows them to crawl.
I allow translators because I run a worldwide site but the user agent must be valid and they can't take too many pages or they get squished. I also check the forwarded IP for validity.
Not "insufficient" why would you say that?
I do not allow caching and block it in several ways, and I have never allowed IA to copy my property. I was one of the very first to bring a suit against them. Because of it, they were forced to start removing anyone's intellectual property if asked by the owner.
Webmasters who allow their content to be scraped by translator services are exposing everything without all the protections they have on their own server. I don't understand why they even block any IPs or UAs or whitelist if they are going to let a translator scrape their content and put it unprotected on another server.
If your business depends on alternative language support, install those translated pages on your own server where you can protect it.
|I do not allow caching and block it in several ways |