Recipe for french toast: Step 1: Learn the history of France Step 2: learn the history of toast Step 3: heat bread, eggs, milk in a pan

Keep going. The ingredient list is on page 12.

One time I inadvertently hit print on a recipe like this and the print dialog estimated 45 pages.

Few people pay attention to their print stylesheets anymore but some recipe sites do and it’s great.

Ahh the wonders of SEO

You forgot the history of the writer’s family and the impact that French toast has had on them for generations.

Blogs in general, I’d say. As for recipe sites: https://based.cooking/

That is where it’s at.

Squeal emoji

This is fantastic

SeriousEats. It’s truly amazing. Most of their recipes are split into two pages, one is just ingredients+steps, and the other is a “story” - but not an irrelevant story of a person, dish, or how it tastes on a warm summer day, but instead it lists different experiments the author tested, results, dispels common myths, …

Boy oh boy do I have the recipe for you!

http://slimsag.com/best-apache-chef-recipe/1438731.htm

This made my day.

That hits so close to home. I’ve given up searching for recipes online because of this. And I’m not even mentionning all the ads you have to scroll through.

Most recipe blogposts these days have jump to recipe.

The mitigating factor for recipes is you can just scroll down till you see a table.

Those have gotten way worse. It’s an SEO thing right?

It's viewed as a DRM measure. Recipes are not copyrightable unless they are attached to a story. It's probably an urban legend, but can't blame poor food bloggers from acting on it.

It's not an urban legend in the United States:

====

Based on this reasoning, the United States Copyright Office Compendium, the Office’s manual for examiners, states that a mere listing of ingredients or contents is not copyrightable, as lists are not protected by copyright law (chapter 314.4(F)). The Office has also stated that a “simple set of directions” is uncopyrightable.

In addition, courts have found that recipes are wholly factual and functional, and therefore uncopyrightable. As the Sixth Circuit described in Tomaydo-Tomahdo, LLC v. Vozary, “the list of ingredients is merely a factual statement, and as previously discussed, facts are not copyrightable. Furthermore, a recipe’s instructions, as functional directions, are statutorily excluded from copyright protection.”

https://copyrightalliance.org/are-recipes-cookbooks-protecte...

I would have thought the same reasoning would apply to software. I'm curious about how reasoning differs in that case.

I have to think part of it is also the pay structure of food bloggers being paid by the word.

I'm pretty sure recipes aren't copyrightable, even when they are attached to a story.

I'd assume it prevents legally scraping & copying the whole site, at the cost of a silly amount of human labor writing the fluff.

I just think they're part of the non-fiction fantasy genre of entertainment alongside cooking, travel, and house buying + renovating shows.

They're ostensibly informational, but 99% of people consuming them aren't genuinely looking to cook the thing, travel to the place, or buy and renovate a house.

Clearly an attempt to lure you in when you're hungry and searching for some common queries like history of famous places.

I’ve assumed it was to create a longer page which can hold more ads.

Recipes by themselves aren’t copyrightable. Bullshit stories are.

Does copyright for a story containing a recipe protect against use of the recipe outside the context of the story?

No, but it stops straight scraping, and requires a scraper to do a little bit more work to copy the recipe.

Not much extra work surely. Most recipes are on sites that use the same template for every recipe so it's pretty easy for a scraper to find the ingredients and method. The structure is usually even labelled with meaningful class names on the elements.

I think the question is “is it possible to split recipe from BS story programmatically”

Generally yes. Most recipe blogs use semantic markup so that Google recognizes it as a recipe, which also makes it easy to scrape programmatically.

No

Yes - it's not specifically that the recipe sites have changed to do this, but rather, that Google is preferring to show you sites that are doing this.

I want an AI browser plugin just for recipe sites called GTTP (Get To The Point).

Probably could build it with regex, actually.