I was just thinking that it would be good to define a standard for recipes on Nostr, probably with a different kind, with some relevant tags. The current way is kinda bad because it abuses the long-articles NIP and then includes some proprietary (and very long) "t" tags. Do you have any thoughts?
And then we need some other client to prove that the standard is good and then to show how can you display or interact with recipes differently.
Login to reply
Replies (8)
Can’t stop laughing 🤣
I don’t know if it’s the same elsewhere but in the United States the first ingredient is what goes first. This may be obvious to those in US but different elsewhere. IDK 🤷🏻♀️
This would help solve content discovery problem, assuming that clients would embrace, but would also take away from current client support. I get it though trying to keep long form clean and true to form. It’s something worth exploring, would love to hear additional feedback from other client developers 🤔
I would love to see a feature added to zap.cooking that’s as easy as how cooked.wiki works, where you can link a recipe from a normie site filled with ads and bullshit and it strips out everything but the essential details and adds a step-by-step checklist and a portion calculator.
I came across
a while back. Not sure if markup formats make sense within nostr, but maybe some lessons can be learned.

Cooklang: recipe markup language
Cooklang – Recipe Markup Language
Cooklang is a markup language for recipes.
Good lord... What an idea. Imagine releasing an AI assistant to it.
@arthurfranca here's a NIP you should write.
That's truely amazing haha