Damus
Seth · 80w
Am I in trouble? 😂 It’s a team effort. nostr:npub1q7klm2w94hyq3qdm9ffzpahrrq0qcppmjrapzhz0rq6xgq3fdrnqr6atmj developed the original concept, nostr:npub1chakany8dcz93clv4xgcudcvhnfhdyqutprq2yh72...
fiatjaf profile picture
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.
52❤️1👀1💯1🤙1
Vanellope von Schweetz ✨🦄🌈Glitch🌈🦄✨ · 80w
Can’t stop laughing 🤣
Vanellope von Schweetz ✨🦄🌈Glitch🌈🦄✨ · 80w
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 🤷🏻‍♀️
Seth · 79w
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 deve...
The Daniel 🖖 · 79w
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.
nostrich · 79w
I came across https://cooklang.org a while back. Not sure if markup formats make sense within nostr, but maybe some lessons can be learned.
fiatjaf · 79w
nostr:npub1l3cgtsurhfchg4cyhhqudm70074sr96srhje330xc5m6czej5n9s9q6vs2 here's a NIP you should write.