4 ms·
> I just want the (functional, non-copyrightable) recipe itself. There's the rub. You can copyright your story. It's easy to scrape recipes from webpages.
by klyrs 6y ago
> I just want the (functional, non-copyrightable) recipe itself.
There's the rub. You can copyright your story. It's easy to scrape recipes from webpages. It's harder to translate a story into a recipe. If you post a plain & simple recipe to the internet, it will be copied and folks (and the bots behind search engines) won't have a clear incentive to visit/link your recipe over the numerous copies. If you've got a clear copyright violation, there's a chance you can get the copies taken down, or at least hidden by search engines. If it's just the functional, non-copyrightable recipe itself, no such luck. And then, with all the expense of creating and hosting the content, plus fighting the deluge of spammers, how do you monetize? The easy way: the borderline malware ads, modal popups, dickbars, etc. Blech. I'm with you, it sucks. But it's not just "an SEO thing"; it's also a case study on how "information wants to be free" meets the gritty reality of the internet economy.