Show HN: TasteSpotting meets StackOverflow(fridgetofood.com)
fridgetofood.com
Show HN: TasteSpotting meets StackOverflow
http://www.fridgetofood.com
9 comments
I agree with everything you said. To address the lack of recipes I'm offering to import recipes from the blogs of food bloggers who register. Doing it by hand for now, want to automate it eventually. Automating is a more difficult problem than I thought at first, so it's on hold.
I hadn't thought of your second point before. I don't think it would effect the search right now. The way it works right now is entirely text-based. It checks for an exact ingredient match (by name) and assigns a high relevance for each one. Then it looks for partial ingredient matches and assigns a much smaller relevance. Then it aggregates the relevances to order.
A planned feature is to allow high reputation users to set ingredient relations. So they could mark two ingredients as substitutes for each other. I suppose I could have some ingredients be marked as common and automatically assign relevance for them as if they were included in the search.
I've also been thinking about how to do a sort of general ingredient relationship system and how to utilize that for search. So far I'm ponder parent child - so ground beef would be a child of beef and ground meat. Beef would be a child of meat, etc. Then assign a relevance to ingredients that are found some number of steps out on that graph. The relationships could be set by high reputation users.
As to the issue of quality, I'm hoping to source food blogs. A lot of food blogs have high quality recipes in my experience. I'll offer links with high SEO value and on site reputation and rewards in return for them posting their recipes. A further filter will be the on-site voting and reputation.
I'll work on these for the next iterations. Thanks!
I hadn't thought of your second point before. I don't think it would effect the search right now. The way it works right now is entirely text-based. It checks for an exact ingredient match (by name) and assigns a high relevance for each one. Then it looks for partial ingredient matches and assigns a much smaller relevance. Then it aggregates the relevances to order.
A planned feature is to allow high reputation users to set ingredient relations. So they could mark two ingredients as substitutes for each other. I suppose I could have some ingredients be marked as common and automatically assign relevance for them as if they were included in the search.
I've also been thinking about how to do a sort of general ingredient relationship system and how to utilize that for search. So far I'm ponder parent child - so ground beef would be a child of beef and ground meat. Beef would be a child of meat, etc. Then assign a relevance to ingredients that are found some number of steps out on that graph. The relationships could be set by high reputation users.
As to the issue of quality, I'm hoping to source food blogs. A lot of food blogs have high quality recipes in my experience. I'll offer links with high SEO value and on site reputation and rewards in return for them posting their recipes. A further filter will be the on-site voting and reputation.
I'll work on these for the next iterations. Thanks!
One thing I'll say is, that in the ingredients columns, experienced cooks know that (uppercase) 'T' is tablespoon and (lowercase) 't' is teaspoon, but why not explain on hover (or just spell it out)?
I imagine units are somewhere in your DB, you probably want some way to control their display programmatically anyhow.
I imagine units are somewhere in your DB, you probably want some way to control their display programmatically anyhow.
That's what I've been looking for. Being honest, that topic really really lacked crowd-sourcing. Most of the recipes are copypasted all over the internet. Q&A should definitely solve that problem. Great job, keep up.
Warning: Big pictures of food inside. (only click when you have just eaten or are about to eat.)
Seriously: Nice idea and implementation. I'll bookmark and hope for much more content to come.
Seriously: Nice idea and implementation. I'll bookmark and hope for much more content to come.
Should have read the comments first, skipped breakfast this morning. :(
Very nice site though, its good to see some quality stuff being made with CakePHP and the idea looks really catchy.
Very nice site though, its good to see some quality stuff being made with CakePHP and the idea looks really catchy.
Looked around for about ten minutes. Very nicely done. One thing that I would like to see is...how to achieve each badge. I see that some users have already received some badges like "Cook" and "Beta Users". It would be great if you link each of those badges to an actual badge page, where you describe users on how to receive those badges. (I'm sure you already have this in mind if you took stackoverflow as the motivation)
Bookmarked!
Bookmarked!
I've been meaning to to just this for a long time, just haven't had the time. I'm glad someone finally did though. Bookmarked. Great job. Hope it keeps improving.
I think this looks awesome. If I were you, I'd take a page out of TextFromLastNight's book and allow users to upvote w/o having to sign in.
Interesting concept. I don't think that anyone's really cracked the code on a truly useful recipe/cooking service yet.
wow, I love it. Your "Add Recipe" page works exactly like mine, but I never made my site live. This is the site I thought was missing but you made it first :-) I will be using it for sure
- You need lots of recipes before you can match them to random ingredient lists*
- It needs to be aware of expected ingredient availability. I always have pasta & rice. I never rarely have sundried tomatoes or salmon fillets without a prescribed use. I will usually search with the latter.
- It needs to be aware of substitutes. I can usually substitute spaghetti for fettuccine.
I like the visual presentation. I would definitely use this if the recipes are good. I still haven't got a go to place online for recipes. Quality seems to be a tricky issue. It could be an interesting problem to solve.
* It worked well with 1 ingredient only, maybe you should remove the instructions telling me to search multiple ingredients for now.