Nostr Web Client

I thought this was an elegant solution, but it's sort of just stalled.

https://github.com/nostr-protocol/nips/pull/1076#issuecomment-1987002929

I think this is cleaner than NIP-22

after reading though NIP-22 again im not really a fan of the meta-tags that it has in the "o" and "r" tags for a few reasons

- The first index of the "o" or "r" tag uses a ":" to separate the values then the following indexes use spaces?

- The "o" and "r" tags have no way of indexing pubkeys. so we wouldn't be able to pull all comments that reply to a pubkey

- Why do we need to reply to URLs, topics or geohashes? cant we just reply to events that represent those things?

IMHO a generic comment kind:1111 + NIP-10 + a "k" tag would be the most elegant solution

Reply to this note

Please Login to reply.

Discussion

hzrd149 1y ago

https://github.com/nostr-protocol/nips/pull/1233#issuecomment-2117476836

Laeserin 1y ago

They've lost me, in the technicalities, I'm afraid. This is a discussion more for nostr:npub1wqfzz2p880wq0tumuae9lfwyhs8uz35xd0kr34zrvrwyh3kvrzuskcqsyn I think.

I just like the idea of not using Kind 01, but also not losing the "general comment" flow or recreating the same type of event with 29170 different event kinds.

james r 1y ago

who is going to create the events that represent those things?

hzrd149 1y ago

commenting on highlight events are similar to replying to URLs

kind 1 with "g" geohash tags or another similar location event would work for commenting on locations

I'm not sure about topics though since that sounds kind of vague

james r 1y ago

what I am saying is that there could be multiple events representing a URL

MichaelJ 1y ago

I think the point is that there is actually no need for an event to represent a URL, since the kind 1111 events can point to entities that are not Nostr events.

It makes a lot of sense to me, all it needs is a good client to wrangle those into a worthwhile user experience.

MichaelJ 1y ago

The tagging suggestions in the NIP-22 proposal are a bit of a mess. I, for one, am not a fan of the significant uppercase 'K' tag. There's a lot riding on a minor distinction, there.

When you need a table to explain all the different tag value combinations, the tagging system is too complex.

Laeserin 1y ago

Yeah, I was like, TL;DR.