Nostr Web Client

I participated in the initial beta test of pubky and I had the same thought as nostr:npub180cvv07tjdrrgpa0j7j7tmnyl2yr6yr7l8j4s3evf6u64th6gkwsyjh6w6, that tagging is one of the best things about pubky. Simple, easy, useful, user friendly.

NIP-32 could be one way to implement tags in nostr, but a simpler way would be something similar to NIP-56. Same basic structure as NIP-56, but we rename it from “reports” (which obviously has a negative connotation) to “tags”, and instead of a “report type”, we just have the tag itself, which would typically be a human-readable string (but in theory could be any string, like an event id that points to a “tag” with some sort of structure).

Tags generated via either of the above methods, or any other method for that matter, will be great sources of raw data to be fed into GrapeRank, via the process of “interpretation” which will convert the raw data into a format that is ready to be ingested by the GrapeRank algo.

Dawn 6mo ago 💬 2

That last paragraph is what I was thinking. If the labels exist in many places, then anyone can utilize or present them (or not) however they want... there must be a better way to create them, though. 90% of this conversation is well beyond me, but lacking an efficient way to do it, is the only thing that holds me back from labeling things now.

Reply to this note

Please Login to reply.

Discussion

david 6mo ago

I’d love to see one or more nostr clients implement tags. Probably worth looking at how Pubky does it from a UX perspective.

Dawn 6mo ago

I hate to use Amethyst as an example of everything but there's a 'timestamp it' option in the 3 dot menu on each note. A 'label it' option would fit really nicely below that. The same could apply to any client that offers note menu options beyond like, reply, and zap, such as raw event data & n-prefixed idenifiers (or whatever those are called). It would be tucked away but easily accessible to anyone who want to use it. I don't think it would complicate the UX any more than that stuff already does. Talking a client developer into adding it, I think, would be the hard part.