zlacker

[parent] [thread] 7 comments
1. Ferret+(OP)[view] [source] 2023-07-08 09:04:59
To be clear, robots.txt is not legally binding, Google is not bound to follow it, and in fact I believe that Google doesn't follow it and hasn't for a very long time, for the simple reason that many sites' robots.txt file is wrong.

The intent of robots.txt is to help crawlers, for example, to keep crawlers from getting stuck in a recursive loop of dynamic pages, or from crawling pages with no value. robots.txt is not for banning, restricting, or hindering crawlers.

replies(3): >>superk+fB >>lisasa+rM >>floomk+xQ
2. superk+fB[view] [source] 2023-07-08 14:55:04
>>Ferret+(OP)
That's just because google is a corporate person who is more equal than a human person. Human persons, at least in the USA, get charged under the CFAA 1030 law if they're using non-browser tools to access the public website of someone with power and/if they happen to rock the boat (like weev w/wget).

That's not to say that I disagree. In most cases robots.txt is not legally binding. It only becomes a legal danger to not follow it when the person running the site has power and can buy a DA to indict you.

replies(2): >>rafark+w61 >>TeMPOr+oJ1
3. lisasa+rM[view] [source] 2023-07-08 16:05:45
>>Ferret+(OP)
for the simple reason that many sites' robots.txt file is wrong.

Which is of course not the real reason.

The reason Google doesn't follow the robots.txt protocol is (1) they don't want to (2) they can get away with it.

4. floomk+xQ[view] [source] 2023-07-08 16:28:54
>>Ferret+(OP)
They are in the EU. If something was not meant to be accessible you may not scrape it.
◧◩
5. rafark+w61[view] [source] [discussion] 2023-07-08 17:57:26
>>superk+fB
If a tool can access a url, does that not make it a browser?
replies(1): >>TeMPOr+HI1
◧◩◪
6. TeMPOr+HI1[view] [source] [discussion] 2023-07-08 22:10:36
>>rafark+w61
Not under any but most narrow of meanings, i.e. "can follow URLs / can talk HTTP". By itself, it's not a browser to users, it's not a browser to software developers, and it's definitely not a browser to lawyers and judges.
replies(1): >>rafark+XR1
◧◩
7. TeMPOr+oJ1[view] [source] [discussion] 2023-07-08 22:16:57
>>superk+fB
> like weev w/wget

Speaking of this and other cases of trying to punish someone for every iteration of a for loop - I wonder if the result would be the same if the accused drove actual browser to click stuff in a for loop, vs. using curl directly. I imagine the same, but then...

... what if they paid N people some token amount of money, to have each of those people do one step of the loop and send them the result? Does executing a for loop entirely on in part on the human substrate instead of in silico is seen as abuse under CFAA?

(I have a feeling that it might not be - there's lots of jobs online and offline that involve one company paying lots of people some money for gathering information from their competitors, in a way the latter very much don't like.)

◧◩◪◨
8. rafark+XR1[view] [source] [discussion] 2023-07-08 23:40:43
>>TeMPOr+HI1
Is there a legal definition of a web browser though? I think it’s an interesting topic.
[go to top]