Michael Dilger

Reading it again now after a long time I think it is too long. I should take out the opinionated advice and some of the excessive reasoning.

> I've implemented this at https://github.com/nbd-wtf/go-nostr/blob/39f541fc034bdf29e45d66751e8c9ae49d7ed3b4/nip49/nip49.go That's awesome. And the code is actually quite short, the heavy lifting being done in the libs.

@melvincarvalho I recently dug through all the PRs to extract all the kinds that might be in use and came up with this list, above and beyond what has been...

> 10002 Yeah this NIP was started ages ago. Most of the comments before Jan 17, 2023 probably won't apply. Better to just look at the text.

I'm about to push a change to the title. Then I'm in favor of merging. We can add more test data vectors, but it does have one.

Every nostr event is digitally signed and can be thought of as a claim: the pubkey claims the contents. But such claims in English are not meant for machine use....

I agree with @staab here that the p tags in kind-3 events don't supply enough information about which relays the person you are following posts to. I'm writing code for...

Ok @eskema maybe you are right, but if so you'll be able to solve my problem for me without such tags. Here is my problem: 1. Existing nostr user decides...

> the client needs to be able to function with the sparse data that it has.. it needs to be able to display any empty profile because users are not...

> What are we trying to achieve with this NIP and does anyone involved in nostr protocol development care about privacy? I would like to reply to this but I...