But not every app need a different message kind.
Actually, the beauty of #nostr is its interoperability between apps, imo.
Different apps managing the same messages kind.
Discussion
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').
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
Yea cause it makes sense to have to open another app to create a community and approve posts.
Like?