nostr-protocol / nips

Nostr Implementation Possibilities
2.39k stars 582 forks source link

Static Websites #1538

Open hzrd149 opened 1 month ago

hzrd149 commented 1 month ago

This nip defines a spec for hosting static websites under a pubkey using kind 34128 events, Blossom servers, and specialized host servers

Readable version here

Implementations:

vitorpamplona commented 1 month ago

I would just remove the word nsite from the title because it feels like you are defining a new NIP-19 bech address.

The rest is good.

fiatjaf commented 1 month ago

I feel like this is better specified as a BUD since it depends on Blossom and Blossom is not even a NIP.

hzrd149 commented 3 weeks ago

I feel like this is better specified as a BUD since it depends on Blossom and Blossom is not even a NIP.

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

fiatjaf commented 3 weeks ago

The same can be said about Blossom.

And I do feel like Blossom should be published as a NIP somehow.

rabble commented 2 days ago

How is this done in comparison to the way npub.pro works for hosting nostr sites?

hzrd149 commented 1 day ago

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"