Nostr Web Client

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

james r 1y ago 💬 1

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

Reply to this note

Please Login to reply.

Discussion

hzrd149 1y ago 💬 1

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 💬 1

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.