Feat: Add relay disclosure endpoint - #73
Open
talvasconcelos wants to merge 2 commits into
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Users events are broadcasted to every configured third-party relay with no way to discover which. Disclosing the list is a transparency/consent best practice.
Adds
GET /nostrclient/api/v1/relays/urls, which returns the list of relays this instance is currently connected to.It's locked behind
require_admin_key, so only someone with an admin key can hit it — no public exposure. It returns just the URLs, nothing else.it reads the live relay list from
relay_manager, not the DB, so it reflects what's actually connected at runtime.