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

Discovery of DVMs and Application Handler relays via NIP-65 #1725

Open
wants to merge 2 commits into
base: master
Choose a base branch
from

Conversation

mikedilger
Copy link
Contributor

@mikedilger mikedilger commented Jan 30, 2025

Simple addition to NIP-65 to allow DVMs and application handlers to be discovered without just probing random popular relays and hoping they published a 31990 there.

@staab
Copy link
Member

staab commented Jan 30, 2025

I agree with using 10002s for relay selections, but shouldn't the k tag go on the NIP 89 handler?

@mikedilger
Copy link
Contributor Author

mikedilger commented Jan 30, 2025

The point here is that I don't know what pubkeys I'm interested in. So I can't search for 10002 by pubkey. All I know is the kind I want handled. And if I have the kind and 10002 gives me the relays, then I can find 31990s that are relevant at those relays. So I need to filter by that kind before I even get to the 31990 events.

@mikedilger
Copy link
Contributor Author

We have this 31989 discovery system where you find things shared by your friends. Maybe that is all we really need, maybe it is even a bad idea to find DVMs as I'm suggesting without any kind of way to know if they are bad actors or not.

@staab
Copy link
Member

staab commented Jan 30, 2025

@mikedilger take a look at this PR: #1728 I think it covers this use case more cleanly (at the cost of some migration of DVM listings)

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.

2 participants