Would it be formed out of something like

`M` OR `o` tag

AND

name (I don't know, "jane eyre" or "ford fiesta")

AND (optional, for specific Nostr-addressable things)

`d` tag

OR

first 20 chars of hexID

Reply to this note

Please Login to reply.

Discussion

Some of this stuff doesn't have an associated event, is the most-difficult thing, so this would need to create a Nostr address for things not on Nostr and for things on Nostr.

They got around it by just dumping all possible addresses to any thing, anywhere into one d tag, but a hash sounds more sane.

Use a pattern to create a hash and then have a d-tag containing the hash. Did I understand correctly?

yeah, something like the hash of the title of the object, and then like _object_name in snek case

i mean, whatever, you got 100 characters so that should be fine if you limit the title text to 36 characters including the underscores

er, no, that doesn't matter, if you use a hash at the beginning that makes it unique already... maybe make the hash out of the name of the object and a timestamp instead of just the name so you don't get collisions there

Ahhh... I get it!!! 😍

So, my event would include, for instance, the `i` tag or `a` tag or whatever tag, that identified what I am rating, and the `d` tag would include a hash referring to that data, so that every time I replaced the rating (by changing the content from "Loved this book!" to "Wow, this book totally sucked." for instance), the relay would look for the same d-tag and switch them out.

And the client would use the other tag to figure out what I am trying to rate. And then I could rate anything for which there could be some sort of appropriate tag.

I think what confused me, and what you and nostr:npub12262qa4uhw7u8gdwlgmntqtv7aye8vdcmvszkqwgs0zchel6mz7s6cgrkj just clarified, is that there are actually two different things needed (a unique d-tag, so that the rating is replaceable), and a way to refer to something (so that the client can figure out what is being rated), and that these two things don't have to be within one tag.

You can use the normal i, a, t, whatever indexes for the second, and use any d-tag structure you want, for the first.