No worries, I working on Zap.Cooking's monthly newsletter, seth asked me to help with ...

npub1n0p…pfp6

2024-11-23 02:07:49

in reply to nevent1q…xss3

No worries, I working on Zap.Cooking's monthly newsletter, seth (npub15u3…05rq) asked me to help with content coordination. So I am trying to see what works with what. Nostr is still a baby and needs a lot of work to make more apps interoperable between clients and other apps. Ideally I would love for a content creator to go to highlighter and do their business. Then their business gets picked up by all the other nostr clients and apps and gets plugged in according to what is submitted. So if I PABLOF7z (npub1l2v…ajft) added a recipe feature on his highlighter app for drafts, it would automatically submit that to zap.cooking's database, AND the recipe can be seen on all the client's feeds or specific groups. The creator would only have to one thing, and it would get distributed appropriately. This is a wishful wish for zap.cooking to be an added feature on these types of nostr apps, because it would draw more people to it.

I also like the idea of the content creator being able to provide the back story of their recipes and fun facts that go with it, but then if someone just wants the recipe, its in zap.cookings "database"

Author Public Key

npub1n0pdxnwa4q7eg2slm5m2wjrln2hvwsxmyn48juedjr3c85va99yqc5pfp6

Seen on

wss://relay.damus.io wss://relay.primal.net

Show more details

Published at

2024-11-23 02:07:49

Kind type

1 Short Text Note

Event JSON

{ "id": "4d2cf50ca14aff1707bde66eeb7352b5fc6d00dc15134bc87f46a6fa660ec282", "pubkey": "9bc2d34ddda83d942a1fdd36a7487f9aaec740db24ea79732d90e383d19d2948", "created_at": 1732327669, "kind": 1, "tags": [ [ "e", "079f497d99a205a4d446ed77a8f9d4523d1c320dabc0897fd60019d71169585f", "wss://relay.nostr.band/", "root" ], [ "e", "22099b84c6010eae64f9d45604652328d7820c4de32582d8e397df15ad75d593", "", "reply" ], [ "p", "0c9e5e17fbdf555ef41daf3c3a196749c848f9c791966f30fae5e4c0480e870b", "", "mention" ], [ "p", "a723805cda67251191c8786f4da58f797e6977582301354ba8e91bcb0342dc9c", "", "mention" ], [ "p", "fa984bd7dbb282f07e16e7ae87b26a2a7b9b90b7246a44771f0cf5ae58018f52", "", "mention" ] ], "content": "No worries, I working on Zap.Cooking's monthly newsletter, nostr:npub15u3cqhx6vuj3rywg0ph5mfv009lxja6cyvqn2jagaydukq6zmjwqex05rq asked me to help with content coordination. So I am trying to see what works with what. Nostr is still a baby and needs a lot of work to make more apps interoperable between clients and other apps. Ideally I would love for a content creator to go to highlighter and do their business. Then their business gets picked up by all the other nostr clients and apps and gets plugged in according to what is submitted. So if I nostr:npub1l2vyh47mk2p0qlsku7hg0vn29faehy9hy34ygaclpn66ukqp3afqutajft added a recipe feature on his highlighter app for drafts, it would automatically submit that to zap.cooking's database, AND the recipe can be seen on all the client's feeds or specific groups. The creator would only have to one thing, and it would get distributed appropriately. This is a wishful wish for zap.cooking to be an added feature on these types of nostr apps, because it would draw more people to it. \n\nI also like the idea of the content creator being able to provide the back story of their recipes and fun facts that go with it, but then if someone just wants the recipe, its in zap.cookings \"database\"", "sig": "1a395f98e9653ef4293909a47ace380724472a1b94471df058faa9636265cfb8ea6ceaa6c64a49e34abb11cdbb85fbf93365c84426b5240ea2eacd7c40f8db3f" }