diff options
| author | sgmoore <git-sgmoore@users.noreply.github.com> | 2022-12-16 22:35:56 -0800 |
|---|---|---|
| committer | fiatjaf <fiatjaf@gmail.com> | 2022-12-17 22:31:19 -0300 |
| commit | 4f67f5c9990c4cd6594d453a5404af9cd1fd5951 (patch) | |
| tree | 0e091ed68fddf534d67b01bb725cca5d3a9bfa6c /05.md | |
| parent | 8918dc06eedfd1584c778746ceeff337ae7df84d (diff) | |
Minor grammar and spelling fixes
Minor grammar fix at line 48. Minor spelling fix at line 56.
Diffstat (limited to '05.md')
| -rw-r--r-- | 05.md | 4 |
1 files changed, 2 insertions, 2 deletions
| @@ -45,7 +45,7 @@ A client can also use this to allow users to search other profiles. If a client | |||
| 45 | 45 | ||
| 46 | ### Showing just the domain as an identifier | 46 | ### Showing just the domain as an identifier |
| 47 | 47 | ||
| 48 | Clients may treat the identifier `_@domain` as the "root" identifier, and choose to display it as just the `<domain>`. For example, if Bob owns `bob.com`, he may not want an identifier like `bob@bob.com` as that is redundant. Instead Bob can use the identifier `_@bob.com` and expect Nostr clients to show and treat that as just `bob.com` for all purposes. | 48 | Clients may treat the identifier `_@domain` as the "root" identifier, and choose to display it as just the `<domain>`. For example, if Bob owns `bob.com`, he may not want an identifier like `bob@bob.com` as that is redundant. Instead, Bob can use the identifier `_@bob.com` and expect Nostr clients to show and treat that as just `bob.com` for all purposes. |
| 49 | 49 | ||
| 50 | ### Reasoning for the `/.well-known/nostr.json?name=<local-part>` format | 50 | ### Reasoning for the `/.well-known/nostr.json?name=<local-part>` format |
| 51 | 51 | ||
| @@ -53,7 +53,7 @@ By adding the `<local-part>` as a query string instead of as part of the path th | |||
| 53 | 53 | ||
| 54 | ### Allowing access from JavaScript apps | 54 | ### Allowing access from JavaScript apps |
| 55 | 55 | ||
| 56 | JavaScript Nostr apps may be restricted by browser [CORS][] policies that prevent them from accesing `/.well-known/nostr.json` on the user's domain. When CORS prevents JS from loading a resource, the JS program sees it as a network failure identical to the resource not existing, so it is not possible for a pure-JS app to tell the user for certain that the failure was caused by a CORS issue. JS Nostr apps that see network failures requesting `/.well-known/nostr.json` files may want to recommend to users that they check the CORS policy of their servers, e.g.: | 56 | JavaScript Nostr apps may be restricted by browser [CORS][] policies that prevent them from accessing `/.well-known/nostr.json` on the user's domain. When CORS prevents JS from loading a resource, the JS program sees it as a network failure identical to the resource not existing, so it is not possible for a pure-JS app to tell the user for certain that the failure was caused by a CORS issue. JS Nostr apps that see network failures requesting `/.well-known/nostr.json` files may want to recommend to users that they check the CORS policy of their servers, e.g.: |
| 57 | 57 | ||
| 58 | ```bash | 58 | ```bash |
| 59 | $ curl -sI https://example.com/.well-known/nostr.json?name=bob | grep ^Access-Control | 59 | $ curl -sI https://example.com/.well-known/nostr.json?name=bob | grep ^Access-Control |