Replying to Avatar Sirius

Current message kinds are for social networking, but if you wanted online stores for example, you'd have to define a new set of message kinds.

Unless you have a k-v storage / graph database. Then you can do nostr.put('npub123/store/items/socks/description', 'Pair of alpaca socks').
Avatar
pet 2y ago

A new message kind for products on sale could be a nice idea, that's true.

One for offers and another one for requests.

These message kinds should then be used by different implementations of online shops (webs & apps). An eventual #nostr-uber and friends could use these same kinds

Reply to this note

Please Login to reply.

Discussion

Avatar
Sirius 2y ago

I mean it would make things a bit complicated if developers and nostr relays need to start caring about message kinds for all sorts of different applications. That's why key-value storage or graph database would be easier, and also solve issues like accidentally overwriting your whole contact list when editing just one entry.