Skip to content

NIP05: warn about CORS policies that may inhibit JS apps#4

Merged
fiatjaf merged 1 commit intonostr-protocol:masterfrom
harding:patch-1
May 7, 2022
Merged

NIP05: warn about CORS policies that may inhibit JS apps#4
fiatjaf merged 1 commit intonostr-protocol:masterfrom
harding:patch-1

Conversation

@harding
Copy link
Copy Markdown
Contributor

@harding harding commented May 7, 2022

JS Nostr apps such as Branle may not be able to load nostr.json files due to CORS policies. Update NIP05 to warn about this and provide hints for troubleshooting and fixing the issue.

I think this is the best way to address a confusion I had trying to add my NIP05 identifier to a Branle instance where I kept receiving an error. It also implies that other Nostr apps may be able to load nostr.json files that Branle and other pure-JS apps won't be able to load, which may produce some user confusion.

Note: I'm not a webdev, I might not be describing CORS stuff accurately.

JS Nostr apps such as Branle may not be able to load `nostr.json` files due to CORS policies.  Update NIP05 to warn about this and provide hints for troubleshooting and fixing the issue.
@jb55
Copy link
Copy Markdown
Contributor

jb55 commented May 7, 2022

ACK

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