Nostr Web Client

That's the idea, but there's not requirement for publishing a definition. 1985 was simple enough that it could be inferred from the event. Reverse-domain notation isn't required either (and probably isn't a good idea). The basic idea is that anything identifiable by a string can be labeled. The namespace is just to avoid label collisions, and was probably overdoing it

david 2mo ago

Suppose I want to start a list of businesses that accept BTC in my hometown. How would I do that using NIP-32?

With the Decentralized Lists NIP, step 1 would be a kind 9998 event as the list header, which would include the name of the list and an optional description. Step 2 would be that anyone could contribute businesses to the list using a single kind 9999 event per business. Then step 3 would be that I use personalized trust metrics to keep spam off the list.

Reply to this note

Please Login to reply.

Discussion

hodlbod 2mo ago

Just create a 1985 with L="businesses.list" or whatever namespace you want to define (via nip, reverse domain name, intuition, whatever), then l="My list name". The trade off is that no one owns the list name, because it's tautological (the identity is the name). Metadata could be collaboratively added using some other tag though. Step 3 would be the same.

david 2mo ago

So my options are:

1. Buy a domain and set up a namespace

2. Make a NIP

3. Intuition

Suppose I’m not a nostr dev and there’s no way I’m going to do 1 or 2 because they sound like a lot of work. So that leaves intuition. Is my first step a kind 1985 note? Can I skip the L tag since I’m not providing a formal specification for the namespace?

hodlbod 2mo ago

You can omit the L if you want. If you want to see an example, see tge collections feature in coracle, which works this way (but doesn't pull other peoples' labels)