It's crazy how fast these tariffs have taken place.

"I don't know enough about that to speak on it"

@jb55 what is your throttling policy for your relays again? I'm almost finished making a game built on nostr, but I'm unsure at what frequency of posting from my game npub is going to be rejected.

I realize now why polyester is terrible. I didn't think it mattered that I was wearing it, how much harm could that do? It's more about the microplastics it leaves behind. Those blankets made of polyester? Leaving trace amounts of plastic everywhere. Especially bringing a baby into this world that wants to put everything in their mouth. Not in my household.

This is a good take View quoted note →

It's getting incredibly easy to get started with nostr and a nostr wallet (takes about 5 minutes). @calle ty as always

Will someone zap this note 16 sats? Promise to double it trust me bro.

Google Chrome continues to push getting rid of ad blockers. Updated Chrome yesterday and it, again, disabled uBlockOrigin. They're stopping short of banning the extension because people would seek alternatives. I'm already there. What's your guys' preferred alternative browser?

@PABLOF7z mentioned that no one had bridged a lightning address to their nostr wallet, so I built it out. Here's a demo of it working and verifying it with Olas. Now you can receive lightning payments to your LUD16 address and ecash sent directly to your nostr wallet. A wallet that travels with you all over nostr. None of this would be possible without @calle, Pablo, and everybody else working tirelessly on nostr and cashu. Thank you guys. This is still in early beta, so PLEASE be careful. View quoted note →

Instead of mentioning Cashu - ecash is custodial every post, I think people will still get the idea if you mention it every other post.

Discouraging View quoted note →

Realizing how useful NIP-60/61 are @calle @PABLOF7z. Wanting to use LUD06/16 with this, thoughts?

Never seen this chart before. Block subsidy reward in USD.

@fiatjaf @Vitor Pamplona NIP-17 obviously doesn't work with whitelisted relays because you have to create a random pubkey to send the message. Could you instead, at some point (maybe when you first follow someone as it's a public event anyways), send a single encrypted message to the recipient intended for the transfer of a symmetric key? That way you could: 1. Encrypt a message using the symmetric key 2. Send it to the relay the pubkey is whitelisted on 3. The recipient's client, probably only checking for that event kind and narrowed to pubkeys they follow) would then attempt to decrypt it using the symmetric keys it's holding 4. The recipient's client would then store the message appropriately