GM, its been 21 days since I last coded, lets see if i still remember how to...
Discussion
welcome back
It's like riding a bike, you can't lose it 🫡
10 Print "Hello NOSTR"
20 goto 10
I remember those days … where line numbers were hard coded into the program logic … so we incremented each by 10, to make later additions less painful as the codebase scaled. 😳
Gm
that’s ok many things are vibrator coded now
Good morning ✌️🧡
A quick primer: https://d.nostr.build/Opr3DxwoWKULhMs7.pdf
welcome back
Good morning Kieran ☕️
Two reasons why flutter (or any “write once deploy anywhere” framework) would be a wasted effort for zap.stream … for event producers, like nostr:npub1h8gzew8am6cezuq7cpjgudldra40hgnruqrqlsrqnxnzs5wjtczqztps02 and nostr:npub1m2urt08mv7ert24gzcarejj92hxd3psggzflcf52kv5c54c2nmkst0ydeh.
1: Custom invite links and QR codes are onboarding gold, and how live events go viral. But these cannot be followed into native apps … that haven’t been installed.
2: Acceptance into app stores is just another (unnecessary) barrier for small business apps, especially ones that allow “zapping for content” transactions.
IMHO, the future of zap.stream (and a funding source for open-source development) is as a “white labeled” platform for event producers. Custom web apps with “low cost of entry” (for all parties) is how zap.stream wins. “Write once deploy anywhere” is a high tech solution that “sounds good on paper”, but in reality doesn’t solve the actual problem of “nostr login sucks for mobile web apps”.
How to fix Nostr login for mobile apps? This is the question to ask, and the first on my mind as I dive in to help with zap.stream for event producers.
You never forget how. You only forget why.