Why doesn't nostr:nprofile1qqs24yz8xftq8kkdf7q5yzf4v7tn2ek78v0zp2y427mj3sa7f34ggjcpzamhxue69uhhv6t5daezumn0wd68yvfwvdhk6tcppemhxue69uhkummn9ekx7mp0qyg8wumn8ghj7mn0wd68ytnddakj703s8dt show a notification when someone follows you?
I presume primal uses their caching service to pick up the follow event and sends the push notification. amethyst doesn't have this afaik s would have to get every contact list update posted to all relays in the background to see the follow.
The greatest trick the devil ever played was convincing the world that fiat money is a public good.
/200px-Feels_good_man.jpg
600bn still in play.
time to spin up another relay...
momentum is gaining. i think some people are understanding the issues more after pavel durov was arrested.
first post has a typo. about right.
nostr:npub1h0uj825jgcr9lzxyp37ehasuenq070707pj63je07n8mkcsg3u0qnsrwx8 looks really good. my npub there is npub1tyss94v5ju56epmp5k8twcwe8t82fqntfckmqxvrjuve8vley5qqudulk0
I'd really like to be able to use my main nsec and import my existing social graph
bloom
too complicated
isn't polished enough
too much Bitcoin content (?)
it's a circle jerk
it isn't really decentralised
I don't think many of them understand public/private key cryptography. also, imo, they're scared of losing the time they've invested on an owned platform.
😆 I have nostr alts that are neither Bitcoin nor nostr. "arts and crafts". be the change you want to see in the world.
I have a business alt. go on once in a while to check the temperature.
i'm torn on encrypting IoT data with the same scheme that NIP4 uses. There are all the metadata issues but the metadata leaks are likely less consequential than with social media clients. however, this doesn't mean it's ok. there are plenty of situations where it could be v. bad.
it's likely that if you're doing iot stuff, you use a different nsec for social media clients, and the devices have semi transient nsecs too.
i've implemented nip04 encryption in the arduino libs. giftwrapping is a good intermediate solution until we have a better NIP. i'll add nip59 support to the lib when i can.
"bitcoiners" hating on nostr on Twitter. 🤦
day 2 up now.
nostr:note1zej03rrughy862dl5dga7uv0vg9u6dlvkptsnl44m4lajwzuw5mqus45wk
pls elaborate. also what's happening with sats link?
One of the biggest technical hurdles for Nostr is finding a way sign events on web apps without browser extensions and without sharing the nsec with the web.
The browser is your enemy...
As soon as there is any meaningful growth in user base, let's say the next adoption cycle "and nsec gone"
Sure, nostr:npub1l2vyh47mk2p0qlsku7hg0vn29faehy9hy34ygaclpn66ukqp3afqutajft created NSECBunker, but there has not been any adoption or alternatives coming up.
I built a hardware signer. however.... the esp32 lacks processing power making it takes a second to sign events which isn't great for UX. this can be improved in how clients feedback to users.
they often do.