You were complaining that Nostr didn't use a DID? Now it does!

You were complaining that Nostr didn't use a DID? Now it does!

I also talk in circles until she leaves the room, you ?

#bitcoin

It's not just nostr that has jumpy feed issues

If anyone is interested in Nostr Proof of Work, I have a draft NIP and functional implementation of a POW service provider that can remotely generate POW for your events before signing and publishing.

The general feedback and support was on Nostr, and the Github issue responses were more concerned based.

I built this entirely in anticipation for mass Nostr spam protection - in case we needed it urgently. We seem to be doing ok with spam now, however it’s possible we may need to revisit minimum POW for events when publishing - as a relay opt-in.

And just to clarify, I don’t like burnt CPU cycles either. Paying sats directly to a relay works well - however unless you pay for 10+ relays.. your events are not decentralised (as most relays move toward becoming paid to publish). POW helps address the issue of low value spam and flooding - it doesn’t solve everything.

#[0]​ opening this separately from the other discussion as this is quite unrelated, but would be a cool idea and I’m kinda doing something like this already but not as cool:

A cooler but way more out-there idea, if nostr could act like a DNS SRV-type record for service-handler discoverability, nostr clients could query my follow list for a recommended list of services that are compatible with a certain kind

1111 = made-up “kind-handler” kind

"kind": 1111,

"content": "zapstr music player",

"tags": [

[ "k": 31337 ],

We don't recommend Coinbase because they've clearly lost their way. Not only do they sell and promote scams, they are not good data stewards of your information. More evidence is below.