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 

 This is internal to the nostr network & not cleaner searchable? 

 1. Is this in any way related to what @brugeman is doing with npub.pro? 
2. Awesome! This is laying the groundwork for Hypernotes (widgets, stories, ...), if I get right. Which is more or less this but with limits on it (no non-Nostr communication, standard pixel sizes, etc...) @Paul 
nostr:naddr1qvzqqqrcvgpzp22rfmsktmgpk2rtan7zwu00zuzax5maq5dnsu5g3xxvqr2u3pd7qyt8wumn8ghj7mnfv4kzumn0wd68yvfwvdhk6tcpz9mhxue69uhkummnw3ezumrpdejz7qqddpuhqetjdehhgefdde5hqyzzlyx 

 I might be very wrong on this. Only just learned what a static site is exactly #noob