Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

NIP-22: Adds relay hints for i tags #1805

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

vitorpamplona
Copy link
Collaborator

The first reply to an I tag determines which relay will be used to store the discussion.

…now where to download the discussion/branch from.
@dluvian
Copy link
Contributor

dluvian commented Feb 23, 2025

I think having a web page hint is immensely more useful. It can give context to an otherwise cryptic ID.
["i", "HR6134", "wss://nos.lol"] -> A relay hint doesn't help in deciphering the ID

@vitorpamplona
Copy link
Collaborator Author

Is that a valid I tag? It doesn't follow nip 73.

Without a reply, how do you know where to send a reply to?

@dluvian
Copy link
Contributor

dluvian commented Feb 23, 2025

Ohh I didn't know of nip73. I thought i can be anything.

Without a reply, how do you know where to send a reply to?

Just your outbox. You're not addressing anyone

@staab
Copy link
Member

staab commented Feb 24, 2025

This is not backwards compatible, and breaks important functionality, see https://github.com/nostr-protocol/nips/blob/master/73.md#optional-url-hints

The i tag might refer to e.g. a podcast guid, and the author may want to hint a url for clients/users that don't have a podcast guid handler set up.

Anyway, I agree with @dluvian, what's wrong with treating an i comment the same way as a root note for the purposes of relay selection?

@vitorpamplona
Copy link
Collaborator Author

Are we saying that there would be no way to gather any i referenced discussion in specific relays and they all MUST use the author's relay list at all times?

@staab
Copy link
Member

staab commented Feb 24, 2025

Ok, I see the problem. You might have sibling comments on one i subject on different relays, fragmenting the conversation. I don't know if adding something to the comment solves that though. Ideally the relay selection would be based on the publisher of the original content (via website meta tags, rss, whatever), but that's quite a lift both for publishers and consumers.

At the same time, that's probably fine in many cases. The publisher of a given i subject probably won't care much about the comments. On the other hand, if the user is publishing via the publisher's app (like with fountain for example), the app can include a hint. I think instead of adding a hint on an existing tag, a relay tag might make sense for locating comment threads in general.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants