hopefully a new NIP. but its static web sites stored on blossom servers and nostr. then serve ( and cached ) from a central server
nostr:npub1elta7cneng3w8p9y4dw633qzdjr4kyvaparuyuttyrx6e8xp7xnq32cume built an MPV of it in SEC-02 https://github.com/lez/nsite
Oooooh 👀👀👀👀
I have a use case for this 👌
Really enjoy the concept that each npub can have its own website no matter the domain name.
This also means going beyond just sha256 and now refer to filenames under a tree structure on that npub (virtual) folder. So we'd look up the most recent sha256 on that path with the same name.
There is the problem of the server side tampering the output, so I guess there would be note from the npub working like a recipe and detail all sha256 that belong to the most current snapshot so we can verify.
If clients or users want to verify that the file has not been tampered with then they could easily fetch the events themselves and check that the hash matches what was sent from the server
