Wrong address

[Silberengel]

Hi, I just noticed that you're using d tags, but those are for things like "first-chapter-book-1" and they don't work as a reference. You'd probably want a tags.

{
  "content": "Rated via Nostr",
  "created_at": 1746630838,
  "id": "d9e2f36649296430b632291fa25b620df8a2f01946e40d81f1635f3f8fa35e11",
  "kind": 34259,
  "pubkey": "fd208ee8c8f283780a9552896e4823cc9dc6bfd442063889577106940fd927c1",
  "sig": "d96647a55d31bb8d259c9087efe54051b08949229bd190bb7819262cd3732920a950194c3b89362a857a7be2168f5fe9d2ab9b703510b54376fa0e2af698f48b",
  "tags": [
    [
      "d",
      "ecda6d37bb6ef23d70c00f0da333ea333911defababca4a30b3f098c6c86ef7e"
    ],
    [
      "m",
      "event"
    ],
    [
      "rating",
      "0.600"
    ]
  ]
}

[Silberengel]

Sorry, made a mess typing on my cell phone.

from NIP-01:

So, you'd probably want to use e tags for nonreplaceable events (who only have nevent addresses) and a tags for addressable events (who have nevent or naddr addresses).

[abh3po]

so it depends, for regular nostr events, it should be the event id, for replaceable events, maybe it should be an a-tag, and we should have a different m-tag value for them.

[Silberengel]

We actually already use m tags extensively, in all event kinds. I have a whole class for them.

https://next-alexandria.gitcitadel.eu/publication?d=nkbip-06

[Silberengel]

There's a NIP defining m tags.
We added the M tags, as our relay can search that index well, to find all calendar events, regardless of kind.

https://github.com/nostr-protocol/nips/blob/master/94.md

[Silberengel]

MIME types are an Internet standard.

https://developer.mozilla.org/en-US/docs/Web/HTTP/Guides/MIME_types/Common_types

[Silberengel]

I think you can leave the m tag off, completely, but I also don't think the M tag is what you're looking for, as it refers to the kind, not the object being rated.

[abh3po]

Actually not a bad idea, was just thinking of cases where clients would need to specifically query for ratings of a particular class.

Also tags are not global, they can be redefined into any event. Except e,d and p tags , but even then they are not used in all events the same way.

I'm okay to change this into a different indexer , if you're using mime types (or see the need for using them) in this event itself

[Silberengel]

I implemented the spec as-is, but whenever I try to fill it out and use it to write an actual rating, I'm completely confused because the tags are all used for completely different purposes than I'm used to and I can't find the spot to enter the information I actually need to later filter and link to the event.

If, for instance, I want to search for events that reference an event, I look for e/E and a/A tags.

It would be clearer to use standard structures in an effective manner and then add an o tag to describe the object ontologically, but it's such a break with the currently-defined ratings events, that I don't know if it could be combined.