Hacker News new | ask | show | jobs
by MandieD 2233 days ago
I've also read that it's to do with copyright - the recipes themselves can't be copyrighted, but the text around them can. Scraper republishes your ingredients list: not a lot you can do. Scraper republishes your fluffy anecdote and pictures: BLAMMO!
1 comments

Except the whole reason this article on scraping recipe sites was written was to ignore the fluff. Forcing copyright this way doesn't sound particularly helpful when the fluffy anecdote has so little value in comparison to the recipe. Or is it really the case that the average reader wants the anecode secondary to the recipe?

It feels like people are trying to make money around information that is fundamentally impractical to make money off of, so they're forced into doing whatever it takes to make money off of it anyway. "Whatever it takes" is defined by Google yet ruins the user experience, and so that is why recipe sites are this way.

I mostly like the pre-recipe text on Smitten Kitchen.

Sometimes it's a little rambling, but there's often useful information about the recipe that follows, like shortcuts that seem like they should work, but don't. She includes some interesting links or background, and getting a bite-sized glimpse of someone else's life isn't the worst thing.