diff --git a/05.md b/05.md index ccaadbb4..0727fee3 100644 --- a/05.md +++ b/05.md @@ -106,17 +106,21 @@ Fetchers MUST ignore any HTTP redirects given by the `/.well-known/nostr.json` e The world is messy, and some people like DNS as a pointer to things, so we can also use these DNS-based internet identifiers to point to events such as [NIP-29 groups](29.md) or [NIP-5A nsites](5A.md), among other use cases. -When using NIP-05 to point to events, we introduce a `"events"` field in the `/.well-known/nostr.json` object, for example: +When using NIP-05 to point to events, we introduce a `"events"` field in the `/.well-known/nostr.json` object, for example, this could be the `nostr.json` output for a website `golf.com`: ```json { "events": { - "golf-appreciators": "", - "homepage": "" + "general": "", + "leaderboards": "" }, "relays": { - "": ["wss://groups.relay.com"], + "": ["wss://groups.relay.com"], "": ["wss://somerelay.com", "wss://someotherrelay.com"] } } ``` + +Then the NIP-29 group about golf that is currently controlled by the people from `golf.com` can be referred to (outside of Nostr, in share-links or in UI display labels) by an id like `general@golf.com` instead of `u349gsifgq3`. + +Likewise, an nsite gateway could accept requests at URLs that can be manually typed, like `https://nsite.com/leaderboards@golf.com`, so the owners of this domain could host nsites without having to actually have a hard association of them with their permanent hosting infrastructure.