11–20 of 204 posts
Are there any legal issues with scraping recipe sites in a commercial app like that? I'm assuming ingredients and directions are "facts" so can't be copyrighted, but what about the pictures?
But how will I read about "Dakota", an avid yoga enthusiast who just happens to be a mom, who enjoys making healthy and savory meals for her family while blogging? Seriously, I hope this spells an end to the Google ranking imposed nonsense that makes the simple act of searching for a recipe so insufferable.
It's a running joke in our house. I start off wanting to make some mashed potatoes, and time and time again, I have to suffer through someone's life story--the camping trip in North Dakota when Susan's husband first discovered his love of homemade sour cream--etc. Makes me wonder if a super barebones recipe site that literally just has recipes and absolutely no fluff would be something people would gravitate towards.
Actual "I have these things and want to cook something" could practically be automated.
The big exception is baking, where precision ratios and time matters a lot.
(I'm also reminded of various stories of people trying to trace the origins of much loved family recipes and then discovering that rather than being an authentic traditional Calabrian whatever, their grandmother copied it off the back of a tin. I'm fairly sure my own grandmother's cookies recipe is from Tate&Lyle)
Are there any legal issues with scraping recipe sites in a commercial app like that? I'm assuming ingredients and directions are "facts" so can't be copyrighted, but what about the pictures?
Scraping is LEGAL, all search engines scrape to some degree for example, there is a fair use component, so you can't "scrape" 100% of a site and stick it on your domain, but you can still scrape more than zero. In general it is leaning more acceptable than less.
https://www.yummly.com/ used to have a paid API for recipe search and currently still lets users search their index. Did they have to go and get permission from each site that they index or is it fair use?
EDIT: Yes, the article mentions it, but doesn't give a clue why it isn't more prevalent.
Are there any legal issues with scraping recipe sites in a commercial app like that? I'm assuming ingredients and directions are "facts" so can't be copyrighted, but what about the pictures?
Is this post illegal as it contains information on how to commit crimes such as copyright infringement?
Earlier quoted context omitted.
It's a running joke in our house. I start off wanting to make some mashed potatoes, and time and time again, I have to suffer through someone's life story--the camping trip in North Dakota when Susan's husband first discovered his love of homemade sour cream--etc. Makes me wonder if a super barebones recipe site that literally just has recipes and absolutely no fluff would be something people would gravitate towards.
Having thought about this and my own use of cookbooks as loose inspiration rather than actually to follow in detail, I have come to the conclusion that the "fluff" is what most of the recipe-reading public want. In particular, the fluff has value even if you never cook the recipe! Which saves a lot of time and inconvenience on your part while still giving the same warm fluffy feelings. Actual "I have these things and…
I've often heard the prevailing reason why this happens on the web is because of SEO and 'bounce rates'. More time spent on the site improves ranking, so the actual recipe is pushed below the fold so users have to scroll down thereby adding more time on the site.
Have often wondered if any SEO wonks with the inside baseball can actually validate this?