The Scraping Problem and Ethics
101–110 of 130 posts
Re: The Scraping Problem and Ethics
#102Earlier quoted context omitted.
While your sentiment is reasonable, I think the main difference here is that McAfee and others mentioned host their own private vuln databases and do not share them with anyone, so they were scraping to increase their own private resources for commercial use. Aaron was scraping private resources to share publicly.
More than that, he was scraping private resources that were freely populated. He was not robbing content creators of their money. He was circumventing a paywall to what should be free data.
I feel bad for OSVDB from a sysadmin perspective, but if Aaron's case was so polarizing for essentially the same thing, why isn't everyone jumping on the Hate Train here?
Re: The Scraping Problem and Ethics
#103Earlier quoted context omitted.
More than that, he was scraping private resources that were freely populated. He was not robbing content creators of their money. He was circumventing a paywall to what should be free data.
That's quite the mental leap. He was circumventing a paywall, but that's not robbing anyone of money because it should have been free in the first place? Well, it wasn't free, even if you think you it should be. Thus the paywall.
Since then, JSTOR has released these documents freely themselves[1]. They have also stated that this was their intention all along.
[1] http://about.jstor.org/news/jstor%E2%80%93free-access-early-...
Re: The Scraping Problem and Ethics
#104This is one of the more interesting policy questions on the web. Our search engine crawls a lot of blogs and what not on the web, criminals who want to find unpatched wordpress sites try to acrape our crawl by sending automated (scripted) queries to find them. We have developed a number of defenses over the years and pretty regularly ban them[1]. Here is the weird part though, if they hired 300 people on mechanical t…
The argument that if you really want this information, they should pay for it doesn't work. Basically, you are punishing people for automating manual labor. The fact that you can hire bunch of people and tell them to manually copy data from the website and achieve the same result means that it shouldn't be any different from automating the process itself.
Terms of service on a website is not the law. If there is something you don't want people to have access to, then don't publish it online at all.
Re: The Scraping Problem and Ethics
#105Earlier quoted context omitted.
You need to be careful sending bogus data: in some jurisdictions this could be argued to be deliberate targeted commercial sabotage. You would no doubt eventually win any resulting legal argument, assuming you could afford to carry the argument on to that conclusion . Sending no data, or limited data, would be safe though. A better method would be to set "default" pricing (something high but not ridiculous, that coul…
Hasn't the mapping industry already set a precedent in this field? They provide maps with small, wrong roads/trails specifically to identify who is stealing their data.
Re: The Scraping Problem and Ethics
#106This is one of the more interesting policy questions on the web. Our search engine crawls a lot of blogs and what not on the web, criminals who want to find unpatched wordpress sites try to acrape our crawl by sending automated (scripted) queries to find them. We have developed a number of defenses over the years and pretty regularly ban them[1]. Here is the weird part though, if they hired 300 people on mechanical t…
Since you work at Blekko, there are more points to discuss that were not addressed in the article. For example: i) Are search engines web scrapers? ii) Should search engines pay the scraped sites if they are charging to access their indexed data? probably some of the scraped sites has a specific license forbidding the search engine to sell their information in any way. iii) Regarding Internet policies, is it fair/unf…
Take the classic example, a search for 'bilbo baggins'. What that is, is a request to identify documents on the web that have referred to Bilbo Baggins and return their locations.
1) It is absolutely true that you could sit down at your computer and look at each site, from aol to zillow, read all their pages, and note the ones that mention Bilbo. Then you could go back and order the list by the ones that had more of the information you were looking for to the ones with less useful information. Along the way you would find some sites that would not open up to you unless you had an account, those you could not visit.
2) A search engine can look at all the sites, it can note which sites mention Bilbo along with a bunch of other terms and can essentially "pre-compute" that list you were looking for. Along the way it will find sites that, through their robots.txt file, will say "We'd rather you not look here." and it will respect that, thus not indexing those sites.
In both cases figuring out which web pages have information about Bilbo on them is creating 'new' information out of existing data. You can do it on your own and it will cost you time, or you can do it with a few thousand machines and it will cost you money. Either way you get a list of possible sites.
That list forms a distribution, where there are a lot of sites that don't care one way or the other if you read them, sites that won't show up because they asked to be excluded, and sites that will show up because they paid to be included. Some sites really want you to find them, some sites really don't. A good search engine caters to both types.
ii) If a search engine was taking the page, copying it, and then showing that instead of showing the page (this is what got Google's news product in trouble) then its pretty clear that they should not do that. But in terms of location information? The sites themselves derive a huge economic benefit from being in the index that isn't reflected at all back to the search engine that sent traffic there [1], so on a pure economic basis the search engine is on the losing side of that transaction. However, the marginal cost of additional transactions is small (search engines are general purpose) so they make a small amount on large volumes.
To put your question in more specifics, where is the economic value in the list; bobs middle earth atlas, wikipedia entry on bilbo baggins, middle earth web ring, imdb pages on characters in the "Lord of the Rings" movie.
Is it that Bob has an atlas of Middle Earth? Or is it the list itself? Who made the list? Bob or the search engine? (or some human curator of a bookmarks page[2])
iii) It is completely up to the site to allow or disallow access to its content by search engines. Some sites do only allow themselves to be indexed by Google and they find they get less search engine directed traffic that way. Some sites don't allow anyone to index them and they get no traffic (sometimes they are surprised by this, sometimes they don't care, sometimes they are angry that the only way for people to find them is to be in a search engine index)
[1] Google broke that by creating AdSense for Content and created a pretty interesting conflict of interest for themselves.
[2] Good luck finding a book marks page these days :-)
Re: The Scraping Problem and Ethics
#107The article is basically saying "I want to charge people for information I have made public online, they won't pay, so they are obviously thieves by refusing to do it manually by hand like they are supposed to."
Gimme a fucking break here. If you don't want the information to disseminate, DO NOT PUBLISH IT ONLINE.
Re: The Scraping Problem and Ethics
#108Earlier quoted context omitted.
You can get scrapping libraries fairly easily. In my more shady past I developed a library like that and shared it, HTTP client library with automatic proxy rotation and rate limiting friendly. When I used it (which was almost a decade ago) never ran into problems, plug a list of 10,000 proxy and scrap away. Not condoning that, which is a bit hypocrite of me, at the time I was mostly doing what I was told and I thoug…
Speaking as devil's advocate, it might just be more convenient to steal the data. Maybe I want to use your data casually once, and I don't want to sign up and give you all my contact details and subscribe to your annual plan with all the other optional extras. Tough shit, you say? I'll just steal it then, and not because I can't afford it, but because you're making it hard to pay.
Re: The Scraping Problem and Ethics
#109Earlier quoted context omitted.
I think there is a great meta-question in here, about business models for digital data and software. Here you have a great case study, about an organization that tried to do a volunteer model, and it didn't work. Then they pivoted to a commercial model, but fundamentally they still believe in a free tier. But they have to cripple that free tier pretty thoroughly, and even still people abuse it. I have a product I'm w…
They made the process of paying for the software a laborious pain in the ass. They are desperately trying to extract money from those who can pay, which sadly drives away those who can pay but don't want an involved process. I have worked at lots of companies where I had a monthly budget of 10k+ that I could spend on whatever I wanted, but if I wanted any sort of complex deal (can't just put on CC with a line item) -…
Re: The Scraping Problem and Ethics
#110Earlier quoted context omitted.
Talking to someone on the phone is not "extremely difficult." Large companies buy stuff by talking to people on the phone all the time.
and I have a policy that if the company does not practice open pricing by publishing their prices online I will not do business with them.. Fuck that non-sense of pricing based on what ever they think they can scam me out of
A conversation I've had a few times:
"We need it to do $THING_IT_WON'T_DO."
"In that case, it probably isn't a great fit for your needs."
"You don't understand. I won't buy it if it doesn't do that."
"I think I do understand. That's fine. You might consider trying $COMPETITOR, although you should know their minimum spend is $1,000 a month."
"That's outrageous. You have a $29 plan."
"Yes. So you should go with the competitor if that requirement is worth $971 a month to you."
"No, I want to spend $29, but I absolutely need that."
"I understand where you're coming from, but we do not offer that feature, and if we did, we would charge prices close to what our competitor does for it."
"You're not working with me here."
"I'm trying to find a resolution which works for you, but including that feature at $29 doesn't make business sense for me, so I won't do it."
"Put me on the phone with your boss."
"I'm afraid that isn't possible, as I sort of run things around here."
"What sort of businessman turns customers away."
"You're not a customer. If you were, you would be purchasing a product I sell for the amount I sell it for. That isn't happening. That's fine. Have a nice day."