Static websites 🤝 nostr procotol = match made in heaven. No "backend" needed. You'll be able to decentralize your website. IMO, nothing on nostr is more exciting than this.
Login to reply
Replies (12)
@josh received a nutzap of 21esats from @Paulo Sacramento with note: "🔥"
Agreed. The idea of no stack websites displacing full stack websites is fun to consider
@josh received a nutzap of 21esats from @royster⚡️ with note: "satoshi's regards"
Would the front end simply filter for your own posts?
How would you handle static pages that need to be updated occasionally?
Also, what about things like forms where you want to privately accept user submissions?
Really curious how this all would work.
Everything is fun until you stumble upon CORS issues 😅
Not with the nostr portion. CORS doesn’t apply to web sockets. Other areas like images and assets, it’s complicated.
Yeah I did't specify why. We had to add a CORS proxy server to Jumble to show URL previews.
This already exists and its pretty simple :)
And there are a few tools here fro deploying them 
NostrHub
NostrHub | Discover and Publish NIPs
Explore official NIPs and publish your own custom NIPs on NostrHub.
GitHub
Static Websites by hzrd149 · Pull Request #1538 · nostr-protocol/nips
This nip defines a spec for hosting static websites using site manifest events
Root site: Use kind 15128 and is a replaceable event per pubkey and...
GitHub
GitHub - nostrver-se/awesome-nsite: A collection of tools and apps built using the nsite spec which extends the Blossom spec
A collection of tools and apps built using the nsite spec which extends the Blossom spec - nostrver-se/awesome-nsite
Can you explain this to me like I'm 5?
Cool, will check it out. Thanks!