A fast, local first, flutter stack that a noob like me can build awesome UI s on, you say? :rocketship:

Oh wow, of I get this right this is pretty cool 👀. Will sit on logo ideas a bit.

An interop :product: Products catalog with fiat payments. 👉 Manage your items and sales in one place and let multiple sites, apps, vendors, ... tap into it. That's something that could really benefit my farm and my local community. If I have 100 bushels of 🥕 and I want to have live availability and sales of these work across: - my local community chat - the orders of the village coop - my own website - resellers - anyone on Nostr How do I even do that in Big Tech land? #noobquestion My own database with an API I let them all tap into? :thinking:

:scoresoccer:

The box is where you meet. Not where you are put. 🌱

They'll keep building bandaids on top of Follows until the cows come home. And given enough vibe they'll forget what cows are too.

Follow pack enjoyoors be like: "Hooray, on Nostr we can interop on putting people in boxes!" Dark pattern = dark pattern. Time to imagine and build the stuff that goes beyond Follows.

I need this: ... to be the same general Marketplace spec as this:

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. Whether 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: 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...) 2️⃣ Buyer fills out the Form 3️⃣ Merchant sends a Bill 4️⃣ Buyer pays or declines 5️⃣ Merchant confirms and provides follow up communication (Nostr Mail) and optional status updates A flow like this means that Apps can support marketplaces for anything from the moment they support Forms, Bills (payments) and basic comms.

We have :app: App Releases and :repo: Repos. (both showing up in Communities') What release event do you need besides that?

I get that. I'm just trying to observe what I can from this thing we live in. Also have a 3yo with tons of questions I honestly don't know how to answer 😉.

364 days 12 months of 30 days 4 inter days Anything else doesn't follow the 6 gates the sun jumps and goes through.

You can just copy-paste in a Markdown / Asciidoc editor and call it a day. Or you can start building for the hyper-linked :Nostr: community knowledge bases you want to see:

Sounds neat 👌 Almost too simple hehe. `e`is not commonly used for other things? If not, lesgoooow!

Would love to find a general way to do 📎 Attachments in the JSON of these sorts of events: :mail: Nostr Mail → referencing and sending along related publications (events) & files (blobs) :task: Tasks → same :event: Events → same Etc... Any ideas?

Wait what? Illegal!? And me I'm pissed I can't sell my raw milk ice cream.

I support the currant thing :salute: #farmstr