The bitcoin logo on the tarmac.
Tallinn, Estonia, April 2018
You can bake them in the oven too 😎
My co-founders are normies, they aren't very familiar with Bitcoin, and have never heard of Nostr. 😔
However, I want to make the case to them why we should integrate nostr into our newly-launched e-commerce app.
I have a few ideas in mind, but would love to hear your thoughts.
🙏⚡ 🧡
Probably not a good idea, after all.
Why add more burden on the relays, when this could be handled by the clients? 🤷
Gossip protocol to the rescue?
note1lj5zlvgvceetjvy2c340vufv2nyt9zujcrysj44w60d2p74nvs4q8mp2sp
All nips, except nip-01, are optional. Clients and relays choose which ones they want to support.
A client would not push a note to a relay, unless this one supports the nip defining the note, or if it does, the relay would just discard it.
Also, I think it should be technically possible.
There's a NIP for this already, but it hasn't been merged yet.
We could define a new 'nLockTime' tag with a parameter that could be set to either a future date for scheduled posts or a past date for drafts.
nLockTime and content can always be modified using replaceable events (nip-16)
Just a thought...
The first time I read nip-02, I thought it was trying to achieve this goal of having multiple follow lists, but it's not quite that...
What do you think about the idea of "timelocked notes" to create draft notes or schedule posts?