Nostr Web Client

Nice, I see, but a question, the format you have for making lists where you define headers in one tag and pins in others can be a bit complicated to handle and parametrize for different clients, why not something like nip51 sets up for categorized bookmarks? ["Key", "value"], and keep adding values if necessary, ["Key", "value1", "value2", "value3" ] Do you think this could be more manageable for the other nostr clients?

Sep 2y ago

because each item of a list should have been defined in a separate tag item. for example in NIP-51 for creating a 'Categorized People' list, we are using ['p', ''], ['p', ''] not ['p', '', ''], in other words, lists in nostr events defined as vertical tags not horizontal ones.

btw, there are soooooo many different approaches, and a lot of them just work!

Reply to this note

Please Login to reply.

Discussion

Gzuuus 2y ago

I see, even though for example in nip39 ( https://nips.be/39 ) each parameter is defined horizontally

```

{

"id": ,

"pubkey": ,

...

"tags": [

["i", "github:semisol", "9721ce4ee4fceb91c9711ca2a6c9a5ab"],

["i", "twitter:semisol_public", "1619358434134196225"],

["i", "mastodon:bitcoinhackers.org/@semisol", "109775066355589974"]

["i", "telegram:1087295469", "nostrdirectory/770"]

]

}

```

I will be studying which format to follow, to see which is more compatible with most of the protocol.