Show HN: OnlyRecipe.app – Remove clutter from recipe sites
showcase.onlyrecipe.app
showcase.onlyrecipe.app
Scroll to the bottom to see what I’m talking about: http://www.cookingforengineers.com/recipe/108/Banana-Nut-Bre...
Example (second image) https://modernistcuisine.com/recipes/pressure-cooked-vegetab...
Currently, some different money for recipes as a service, and the weird price of $41 for a "lifetime" subscription
It will interest this audience that they have a public roadmap, too: https://roadmap.thecookbookapp.com/cookbook
I would actually expect the whole process could be laid out in graphviz since all of those are dependencies of the ultimate outcome (heh, "enjoy"). I originally thought it may be a DAG, but I can recall a few recipes that explicitly have a looping step in them
I know tastes differ, but personally I think it’s terrible.
Personally I am a fan of the Food Network recipes online, especially Alton Brown’s. Straight to the point with no fluff, and maybe a Good Eats segment if you’re lucky.
I have ADHD so I often find my self taking a non-linear route to following a recipe: Step 1, Step 3, Step 4, oops! Step 2, now where was I? Is that salt or baking powder in the bowl?
Everyone thinks I made an “app” because it launches in full screen thanks to the MDM. One of our kitchens doesn’t have Wi-Fi, but once the recipe viewer is launched, it doesn’t need connection anymore since it’s a single HTML page and the refresh button is hidden.
The recipes on my “app” use HTML tables fairly similar to the tables on the link you shared. I didn’t know HTML tables could be formatted like they are on cookingforengineers.
I think the op means it’s nice that the ingredients are given by weight because it is more accurate than volume.
I’m not sure why it’s talking about “cups”, I thought americans used “gallons” or “fluid ounces” for volume? It also has one ingredient that has accuracy to 3sf in its weight (167 grams) which seems rather excessive for cooking.
In theory you can use volume to measure things like flour, although it is trickier than using weight as you have to smooth it over.
I have always been interested in seeing a database which had consistent units and ingredients as well, such that pulling the full database and doing visualizations could be easily done.
This would also make the adjustment to the batch size for each recipe on each webpage much simpler.
"Want 1 Liter of dough for 2 banana bread loafs? Just change the amount output field and watch the values change". Type of thing.
Obviously I know heat transfer effects need to be taken into account and such for some things, but it would be at least a start . Then the real mass/heat transfer and such engineering fun can begin.
You can also save it to your phone directly using the app. Scan recipe QR code using your phone camera and voila.
Android: https://play.google.com/store/apps/details?id=com.mysticpeak...
iOS: https://apps.apple.com/app/id1602130759
Short 50-seconds video on how recipe camera scanner works https://www.youtube.com/watch?v=ziSNwjv9PXo
Currently working on a feature that lets you share recipe "image cards" with your friends.. Something like this https://i.redd.it/kk1goqsswo981.png
Let me know if you'd use that feature
I believe it's more likely that it's to do with whether you can or can't copyright a listing of ingredients and method.
If you add enough of a story, you definitely can.
The recipe is separate from the text that accompanies it
Separate in a copyright sense?
A web scraping bot won't necessarily make that distinction.
As a cook there are several solutions to this:
1) pay for a subscription from vendors who are in business to sell recipes, such as Cooks Illustrated
2) get recipes from companies that provide them as a complement because they sell something else, generally food-related products. For instance King Arthur Baking has good recipes, and many are available from food companies such as Tyson, Kraft, and Betty Crocker. Grocers also have many recipes. These sources aren't interested in spamming users with ads because the website is one big ad.
3) Buy cookbooks, they're not expensive.
But yeah as long as people want to crank search terms into Google and get "free" stuff, it's going to be ad-infested, and then other ad-seeking folks are going to run their shakedown operations just like the adblock extensions charge money to advertisers to let their ads through.
While cookbooks are great they're not easily searchable. If only I could ingest every recipe from every cookbook I bought into a personal database.
Hey that'd be a neat app idea!
And how does a site opt out of your scraping? Do you have a unique user-agent when you scrape? A set of IPs?
Let me see if I can build a opt-out list. But wouldn't it beat the entire purpose of this app?
If your business model relies on people scrolling past a bunch of filler to get to a short list of instructions, be prepared for people to get tired of it and solve the problem.
"Essays meanwhile allow bloggers to make money off search engine optimization (or SEO, which scans the essays for keywords and relevant search terms) and ads allow the blog to remain free for readers."
So here they openly admit to the hack. This entire fraud is one app or google algorithm tweak away from being annihilated.
It should be seen as a side job with expectation zero, any money is a bonus, not something you do to "feed your family". I mean, read this rant:
https://www.eater.com/2020/3/31/21201374/why-are-free-online...
Delusional.
Recipes can be protected under copyright law if they are accompanied by “substantial literary expression.” This expression can be an explanation or detailed directions, which is likely why food and recipe bloggers often share stories and personal anecdotes alongside a recipe’s ingredients.
So besides SEO, there's this thing where the recipe itself is basically defenseless against someone stealing it and calling it theirs but the sum of the fluff around it plus the recipe on the other hand can be copyrighted and enjoys all the protections afforded to these kinds of things. So, if say, Jamie Oliver likes your recipe and puts it in a book passing it as his, you can now legally tell him to stop doing that because of said fluff. Even if the description of the recipe is sufficiently creative and copyrightable, the copyright will not cover the recipe’s ingredient list, the underlying process for making the dish, or the resulting dish itself, which are all facts. It will only protect the expression of those facts. That means that someone can express the recipe in a different way — with different expression — and not infringe the recipe creator’s copyright.
So they can still put your recipe in a Jamie Oliver cookbook, they just have to put it in their own words as opposed to copy pasting it verbatim.Chrome: https://chrome.google.com/webstore/detail/recipe-filter/ahlc...
FF: https://addons.mozilla.org/en-US/firefox/addon/recipe-filter...
Source code (there's Safari in there if you don't mind building it yourself): https://github.com/sean-public/RecipeFilter
I was spurred into action by a comment here on HN back in 2017: https://news.ycombinator.com/item?id=15755378
It got demoed to the world during WWDC 2020, which was really neat: https://youtu.be/Kwh2y6VkzoA
I'd love to support Safari, and like OP I have it technically working as well, but as the extension is free and open source it's hard to justify the $99 price tag just to share it with the world. https://github.com/idolize/xcloud-keyboard-mouse/issues/13
I often don't remember it's running, but then I invariably land on a recipe site, and then the Recipe Filter modal pops up, and instantly brings a smile to my face.
One feature that would improve the recipe recognition and unlock lots of other features where it's found would be JSON-LD support. I'm seeing lots of recipe pages containing those handy, structured formats lately.
A comment about JSON-LD: https://github.com/sean-public/RecipeFilter/issues/22#issuec...
But all of these things stray from the fundamental simplicity of what it does. The code is just 92 lines of JS and works (or breaks!) transparently. If I started adding features, it would quickly become another complex system to maintain and I have plent of that at work ;)
There's a handful of recipe sites I tend to stick to. Smitten Kitchen, All Recipes, Serious Eats, NYT Cooking. I also have a few favorite cooking books: On Food and Cooking, Joy of Cooking, The Art of Simple Food. Then I have some speciality cooking books for desserts, ice creams, and soups.
My wife transcribes recipes we really like to 4" x 6" index cards. The recipe box is up to probably about 200-300 recipes we've collected over our 25 years together.
FWIW, on current iPadOS, Only Recipe isn't showing up in the Share menu for me.
Congrats.
Which, to me, means digital is a bad format - because I'm not going to annotate in my text editor while juggling three burners and the cake in the oven.
I think the reason that people are all upset about the spammy recipe sites is they are too cheap to pay anything for content, so they are stuck with the spammers. The easy solution is to just look at yourself and stop being such a cheapskate. Buy a recipe book. Buy a magazine. Subscribe to a newspaper.
Edit: Oh, there is also a website.
IMHO there are ways to make recipe-scraping resistant to copyright claims.
1. hide all scraping actions behind a login page; that makes content private, hence uninfringing.
2. every time a user "publishes" or shares content, present only an extract of the recipe, like the ingredients and first few steps; expanding the extract sends you to the original site (ideally to the specific anchor of the procedure).
let me know how this goes for private torrent tracker sites
But it’s even more complex than that. The stories are personal. They’re cultural. They’re often told from the perspective of women, immigrants and people of color who have created and invested in a platform to share their stories. The recipe aggregator sites, bloggers note, basically tell the creators that their stories have no value. It’s the same message America has told immigrants and women for centuries, now just in electronic form.
I think that may be taking it too far, particularly since Google effectively created this entire syndrome.
I personally don't give a shit about mathematicians and scientists personal lives, but I don't have a problem imagining those who do. I think the numbers say it all. Others think that the examination of every detail of the person who wrote the numbers first might give them some insight into how to create more numbers.
I'm going to go out on a limb and say that if you polled recipe searchers, the vast majority (>66%) would say that they don't want the story. In fact, I'll back that. If you're in San Francisco, I will bet $1000 against your $1000 that this will be the case and we can equally bear the price of running this. An associate will contact you if you're up for it.
The story writers don't have to write for randos, but I (a rando) rather enjoy the stripping tool. So I think I'm going to install OnlyRecipe.app and if OR's author is pressured by WaPo-like folks to shut down, I'll probably write my own since parsing that schema is trivial.
And I have a day job in HFT so I can't be shut down. After all, no one can boycott me or my products.
If this gets shut down I would love if a general, open-source solution could be developed to spread the capability. A generic Python recipe parser that anyone could hook up to a front-end. If the apps proliferate at a high enough rate they can't all be shut down.
So what you want is for recipe developers to have their work scraped, stripped, and presented outside of its intended creative context and revenue generation mechanism, and while other people may think this is unethical, they can't stop you so that makes it fine.
But rarely do I go on a narrative stroll where I happened to stumble on a recipe that I decide I might make some day.
> It’s the same message America has told immigrants and women for centuries
I certainly won't deny this point conceptually, but it assumes that the stories are even true in the first place.
For example I enjoy pad Thai, but I didn't know it was created by the Thai government in the 1930s until I saw a small comment and did some reading. https://www.theatlantic.com/international/archive/2014/04/no...
Or the history of Lebanese immigration into Mexico that led to Al Pastor. https://theeyehuatulco.com/2020/07/29/al-pastor-and-the-leba...
It has the floating “skip to recipe” button which is handy when you come back to a familiar recipe for some details.
The clutter isn’t the problem as much as the content quality is most often for me.
That they also give you a quick-and-easy "here's just the recipe" page is just an added bonus, for me.
Interspersed liberally with enormous high-res photos of the finished product, the ingredients, stock photos of summertime, etc. And because those SEO tricks seem to work, this type of site absolutely dominates the search results for recipes. The recipes are often fine, too (probably because they're frequently cribbed from cookbooks with a few tweaks).
The "Print Recipe" page usually contains just the recipe in a format which is easy to read without any clutter.
I know this stuff is obvious to an experienced cook, but I can also imagine seeing 14,2g of anything causing some unnecessary distress when trying to work with an unfamiliar recipe.
Maybe something like "1c of flour (approx. 120g)" is a good way to be safe?
If you're looking for an engine for actually doing the conversions, there's GNU units[1] and Frink[2] which both contain databases of these conversions you may be able to mine.
Recipe websites don't include that first 10 pages of a "beginner" recipe book, which usually describes how to measure ingredients and the various cooking techniques used.
¹ 1.5 metric tablespoons, 1.5 × 15mL.
The recipe itself is likely to be a bit less sweet, and my ingredients (purchased in Denmark) are also closer to those sold in Britain than the American versions. Things like types of cream, lack of sugar added to slightly-processed ingredients etc.
But now I see Germany changed the definition at some point, and a 15mL spoon is an Alter Esslöffel, with a Moderner Esslöffel being 7.5mL. Can a German confirm this, or clarify which is used in practise?
The other European countries I've checked use 15mL (if they use the measure at all).
https://de.wikipedia.org/wiki/Essbesteck#Verwendung_als_Ma.C...
So basically TL and EL are not for measurement but used anyway. Things get funny with a "gestrichener" (flat filled spoon) and "gehäufter" (as much as you can fit onto a spoon imho) Löffel.
FTR: I hate volume measured recipes that include flour. "1 cup of flour"...hmm, what does that mean? Guess I'm about to find out.
I generally assume it means to sift the flour into a cup but that is not always the case. Some recipes do not specify, and some do. It's a roll of the dice which is the recipe writers default for "1 cup of flour." Some recipes count on you gouging out a packed cup and some assume you should be sifting. Professionals weigh their flour.
The last thing this app should be doing is trying to figure all this out. Impossible.
I have seen it tried in other services and the feature just got in the way or ruined the recipe.
- easily scale the recipe to make different quantities
- convert units used to one you’re more familiar with.
- wherever the recipe says ‘do x for 10 minutes’ you can tap on the time and it’ll allow you to set a timer for that one piece.
The main thing I've done to find decent recipes these days is to check youtube. Not stuff like 5 minute crafts or overproduced tiktok recipe "hacks", but videos by people cooking in their own kitchen, mostly in real time, talking about what they're doing and why. You can see the whole process and see their technique and be reasonably certain that they know what they're doing on some level.
Here's a few people I always come back to in case anyone is interested:
https://www.youtube.com/watch?v=aNrkDzpgSFY
https://www.youtube.com/watch?v=5dSeHP14Osc
I.e. the twenty paragraph "When I was a child growing up in Atlanta..." followed by a crappy in-house video player followed by, finally, the actual recipe?
My assumption is SEO? For some reason, Google must really like having tons of text on your page, and dislikes simple "here's the recipe"? etc?
Second question - anyone who has searched for recipes also knows that Google will parse out any star rating from the recipe page and show it alongside the results. Which is obviously meaningless because comparing 4.5 stars from grandmas-cooking.net to 4.5 stars from foodnetwork.com is apples-to-oranges. So what's to stop me from simply faking my own star system, then presenting it on my website so that google picks it up in its results? And what triggers Google to look for a star rating? Could I update my tech blog to have a star rating and Google will show it? Or is it limited to keywords like "recipe"?
[1] https://www.copyrightlaws.com/copyright-protection-recipes/
https://en.wikipedia.org/wiki/Feist_Publications,_Inc.,_v._R....
I wonder whether "fake facts" (bogus names, numbers, addresses) are copyrightable. If they are, they can be used to give copyright protection to a collection even when the bulk of the collection isn't copyrightable.
This has, unfortunately, been upheld on occasion. True damages from copying such false entries would be nonexistent, naturally, but statutory damages are blind to such trivialities as justice or proportionality.
Morally speaking, anything presented as fact (including entries in a phone book or notations on a map) should be treated as fact and thus not copyrightable. Something along the lines of estoppel should prevent one from claiming that they are providing a database of facts and then suing the recipient for reproducing copyrightable "creative elements" which don't belong there. Also, selling someone a database of "facts" with deliberate fictitious entries mixed in which are not specifically labeled as such should be classified as fraud and open the publisher up to liability should anyone suffer the slightest harm due to the false entries.
* database rights, which are similar to but distinct from copyright; in particular they last for only 15 years;
* copyright in a particular collection of public-domain things.
Case C-304/07 Directmedia Publishing GmbH v Albert-Ludwigs-Universität Freiburg, which was about an anthology of poems, seems to have involved both things. See if you can make sense of it because I'm not sure I can!
Do you have any other info on copyright as a reason?
[1] https://www.inspiredtaste.net/15938/easy-and-smooth-hummus-r...
[2] https://www.spendwithpennies.com/easy-homemade-lasagna/
[3] https://developers.google.com/search/docs/advanced/structure...
2. I think it also appeals to a certain audience. It makes them feel open minded to other cultures. There's an emotional bond forming with the story or the people in the story.
Don't forget that the average american speaks only one language, yet considers themselves as part of the country that is creating/keeping world peace and that at the same time the average american consumer spends more on average on consumer goods per capita than any other nation in the world. Add to that, that ad revenue is the US is also disproportionately higher than anywhere else.
It helps she writes well and it seems to genuinely reflect the author's life--I think it started out as a personal blog with occasional recipes before becoming a recipe site with bloggy bits bolted on. The text is also fairly helpful, in that it sometimes describes less successful attempts cooking the same thing, or compares it with other dishes ("If you hate X, try [this] instead").
This may be a rare exception though--I agree that a lot of other recipe sites have tons of vacuous filler.
The format of Smitten Kitchen and David Lebovitz's blog have remained unchanged for about 15 years, probably because those authors used the success of their blogs to establish related revenue streams (mostly via bestselling cookbooks). I would be surprised if the blogs themselves still make much money, given how few display ads are included on each page.
But for some random blog that I find while googling? Never.
- The ones that I have noticed do this, also tend to have a lot of ads. So maybe to both be able to show more ads (there is a limit of how many ads you can show if you just have a simple recipe, but add a book above it and you can show many more). Maybe also the ability to add referral links to talked about products?
- It seems like some of them are trying to build a community. They do the whole "tell me about your experience" thing that only generates more page views and "interaction". So maybe there are people that actually follow these blogs and feel like all of that story is personal?
- I am sure there is some SEO stuff going on here like others have said.
From an SEO perspective, yes.
Time spent on page will be less if the recipe is on the top.
When I am looking for cooking instruction, I find my existing library of trusted cookbooks to have a much better signal to noise ratio than Googled recipes sites on the web.
Ie, not step by step, but more general. Let me improvise, but still guide me.
However, that all likely paled in comparison to him gaming the system by paying to host separate sites that linked back to his in an effort to boost legitimacy during the times when SEO was a make or break thing.
"Please, I'll write whatever you want. Just list me!"
This is the crux of the answer. The reason why recipe sites are full of garbage? Because it is effective and profitable.
Top tier ad networks won’t accept your site if it’s just straight up recipes so you need to have the padding to get approved.
And it increases the amount of ads you can squeeze onto the page for higher RPMs
Recipe Schema: https://developers.google.com/search/docs/advanced/structure...
Yes, you can totally fake the # of stars & rating.
If you want to know what categories of things will have especially horrendous (ie clickbait-optimized-to-hell) results, look at the other things that google encourages developers to semantically tag and compete for use of the shiny results page features. A couple interesting ones:
Ecommerce (monetizable sales):
- Books
- Review snippet
- Software app
- Events
Google Maps data ingestion:
- Local Business
Youtube previews:
- Video
- Movie
Job search:
- Employer Aggregate Rating
- Estimated salary
- Job Posting
Knowledge graph:
- COVID-19 announcements (ooo, topical!)
- Dataset
- FAQ
- Fact Check
Recipes are something that people who search for recipes do several times a week, so the algorithms identified this as a Thing with High DAU's. Semantic tags then makes it easier to identify "this is a recipe page", but that means for such a crowded category it's a race to the bottom with optimization and ad-stuffing (more life story == more inline ad blocks).Unfortunately, it's against google's interest to promote to-the-point recipe pages that have fewer embedded AdWords blocks.
Projects like OP probably just parse out the semantic tags and throw away the rest of the content. This could easily be a browser extension.
"pizza pocket recipe" 2nd result is decent: https://foodnetwork.co.uk/recipes/pizza-pockets/
"lasagne recipe easy" 1st result is good: https://www.spendwithpennies.com/easy-homemade-lasagna/
"sushi recipe chicken" 1st result is to the point https://www.tegel.co.nz/recipes/teriyaki-chicken-sushi/
Note that I have adblocker so I don't know how many ads you see and I can't judge the quality as well, buy at least the sites are quite usable. I'd be more pissed off by a missing ingredient than having to scroll a screen or two.
Interesting enough, the big name recipe sites: Allrecipes, food network, NYTimes, binging with babish etc. all are short and to the point. But for some reason the crappy recipe sites outperform them on Google.
Although the optimization is infuriating, in my search to become a decent cook, I have found more success following specific writers instead of a top result/highest rated meal. Many of these writers self-promote (and cross-promote) on sites with the same template as spendwithpennies.com
I wouldn't be surprised if that annoying SEO template was designed in collaboration with Cookbook publishers. The "anecdote before recipe" style was made famous in Irma S. Rombauer's Joy of Cooking, and took on a variety of forms throughout the 20th century.
I think this (or a hybrid approach) was already a thing. See Food Wishes (Chef John), which has been using a similar model for a while.
Actually, video recipes are the best imho: https://www.youtube.com/c/yousuckatcooking :)
Be careful. I also have an ad blocker and sent a fun link to my mom a friend had sent me and she saw Alllllllllll the ads. It was not a fun link for her. Didn’t even think of it before sending.
I get that some WP themes are more popular than the bazillion available, but the consistency in look and feel between a Malaysian immigrant to New York cooking curries I know aren't that Malaysian and a stay at home mom in Ohio doing baking that may have been passed down by a great aunt that tweaked a King Arthur Flour recipe is often remarkable.
As a child growing up outside of Atlanta, this is how we were typically taught recipes.
"One day, when you're sharing this recipe on a mass communication network that doesn't exist today, make sure to (1) mention that you're from Atlanta & (2) include a story about your children / partner / family."
I guess, maybe it's different elsewhere?
> My assumption is SEO? For some reason, Google must really like having tons of text on your page, and dislikes simple "here's the recipe"? etc?
Cookbooks that sell well usually have some introductory text for every recipe. The best cookbooks use this intro to describe unusual techniques or flavor combinations in the recipe, so the intro text in such books can be really helpful and is sometimes critical to getting the recipe right the first time you try to make it. The only cookbook I own that doesn't have intro text for each recipe is a culinary school textbook, so the authors felt safe assuming a certain level of familiarity with the terms and techniques used.
OG food blogs like Smitten Kitchen and David Lebovitz emulated the classic cookbook style, and, not surprisingly, those authors have gone on to make a lot of money writing traditional cookbooks. Contemporary food blogs tend to try to emulate older, successful blogs (maybe because Google somehow boosted recipes with intro text back when such text was usually helpful?) but mostly come off as AI-generated garbage text, made just long enough to create a couple scroll events and artificially lower a site's bounce rate.
Ideally I would expect a page with my question and a number with link to the source. However in the real world I get various pages with somehow related title and tons of text inside I don't need. Often times without the exact number I'm looking for.
I guess that most likely nobody wants to maintain such a resource since it might be hard to make it profitable. Still it might save a lot of time for collective humanity.
https://goodcheapeats.com/simple-rice-pilaf/
versus:
It would be nice if this app would support printing. It does a great job reducing this recipe page to its essentials: https://onlyrecipe.app/?url=https://cookieandkate.com/best-v... but when I try to print, the preview shows a blank page (Safari on Mac).
Honestly, not a terrible way to make money, while offering a free service.
There would be a standard layout, introduction paragraph would explain the history of a recipe and link to other similar recipes. That would be interesting to read.
And there would be an endless number of recipes. For-profit sites are full of ads and SEO optimized to improve user retention/engagement, which make them annoying to use. A wiki could be print friendly and distraction-free, which would be perfect for a recipe.
Then you could, as user, follow users you like. Each recipe would be in structured format, but could also have rich text introductions / explanations, if users wish to add such information.
You could even let users add custom styling to their own namespaces/subwikis, as tumblr, myspace, wordpress, youtube and reddit used to do / still do (with a way to turn this off as user, if you just want the plain content)
This is the way. Publicly read-only repos with easy access to forking and pull requests are far superior to wiki pages with no access controls. Compared to current GitHub you would mainly need to add support for structured data, ratings, and indexing.
But I see the wiki more as a reference book on recipes and their well known variations (which is mostly what I'm looking for when searching for a recipe) than a sharing platform/pseudo social network.
No. In many cases there are N variations that all claim to be the standard.
Here's an example page of one recipe: https://www.chefkoch.de/rezepte/343371118405722/American-App...
Here's what began as my wife's banana bread recipe many years ago: https://en.wikibooks.org/wiki/Cookbook:Banana_Bread
- Skim a few recipe sites for anything new I want to try
- 1-click import them to Anylist (using the browser extension)
- Add recipes to the weekly meal plan in Anylist
- Click "Add all ingredients" for each recipe, which automatically puts all ingredients for the recipe into my shopping list.
One of my favorite things is that it automatically categorizes the list items by store section, making the shopping much easier.
It doesn't work with every recipe site, though (traeger.com for example), but it works with most.
There are two features I wish it had that would make it nearly perfect:
1. Ability to create my own categorization rules. For example, "whole peeled tomatoes with their juices" gets categorized as beverage, and I can manually recategorize that specific item, but it would be nice to create a rule for wholepeeledtomato* that puts it in the "Canned Goods" category
2. The ability to exclude ingredients from being added to the list. I always have salt, pepper, and olive oil on hand, but I end up having to manually cross a dozen of those off my shopping list when I add ingredients for the week when nearly every recipe inevitably includes them.
It was featured in the MacOS Big Sur keynote being used with Safari but sadly hasn't made it to the App Store yet.
I get the authors are doing it to boost Google rankings. But why do I only see it on cooking blogs, and not on blogs about cycling, DIY, programming, urbanism, whatever else I'm searching....
Not many tech blogs start with a 4 page life history before showing me the code snippet I'm looking for.
Unfortunately, she's no longer with us. However, her Rust continues to be a part of our lives.
The Rust you buy from shops today just isn't the same.
I lived with a food blogger for six years and might be able to provide some more perspective for these types of comments (beyond just SEO).
First, there's actually an audience that _is_ interested in this type of content. Some are repeat readers who want to follow food bloggers' lives, similar to how HN readers might follow a streamer on Twitch. It's a much more rewarding journey if people don't just see you as a recipe database and bounce, but actually engage with you and follow you over time.
Second, a lot of food bloggers simply enjoy writing and see their blogs as a way to express themselves. Some of them write these stories for their family and friends and didn't think they'd be at the top of Google.
Third, it takes a ton of effort to write a single recipe. I can't speak for others, but hers involved multiple days of planning/cooking/shooting, remaking it several times so she knew it'd be consistent for the reader, planning/shooting/editing the photos, and even scrapping recipes altogether if they didn't work out. She also had to deal with the business end of things (like getting a lawyer, accountant, social media manager, and managing contracts with sponsors). Her attitude was basically, "if I'm doing all of these things to provide someone with a free recipe, they can scroll past my story if they don't feel like reading it". (That being said, her site was pretty minimalist compared to other food blogs – she didn't run ads.)
FWIW, I don't have a problem with onlyrecipe.app, I just wanted to share this because I'd be interested if I didn't know already.
So while I'm sure there exist bloggers who put care into these things, a tiny minority of people seem to find any value there. In fact it now seems that so many people are aggravated by this style that an app to remove them all has been developed.
Like many others I have mostly abandoned blogs in favor of tried and true cookbooks.
similar open-source program plainoldrecipe https://plainoldrecipe.com/
It really successfully imports and de-clutters recipes from any and all recipe sites I've thrown at it. Ben Awad, the programmer behind Saffron, actually posted about their scraping technique on HN to significant success: https://www.benawad.com/scraping-recipe-websites/ (https://news.ycombinator.com/item?id=23142220)
Their UX is unmatched, they've got apps for iOS and Android in addition to the web app itself. Undoubtedly one of my favorite pieces of software.
Since google encourages this and ranks pages with schema higher, all recipe blogs and sites add this schema to their html.
This is structured data. I just parse this json.
Not all recipes follow this though. So you may occasionally see error messages for old sites that have not implemented schema.org structure.
Sometimes the stuff I'm cooking actually turns out differently because of all the mad scrolling I do trying to find the next ingredient to add while my sauce pan is boiling over or whatever. Kindof fun.
Last, recipe books are a great way to get around this crap, and then you're actually paying for the knowledge you use.
I do wish there was a more modern multi-platform alternative. CPM recently stopped updating their iOS app so we can’t use with recent iOS.
Should be fixed in a few days.
I imagine a cache of this simple web shared across all browsers.
Imagine translating all PDF manuals, scientific research, and yes, recipes, in this decentralized manner. The dataset would be clean both for human consumption as well as ML training.
[1]: https://www.food.com/recipe/homemade-curry-powder-38702
You could make an extension that literally calls Print on the page, and turn it into a PDF view from which you can save it. Your recipes could get stored locally or something, so you always have the website URL + clean recipe view stored.
That way you support the site, and you get your recipes without destroying your eyes.
This worked perfectly and will make shopping a bit easier. Example below.
https://onlyrecipe.app/?url=https://www.loveandlemons.com/sh...
For example here: https://onlyrecipe.app/?url=https://www.allrecipes.com/recip...
From my personal experience running a small tech tips site - it seems that I constantly end up further down the rankings cause I refuse to stuff each page with information that is not relevant.
Regarding "How to use?", yes this is an issue on android. If you click multiple times, it will work.
I will fix it.
Regarding http/https, I'll implement that.
0: Safari on iOS 15.2, iPhone 8.
In addition, I would encourage you to try the iOS app. Way better experience.
Because this is a app-first service. Web was built later.
Reminds of Tandoor: https://github.com/TandoorRecipes/recipes
javascript:window.location.href='https://onlyrecipe.app/?url=' + (window.location.href)I can imagine that "just the recipe" is useful for very novice cooks, but most of the time it's much better to learn the patterns and techniques than to follow the precise recipe. You'll be much more prepared that way when things don't go to plan, or when you're missing a few ingredients.
And this may be unpopular here, but I often enjoy the "life story" too: for me, many of the joys of cooking are in the connections made to other people. And if the recipe writer wants to build a connection with the cook because they poured so much effort into the recipe, I'm open to that -- and whatever it may bring to the actual cooking.
(Maybe I should make a "just the code" browser extension for Github that deletes README files ;) )
1. Full of tangential life-story BS
2. Placed far above the content I went to the repo for
3. Filled with advertisements
I would love your browser extension.
Also, you claim the story is "much more important" than the recipe itself. So then I guess you would enjoy these recipes pretty much equally if they completely removed the ingredients of what they actually cooked? It's so much less important, after all.
I guess you guys heard my sighs!!! Amazing. Thanks!
An active comment section tends to be a step above reviews, because at least you can see if other people find the recipe too spicy, or boring, or an exciting base for other ingredients. And no, 2 comments that say "I loved this recipe!" and "Thanks!" isn't sufficient. This is usually how you can tell a recipe on an aggregate of authors like FoodNetwork, AllRecipes, or NYTimes is legit.
In my opinion, one step above an active comments section is following individual recipe writers that you jive with. An individual writer will usually have a measurement of success that you can agree with (health-conscious, budget-friendly, unique flavors, wide appeal), so you can understand their motivation better. Also, they have some credibility on the line. When you find writers that you agree with, you may even find their "filler" text to have some substance (another reason a "poseur" would feel obliged to include vapid copy before their recipe).
It started out as a joke but I have made a point of picking a recipe out of it every week to try.
The stone soup one is fun and a nice story - https://based.cooking/almeirim-stone-soup.html
You can also submit recipes on the Github repo - https://github.com/lukesmithxyz/based.cooking
/end rant.
Where is the limit ?
For me it's just a web browser optimized for recipe websites. It's basic scrapping. Google does it, why can't I do it ?
Are "reader mode" browser extensions theft ? Are ad blockers theft ?
Is using Lynx as a web browser theft ?
If your business depends on your content never being scraped, you are screwed.
Ad free recipe sites are already handled, you pay a subscription fee instead.
That being said, the final format of an onlyrecipes scrape is very attractive! It would make for a nice intentional feature of recipe website, so the producers can still get their impression revenue and the readers can enjoy such a pleasing format
Specifically creating products to damage these people's returns because of your inability to scroll, use page down, ctr f to move quickly to the information you need is your own weakness and it doesn't give you a right to someone else's labor. You know that without a long ethics conversation. Most recipe writers will fail hard and most who try to create revenue through the ad model fail hard. You want unrestricted access, pay a subscription fee, just as you would expect for your own efforts.
There is no Grey area here, you know and understand the problem and the excuse of laziness or the importance of your time for a 30 second operation wouldn't hold up with anyone.
If enough people like it, I will make this a full-fledged service.
And focus on adding features like dark mode, server-sync, sign-in, account management, export/import of recipes, sharing screenshots of recipes like this one directly with your friends https://i.redd.it/kk1goqsswo981.png
[0]: https://apps.apple.com/us/app/mela-recipe-manager/id15484660...
Not only do they did rid of the novel about the ingredients and their origins, they also get around most paywalls.
The thing that would make me instantly switch to any other manager is an app that would parse recipes from the various YouTube and TikTok videos. If you follow the right accounts these videos are a gold mine.
It's not like they're paying them via some publisher program, just pure scraping and re-organizing.
What? HN doesn't encourage its users to bypass ad- and subscription-supported content.
Oh wait, it does. https://news.ycombinator.com/item?id=10178989