<oembed><type>rich</type><version>1.0</version><title>Niel Liesmons wrote</title><author_name>Niel Liesmons (npub149…g722q)</author_name><author_url>https://yabu.me/npub149p5act9a5qm9p47elp8w8h3wpwn2d7s2xecw2ygnrxqp4wgsklq9g722q</author_url><provider_name>njump</provider_name><provider_url>https://yabu.me</provider_url><html>If any Nostr Product or Service listing just includes a Form event that the Merchant needs you to fill in, you solve most of the issues that all the current weirdly specific specs have. &#xA;&#xA;Whether it&#39;s an Image generation bot, a T-Shirt, some relay hosting of 2GB for 3 months, a logo design service or a freakin&#39; cucumber, the general pattern is the same: &#xA;&#xA;1️⃣  Merchant announces product / service + adds Form with fields for the data he needs back to create a Bill for you (this data can be a shipping address, a prompt, contact info, filter options, etc...)&#xA;2️⃣  Buyer fills out the Form&#xA;3️⃣  Merchant sends a Bill&#xA;4️⃣  Buyer pays or declines&#xA;5️⃣  Merchant confirms and provides follow up communication (Nostr Mail) and optional status updates &#xA;&#xA;A flow like this means that Apps can support marketplaces for anything from the moment they support Forms, Bills (payments) and basic comms. &#xA;nostr:naddr1qvzqqqrcvgpzp22rfmsktmgpk2rtan7zwu00zuzax5maq5dnsu5g3xxvqr2u3pd7qyf8wumn8ghj7mn0wd68yv339e3k7mf0qythwumn8ghj7un9d3shjtnwdaehgu3wvfskuep0qyghwumn8ghj7mn0wd68ytnhd9hx2tcqpphxjupdvehhymgweqq8q</html></oembed>