Nostr Web Client

Thank you! That's more a testament to the work that nostr:nprofile1qyxhwumn8ghj7mn0wvhxcmmvqyg8wumn8ghj7mn0wd68ytnhd9hx2qpq5u3cqhx6vuj3rywg0ph5mfv009lxja6cyvqn2jagaydukq6zmjwq5vnrz7 has built out for the nostrcooking tag than it is with anything I've done here. I'm just building on that work to let anyone pin nostrcooking events into pinboards to create their own cookbooks. I look forward to your feedback on the implementation I'm using on pinboards before I publish it as draft NIP.

Seth 1w ago 💬 1

Looks great! I appreciate the kind words, but we’ve just been building off an idea for the past few years.

It is possible that some of this logic will change soon, certainly the tag will go to #zapcooking but also a custom nip for recipes is possible. This has been discussed, and developed but I have not implemented primarily because I have not had any incentive to do so. In fact, it would remove the current interoperability for the implementation of long form notes that work great with clients like nostr:npub1yzvxlwp7wawed5vgefwfmugvumtp8c8t0etk3g8sky4n0ndvyxesnxrf8q and nostr:npub18m76awca3y37hkvuneavuw6pjj4525fw90necxmadrvjg0sdy6qsngq955 . nostr:npub12vkcxr0luzwp8e673v29eqjhrr7p9vqq8asav85swaepclllj09sylpugg filters us out.

I would have to convince other clients to implement this custom nip and then lobby for the approval, which has been part of the reason for the delay. nostr:npub180cvv07tjdrrgpa0j7j7tmnyl2yr6yr7l8j4s3evf6u64th6gkwsyjh6w6 removing nostr:npub1xxdd8eusvdxmaph3fkuu9x2mymhrcc3ghe2l38zv0l4f4nqp659qskkt7a from Nostrapps.com for not meeting the purity spec also fuels my contrarian energy, because I thought this was an open protocol where we can build what we want. 🤷‍♂️

I get it though, and my friend nostr:npub1cgcwm56v5hyrrzl5ty4vq4kdud63n5u4czgycdl2r3jshzk55ufqe52ndy has been a voice of reason and has given me pause, consideration and perspective to think about it, which I am. We’ve been building lately with a maniacal passion, so anything is possible.

Reply to this note

Please Login to reply.

Discussion

Constant 1w ago 💬 3

Now since this concerns perhaps my biggest personal failure of 2025, the topic is a bit of an open wound for me, and I do understand your position as ''zapcooking'' in all of this....but ( 😅 ):

The fact clients were sort of forced to include special behaviors on an existing kind, like primal actively filtering, is the crux here. A recipe kind could/would be a nice first example of ''partial kind rendering'', something i don't think we really have thus far. i.e. a ''general'' client like primal could half-ass the recipe implementation, only showing the bare minimum and pointing their users in the direction of zapcooking for a better/more complete experience. It would be a win-win where Primal only spends minimal time on implementing the kind such that their users don't experience broken references in their feed while browsing primal irt something Primal generally have no interest in putting much effort in anyway, whilst it would give zapcooking (and other potential recipe apps) room to shine in terms of features. Because as it stands, Primal spend that time anyway, in a way that sets a bad precedent (not their fault) for the ecosystem as a whole. Anyway, this whole notion should, in theory atleast, ease the whole implementation lobby process.

Hope you had a good talk with nostr:npub1ehhfg09mr8z34wz85ek46a6rww4f7c7jsujxhdvmpqnl5hnrwsqq2szjqv about it?

Il retreat from the discussion now, ive kind of spend my credits to weigh in anyway, so il just wish everyone a happy new year :)

Seth 1w ago 💬 1

I get it, of course. The challenge is implementing this in a way that allows users to retain their existing work. Zap Cooking is completely self funded and has never received grant money, so you can imagine that a solution which creates a strong disincentive to start “new” while removing current interoperability is not optimal.

Users have also come to value that interoperability, especially with tools like npub.pro, and breaking that would be a disservice to them as well. I remain open minded and haven’t dismissed the idea entirely, and have come around to it more recently. I’ve put real time, money and effort into this project over the past few years, so these important considerations need to be weighed seriously.

maya 1w ago

You should definitely Work on that...that would be nice 💯🙂

Dawn 1w ago

I don't know how many people have opted to self-host npub .pro, but if nostr .band is an indicator, anyone using the hosted service might already be at risk of losing what they've built up. Just another thought to consider in this.

Derek Ross 1w ago

Primal could have shown recipes as blog articles if they wanted to do that. After all, recipes are just blogs. Look at every single recipe website on the internet and you'll find a story about someone's old grandmother or aunt and how her cookies reminded the author about something from their past and then 12 paragraphs later you'll find the recipe :)