Very good point, though you're missing a layer of indirection in your thinking. I should have made my point more explicit! Usually you would subscribe to a cry

Very good point, though you're missing a layer of indirection in your thinking. I should have made my point more explicit! Usually you would subscribe to a cryptographic pointer (the publisher's public key) whose value is stored in a DHT. Then the pointer can be updated to point to new revisions of the content/website. IPNS is a famous implementation of that for the IPFS protocol. So as a client you can seed a specific revision of the content, or all of them, or just seed the latest version.