Hacker News Reader

Comment by jon-wood | Hacker News Reader

I'll add my piece of anecdata to this. I've done a few projects that involved scraping over my career.

1. Scraping results from a property listing website, specifically to pull the properties an agent had listed and put them on their website. The agent didn't want to pay the fee for API access (they probably ended up paying my employer more to scrape it, and keep that updated, but hey).

2. Scraping an e-commerce website of a company my employer were working with to keep our product catalogues in sync - the partner had their own platform, but no API for it.

3. Automating requests to a price comparison website to find out what prices competitors are offering for particular types of customer.

View on HN

API keys can be revoked at any time or the API service can be suddenly terminated. You can't trust them. Scraping is more maintenance, but it is more reliable.

But whoever you're scraping can suddenly break your scraping tool too.

Temporarily until you work around what they're doing. API key revocation leaves you dead in the water until you rewrite your app to do scraping.

Yeah, but imagine they totally redesign their Web site. The "workaround" is a complete rewrite.

Ultimately it has to show the same data unless the site is completely discontinuing the service (in which case you are up a creek in either scenario). Even in the face of a total redesign you're usually just adjusting a few signatures and maybe tweaking the traversal tree.

You can run into problems when they remove things like chronological listing view in favor of some "algorithm" that you can't control, but even that just adds a little work on the back end to detect duplicates and an asterisk that some of the content will be missed.

There can also be an arms race where the site developers will start trying all kinds of crazy techniques to make scraping harder. Ironically this often happens after they revoke API access, meaning users don't have an alternative except to participate in the arms race.

I'm not anti-scraping or anything but I'd pretty much never choose it over an API for stability.

Having once worked with the "machine-readable" formats the realty industry produces, I'd rather scrape.

It's probably simple enough to implement both methods if available.

> The "workaround" is a complete rewrite.

No it's not, it's just swapping out a few selectors or regular expressions...

I think that depends on how thorough the redesign is, but surely it's not any less work than if the API breaks overnight.

Simpler than regular expression to be honest; css or xpath queries are rather simple compared to regular expressions.

Reorganizing the scraping queries is a lot easier than redesigning the website's layout.

Then they publish a new site format update with no notice. Doesn't sound very reliable to me.

Sure, but how often do websites change their layout? Once every five years at most. And it will take you no more than an hour to rewrite the signature. Ain't that hard. I've been doing that for a living and it's manageable, even if you monitor thousands of sites.

Indeed. A web site is an API, a crappy one, yes, but also one without unnecessary auth requirements and one they can't remove without removing their business.

Reply on news.ycombinator.com