-
Notifications
You must be signed in to change notification settings - Fork 3
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
Empty nostr.json #20
Comments
Follow-up ... I'm seeing a I've re-installed the extension and nuked the DB, but no change. |
It's kind of counterintuitive, but
The relay field is 'recommended', see the specs: https://github.com/nostr-protocol/nips/blob/master/05.md
Yeah, that was a stumper for me too. The Don't give up, give it another try; it took me some time, but now it works for me! |
Ah, I didn't know it was dynamically generated. However, it should return a non-empty file when is is generated, right? Clients don't provide query parameters afiak. Even using the filter doesn't work for me. |
Clients should provide query parameters, as per the specs: https://github.com/nostr-protocol/nips/blob/master/05.md#reasoning-for-the-well-knownnostrjsonnamelocal-part-format It took a while, but now it works for me: https://lnbits.noszter.hu/nostrnip5/api/v1/domain/JTai6rMtFMhjjSfYt7duaC/nostr.json?name=zoltan Can you check your |
Have setup a domain and a user, but have an empty nostr.json.
It was also unclear what the relay field did. Shouldn't NIP-05 be totally independent of relay?
Running 0.2.9 ext and 0.12.11 lnbits.
The text was updated successfully, but these errors were encountered: