Oddbean new post about login | logout Am I in trouble? 😂 It’s a team effort. @tijl developed the original concept, @jack has been working on additional development with design support from @Karnage. @The: Daniel⚡️ developed the logo and @Sarah SoupBox [Zap.Cooking] is working on content and marketing.
sounds like a recipe for success
This is why we can never lose our @5c508c34.
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.
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 🤔
Are there other clients? We don't have to trash the current recipes, we could do a transition by doing a [REQ, legacy, {kinds: [30023], #t: [cookingwhatever], until: 2024-09-04}] and then only fetch recipes on the new standard going forward. Does it work? We’re so early! I don’t know if other clients exist even..
100% agree with this. I would love a standard kind for recipes. Instructions and ingredients could be in tags or something.
Unrelated, but I also think the current approach of just blasting recipes everywhere and then connecting to 50 relays and trying to download them isn't going to work in the long term since it can be spammed and will be infeasible when a lot of people come. A mix of followers + WoT and outbox model, like-based recommendations and relay-based curation is the way to go in my view. That's kind of what I implemented on https://wikistr.com/ and I think it be improved and tweaked but applies to all these other-stuff use cases like recipes. What do you think?
Side note, because I dont know what any of this means: Ideally I would like to have a Zap Cooking newsletter type long form post featuring new zap.cooking recipes, articles, and all that jazz that shoots out to all of nostr if they are following the zap cooking, and then people are allowed to share their recipes on their profile (key) as an option or share it to their business profiles (shared key with team members) or gets posted on long form apps like highlighter. Automattically posting on newsfeeds might not be for all people, some people might just want to create a collection for themselves. I would like to offer the choice for the users.
Could there be some sort of regular roundup with autogenerated content showing highlights of what’s been added or most popular recipes?
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 https://cooklang.org a while back. Not sure if markup formats make sense within nostr, but maybe some lessons can be learned.
Good lord... What an idea. Imagine releasing an AI assistant to it.
Yeah, DVM where you give it whats in your fridge and it finds a recipe within the new recipe kind.
The team discussed this and thought it would be so fun.
@arthurfranca here's a NIP you should write.