we’re early! it will improve!
this is the mantra nostr:note194n247lecqgcskk5rmmfgrapt4jx7ppq64xec0eca3s4ta3hwkrsex7pxa
nostr has its issues. but for those who figure it out, it’s the most powerful network that exists today. challenge is helping more people figure it out.
likely most of that won’t come from social use cases, but rather the microapps that #[0] originally envisioned and folks like #[1] are focused on building.
the power of this thing is the ecosystem part. it’s permission-less, meaning anyone can build whatever they want, and it has a permission-less global payment system readily available through bitcoin. but neither will sell people on joining it.
if the apps built on top of nostr do valuable things, like https://highlighter.com does, then every nostr app and use case benefits, including the social clients.
this is going to be a long road, but one that fundamentally changes the way people experience the internet. if it doesn’t succeed itself, it will certainly inspire the thing that does.
well said 🫂
life hack: food-safe gloves for handling meat in the kitchen 
speaking from personal experience, many men do not learn emotional intelligence.
gm, today I tried butter in my coffee and I do not regret it. thanks #coffeechain
this exists: https://github.com/benthecarman/nostr-tx-broadcast
twitter is a shitcoin
#runningnostr 
💥 🛹 nostr:note12r9ezsyu9hsh6narplahf2ph7vec7m5xulc0d5gnt69hvp022ylq52xlxs
this would enable cool stuff like localized relays.
when will clients stop blasting notes to ALL relays and allow users to choose where they r/w notes?
what if we treated relays more like subreddits where your current context is scoped to a relay(s)? 🤔
hey #[4] what’s the status of your wrapped dm stuff? seems I cooked up a very similar idea on the couch last night 😂
nice find! this is very similar to what I was thinking, down to calling it a “wrapped message”. though this has some additional complexity layered in that I hadn’t considered nor wrapped my head around fully
alice would ideally use the same protocol- a one-time key to send the message. now alice isnt the sender.
I don’t think there’s risk of losing the SK, it’s computed with (event.pubkey, privkey). it could be a nip but I think there are ways to implement that wouldn’t strictly require clients in implement it.

