Re:Robots.txt meant for search engines don’t work well for w...
by eknkc on Friday April 21, 2017 @03:49AM
(#14163771)
I don't think a poorly written scraper would follow robots.txt rules according to spec. So, in any case the site should have other measures (rate limiting?) anyway.
Re:Robots.txt meant for search engines don’t work well for w...
by davb on Friday April 21, 2017 @03:34AM
(#14163710)
Additionally, if excessive scraping became an issue for my site I'd consider rate limiting client.
Re:Robots.txt meant for search engines don’t work well for w...
by dingo_bat on Friday April 21, 2017 @04:21AM
(#14163875)
> (specified by the website owner via a robots.txt like spec).
Nope, if a website wants such a restriction, it must enforce it. Robots.txt is a request. It's worthless.
Re:Robots.txt meant for search engines don’t work well for w...
by bkor on Friday April 21, 2017 @06:13AM
(#14164281)
If a robot misbehaves, it'll either be blocked or it'll go to the networks abuse section and that bot will be taken down. That a site possibly could have some kind of technical solution to this doesn't matter.
Re:Robots.txt meant for search engines don’t work well for w...
by problems on Friday April 21, 2017 @11:25AM
(#14166373)
Precisely - the solution here needs to be that the server blocks the robot - if it can differentiate it from other traffic that is. That's all well and good and that's the solution which should be used here. If you don't want to be archived, block the IP.
a poorly written scraper may really slow down your site, especially if it wasn't intended to be scrapped repeatedly. There should be something to be said about frequency which scrapers should follow (specified by the website owner via a robots.txt like spec).
But website owners cannot demand unreasonable frequencies (such as once a year!), and what constitutes unreasonable is up for debate.