[scrps]

A feature I think would be helpful would be a reverse shopping list (for lack of a better term) where you can say 'I have ingredients a, b, c... list what recipes do I have all or ≥ n% the ingredients for?'

I shall poke around the cli code.

[thebricklayr]

I just added multi-ingredient keyword search across all of your recipes to Umami (https://www.umami.recipes). If you’re on iOS, I’d recommend checking it out!

[scary-size]

Looks promising! I’ll give it a thorough test. Been working on my own recipe clean up tool [1]. Does your app all the scraping and parsing on the client side?

[1] https://pretty-recip.es/

[thebricklayr]

Wow, this is awesome! Your layout, subtle dividers, and serifed font really come together perfectly.

At the moment, Umami's scraping is done server-side. I'd really like to speed it up, so I'm going to start working on a 100% client scraper soon (for the native apps & browser extensions; the web version will always have cross-domain browser restrictions though).

[samldev]

Umami looks great, I just sent it to my wife who just uses Apple notes for recipes right now. I’m curious, how can you offer it for free while having server side processing / syncing etc?

[thebricklayr]

It's few enough users right now that I can cover the couple bucks per month in server costs. If more people start to use it, I'll make it paid (either upfront or subscription, not sure yet), but I'll grandfather all existing users as free.

[scary-size]

Interesting, does the server fetch the html itself? Or does the client POST it? The letter would be useful for paywalled sites like Cook‘s Illustrated. I spent quite some time on ingredient labelling (what’s a unit, quantity etc.). Feel free to ping at hn[at]franz.hamburg

[thebricklayr]

> does the server fetch the html itself?

Yep, the client just sends the recipe URL and then the server fetches the HTML. Agreed, it would be better to have the client send the HTML for paywalled sites, which is another reason I just want to do it all on the client.

> I spent quite some time on ingredient labelling (what’s a unit, quantity etc.)

I can relate to you there. It was a long process of trial and error for me to get right, and there are still plenty of edge cases left to handle. Long-term I think AI + NLP will make this kind of thing easier, but for me it wasn't fast, reliable, cheap, or portable enough to run in an iOS app in real time quite yet.

[scary-size]

Nice! I dabbled with deep learning and CRF for the sequence tagging. I ran in the same issues you mentioned. Current approach is hand rolled. The „holy grail“ would be linking ingredients mentioned in the directions. So, I could just tap on „…vinegar…“ in an instruction and see that I need 2 tbsp.