When people inevitably start building on the **other stuff**, is it more likely that the applications will be walled off on private relays or some how find a way to filter public relays?
For instance, if someone chooses to develop a nostr based market place, how would they go about insuring that the events in their site aren't flooding note based clients?
We def need a decentralized lightning or bitcoin integrated E-bay or Amazon situation.
That’s where the concept of different Event Kinds come in. If an event kind is added to the protocol that specifies it’s a product listing, a client like Damus won’t show those unless it specifically includes that event kind in its feed
Ahh gotcha, didn't realize different even types could be used in that way. To use a special event type in an application would it need to be "registered" in any way or do you just kinda go for it?
You'd probably need an NIP on https://github.com/nostr-protocol/nips giving details of the new event type & how it's to be handled. Atleast that's what happened for zaps & badges
^ what #[4] said
It’s really a shoot first, make NIP later system, since NIPs are encouraged/required to be implemented somewhere in production before they are approved.
Thanks friend, this is what I was looking for! Wasn't sure if it was a before or after you have a proof of concept kinda thing. Thanks for your help
Many people go ahead and open a proposed NIP as a pull request to get feedback before implementing. That's still a good idea I think. But the NIP readme says they won't be merged until they're being used for real.
Oops, I meant to reply to your message here. Replied to root instead.
