👀
nostr:npub16dhgpql60vmd4mnydjut87vla23a38j689jssaqlqqlzrtqtd0kqex0nkq is this marketplace spec converged yet?
#FYI to anyone who is listing items for sale on a NIP-99 based Marketplace, such as on #Amethyst, #Shopstr, or Cyber.Space:
You absolutely WILL miss sales if you are not using a client that supports NIP-17 DMs. This is because Shopstr only notifies you of sales using this DM spec and sends you the payment as eCash tokens retrievable via said DM.
If you can't receive NIP-17 DMs, you will never know that the payment has been sent, but the buyer will still be out the sats.
There are plenty of clients that now support NIP-17 DMs. Here are a few:
#Amethyst
#Coracle
#0xChat
Why has Shopstr made this decision? Because NIP-17 DMs are quite a bit more private than NIP-04 DMs, since less metadata is leaked. Similarly, eCash as an in-between for payment is great for receiver privacy, which is not great by default on Lightning. Yet because there are still several popular clients that do not support NIP-17 (maybe waiting for something even better that nostr:nprofile1qy2hwumn8ghj7erfw36x7tnsw43z7un9d3shjqpqzuuajd7u3sx8xu92yav9jwxpr839cs0kc3q6t56vd5u9q033xmhsz294jr is working on?) it creates a frustrating experience for both buyers and sellers.
Discussion
I don’t think the marketplace spec is converging. Nip-99 classifieds are not the same as storefronts or e-commerce shops.
No, but I believe it's a valid use case to extend it to allow e-commerce without removing the classifieds. This is a natural evolution, as e-commerce clients using Nostr have adopted NIP-99, which requires a custom implementation for checkout, communication, and other features, and this has led to confusion and poor user experience for both merchants and customers.
Oh yeah. That feels reasonable. I always thought the marketplace nip was really heavy weight for simpler use cases