We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Feel free to close this if I'm confused.
The NIP-11 spec (https://github.com/nostr-protocol/nips/blob/master/11.md#relay-information-document ) ... says that...
Relays may provide server metadata... This is made available as a JSON document over HTTP, on the same URI as the relay's websocket. )
Operative text here is "on the same URI as the relay's websocket"
So I THINK that means if my relay_url is set to...
relay_url
wss://mydomain.com/v1
Then the Nip-11 data should be accessible like ....
curl -i -H "Accept: application/nostr+json" https://some-domain.com/v1
But so far I am finding this not to be the case with Nostream. The Nip-11 data is instead accessible on the ROOT of the domain
curl -i -H "Accept: application/nostr+json" https://some-domain.com
The text was updated successfully, but these errors were encountered:
cameri
No branches or pull requests
Feel free to close this if I'm confused.
The NIP-11 spec (https://github.com/nostr-protocol/nips/blob/master/11.md#relay-information-document )
... says that...
Operative text here is "on the same URI as the relay's websocket"
So I THINK that means if my
relay_url
is set to...Then the Nip-11 data should be accessible like ....
But so far I am finding this not to be the case with Nostream. The Nip-11 data is instead accessible on the ROOT of the domain
The text was updated successfully, but these errors were encountered: