laantungir/nips
1
0
Fork 0
mirror of https://github.com/nostr-protocol/nips.git synced 2026-07-22 07:48:25 +00:00
Code Issues Packages Projects Releases Wiki Activity

clarify nsite gateway behavior.

Browse Source
This commit is contained in:
fiatjaf
2026-06-21 22:30:35 -03:00
parent 5cdb9cf66a
commit 2834a7f937
1 changed files with 1 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
05.md
View File

@@ -123,6 +123,6 @@ When using NIP-05 to point to events, we introduce a `"events"` field in the `/.
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.
Likewise, an nsite gateway could accept requests at URLs that can be manually typed, like `https://nsite.com/leaderboards@golf.com` (and redirect to the proper subdomain), so the owners of this domain could host nsites without having to actually have a hard association of them with their permanent hosting infrastructure.
This does require `golf.com` to have a dynamic server that can locate the actual event id they want to point to, which is a good thing, since it can enforce the version they want, and they can even have different NIP-05 names pointing to different "versions" of the same thing.