{"type":"rich","version":"1.0","title":"Niel Liesmons wrote","author_name":"Niel Liesmons (npub149…g722q)","author_url":"https://yabu.me/npub149p5act9a5qm9p47elp8w8h3wpwn2d7s2xecw2ygnrxqp4wgsklq9g722q","provider_name":"njump","provider_url":"https://yabu.me","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. \n\nWhether it's an Image generation bot, a T-Shirt, some relay hosting of 2GB for 3 months, a logo design service or a freakin' cucumber, the general pattern is the same: \n\n1️⃣  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...)\n2️⃣  Buyer fills out the Form\n3️⃣  Merchant sends a Bill\n4️⃣  Buyer pays or declines\n5️⃣  Merchant confirms and provides follow up communication (Nostr Mail) and optional status updates \n\nA flow like this means that Apps can support marketplaces for anything from the moment they support Forms, Bills (payments) and basic comms. \nnostr:naddr1qvzqqqrcvgpzp22rfmsktmgpk2rtan7zwu00zuzax5maq5dnsu5g3xxvqr2u3pd7qyf8wumn8ghj7mn0wd68yv339e3k7mf0qythwumn8ghj7un9d3shjtnwdaehgu3wvfskuep0qyghwumn8ghj7mn0wd68ytnhd9hx2tcqpphxjupdvehhymgweqq8q"}