Non-Authoritative tags

[ondra-novak]

I think it would be a good idea to define a set of tags that are not part of the original event, but may contain useful informations that might be useful to the client, but were not in the original event and thus are not signed.

For example: if a relay is doing some caching, it could pass information to the client about where to find additional content that is more quickly available than using the main connection.

These tags are added to the event in a response to REQ command.

Example:

{
   "id":"...",
  "pubkey":"..."
   "content":"...."
   "kind": ...,
   "tags": [ ...],
   "sig": "...",
   "na_tags": [
        ["r":"wss://abc.xyz"],
        ["url":"https://cdn.abc.xyz/path/file"],
   ]
}

• na_tags - non authoritative tags.
• r - use relay - suggests to client to use this relay to download more informations about the topic
• url - download (for example file/image/video) from this url
• ....

[AsaiToshiya]

Is this the same as PR #605?

[ondra-novak]

Might be

I have another solution that I think is better than putting this information in the event. I just realized this now when I tried to implement it on my relay.

All events are received by the client via the EVENT response. This answer has 2 arguments. "Subscription id" and "event". It would be possible to send this metadata rather as the 3rd parameter of this response

[ondra-novak]

["EVENT","subscription",<event>,<metadata>]

[fiatjaf]

Since it isn't signed you don't need to use the cumbersome tags format, you can just append keys to the event object or do as @AsaiToshiya's link.

[ondra-novak]

As I wrote above, I realized that it is not a good idea to interfere with the event itself. In my relay, I have the event picked up directly from the database and forwarded to the response, and interfering with it would mean a more complicated implementation. It would be better to send this information "by a side path"