Replies (29)

Just tried plektos out - it’s super fast. You vibe coded this? What tool did you use? Well done 👍👌 FYI we’re doing nostr stuff as we speak, take a look at some of my past notes, I’ve got lots of questions 😇
Nice! Look forward to trying it out. We’re adding NWC ticketing now, it’s looking really good. We’re taking baby steps here since our users are not technical at all… our priority is UX / being SUPER user friendly, and we have a bunch of features that event hosts are asking us to build. We’re a super small team so there’s only so much we can build at once. You get it! But expect more nostr stuff soon :) Goose is great. I’ll try the others too! Thanks 🙏
I'd be curious how you see ticketing working for your app. I have ticketing on Plektos but it's via zap receipts and I've found that these are unreliable. We need something that's Nostr native and decentralized that works better.
Ticketing is complicated. Live events are the golden opportunity to onboard both to bitcoin and to Nostr … but in order to embrace this, the “first touch” event entry point needs to have on-rails built in. “Pay in fiat or BTC … Get new Nostr nsec or use existing. Load wallet with sats from fiat ticket fee…?” I’m tackling this right now for Tunestr… but it’s much easier to solve for a single “company” than an open app to which anybody can post events… 👀
I am using mkstack and began with the default Dork. How can I switch to Goose in the middle of the project? What are the negative aspects of switching? Will it forget that the project is about or forget any context or anything that Dork learned while working for me? I'm totally new to this @Alex Gleason
Ok, another point: I saw the vibe coding Session of Derek and saw there sometimes Mkstack gives random names to Nostr users. I had the same issue. Is there a way to update mkstacks so it happens less often? Thanks! Ps: I'm having lots of fun and now can feel the enthusiasm! I'm calling everybody to talk about it and can't shut up! Haha!! #vibecoding #grownostr