someone-build

Cooking recipe tooling:
1. Import a recipe with normalized format and units (LLM?)
2. Find similar recipes we've already logged and add as a variation if they exist, include a diff summary
3. Log of when we've cooked the recipe, with any notes and modifications.

Preferably storeable in Obsidian-friendly markdown.

Bonus project: Goodreads for recipes (all stored in this normalized and cross-linked variations way).

There's things like cooklang, it's a good starting point but somewhat janky and barely maintained.

A doodler and computerer. I like permissive/permissionless open source, smart contracts, p2p systems, room-scale VR, and NixOS.

shazow.net

Currently: WhatsABI

love my Tandoor selfhost, it's django+drf based so ive been looking into integrating an llm either via gpt actions or some kind of custom bridge, llm would be a huge upgrade to cleanup sloppy imports or suggest variants, i imagine i could even show it a fridge pic for inventory and ask it to suggest the fastest recipe

Full-stack digital product consultant @ BoundCorp.net - eng @daylight

it does handle for #3! you can log cooking with comments but i don't usually fill that out bc it's too much data entry. it also helps with your concern about processing recipes, as the import tool can read most existing websites, but it does have some issues with putting the right data into the wrong fields - i think a Tandoor LLM integration could help with #1 and #3 by providing easier natural language interfaces and leave me doing less weeding.

Looks okay, but don't think it solves any of the problems I have on that list (and ugh that license).

I'm honestly happy to just use markdown plus a tool to import things coherently. Processing recipes from various websites and normalizing units/portions is such a pita.