while working on seamlessly handling NIP-07 signer integration and user profile enrichement from kind-0 events, I realized how much compute we probably collectively waste by reimplementing the same thing in all the vibe-coded apps. is it time to work on nostr SDKs for web and mobile apps..??

Unlimited fresh mint in 3, 2, 1... 3D printing & urban farming towards more self-dependent living

✅ you pay for your VPS server via lightning, no kyc ✅ you spin up your PoC nostr app ✅ you publish your custom event to the public relays ✅ the relays accept it ✅ your app sees the event on the relays ✅ your app fetches the kind0 event you initially published via primal (totaly different client than your app) through your pubkey on the custom event ✅ everything just works together if this isn't magic, idk what is the whole app is still janky af but I am so happy

what do the cool kids use for non-kyc linux VPS paid for in sats these days? #askNostr

Trying to hit the balance between "Look, nostr apps are cool" and "#$%@$# WHAT IS NOSTR, IT IS SCARY" - check signer presence in a calm and human way - explain what's happening - make it clear that signed npub is all we need - support full blown user profile based on kind0 if available

The final verdict is in - cherry tomatoes are very much NOT suitable for the hydro tower. We're calling the lumberjack in and starting from scratch soon

honest review of Nostr from a new user: "it's like yelling into a black hole, you can throw the wildest stuff in and nothing ever echoes back" web-of-trust is a cool concept but it doesn't work well for content discovery and new user engagement imo

Deriving identicons and gradient banners from pubkeys is my new favorite thing while working on nostr based apps.

asking my agent to refactor a huge chunk of my codebase and at the same time asking the same agent for the best ratio of eggs, flour, and milk for pancakes...we really are living the cool timeline

can I get some pointers for if I'm making an app that's mostly targeting non-nostr population but don't want to implement identity in my app? basically, my app is yelling: I'm running on nostr, nostr is cool, use nostr...but I can't give you the keys. What are my options for non-read-only users these days? maybe someone from @primal?

Only when you're out of tokens and you have to talk to the dumb model, you realize prompting the apex model "JUST DON'T BE DUMB AND FIX IT" wasn't probably worth the 1.2M token codebase scan that resulted in precisely nothing. 🤦

I'm a generous god. Letting one of the cherry tomatoes live to see it through. Forking the rest of the tower into a new one. Behold the tiny basil tower 🗼🗼🗼

Lesson of the day: Regular cherry tomatoes do no good in the hydro tower. They require a ton of space and gulp up all the water. Had to put most of them down 😭

Only once you spin up a local nostr relay and start messing with it, it really clicks, and you realize how much more nostr really is than just a decentralized social network. There is so much to build.

Huston, we have a tomato problem....turns out that cherry tomatoes are NOT very suitable for hydro tower. Stay tuned for future development 🌴🌴🌴

Can someone micro-zap me please just to test my wallet setup? #plebchain

The tomatoes are growing too fast and the lights had to be relocated out of bounds. Maybe I should have done my homework on which varieties are suitable for hydro towers 😅

Steven the Stinkbug is the latest resident of the hydro tower. Welcome, Steven!

Tomatoes coming up nicely - in February, in a tiny apartment. I think we're onto something!

Are there any good docs for using the @routstr chat for someone who has little experience with cashu? Something like follow these exact X steps to get from zero to get your prompt answered without losing all your sats accidentally?