-
Notifications
You must be signed in to change notification settings - Fork 582
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
Static Websites #1538
base: master
Are you sure you want to change the base?
Static Websites #1538
Conversation
I would just remove the word The rest is good. |
I feel like this is better specified as a BUD since it depends on Blossom and Blossom is not even a NIP. |
nsite.md
Outdated
Host: npub10phxfsms72rhafrklqdyhempujs9h67nye0p67qe424dyvcx0dkqgvap0e.nsite-host.com | ||
``` | ||
|
||
If the requests `Host` does not have a subdomain server MUST lookup any `CNAME` or `TXT` DNS records for the domain and attempt to resolve the pubkey from them |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
how?
I could go either way on this, but I think its closer to nostr since the majority of this NIP is the static file event for mapping path -> hash |
The same can be said about Blossom. And I do feel like Blossom should be published as a NIP somehow. |
How is this done in comparison to the way npub.pro works for hosting nostr sites? |
npub.pro from my understanding is mostly a client-side app. it it has website templates and make relay connections to fetch data This on the other hand is more generic and lets users define a folder structure of files that they want to serve as their "website" |
This nip defines a spec for hosting static websites under a pubkey using kind
34128
events, Blossom servers, and specialized host serversReadable version here
Implementations: