Would there be any objection by the Clams devs/stakeholders to me trying to do this?
Considerate of you to ask. In the absence of either sanctions or penalties, objectors are impotent.
You're not the only one seeking independence from corporate overreach, others see the same need:
https://github.com/elendirx/web2web/How It Works
This repo contains two HTML files:
index.html is responsible for loading the webpage from torrent,
webpage.html is the actual webpage.
When you open index.html in the browser (live demo), here's what happens:
Bitcoin address 1DhDyqB4xgDWjZzfbYGeutqdqBhSF7tGt4 is searched for the latest outgoing transaction containing OP_RETURN script. Inside the script there is a torrent infohash of webpage.html.
webpage.html is downloaded from torrent via webtorrent and displayed.
How Is It Updated
To perform serverless updates, torrent of the updated webpage.html is created and its infohash is inserted into new bitcoin transaction sent from 1DhDyqB4xgDWjZzfbYGeutqdqBhSF7tGt4 address.
How Is It Domainless
Save the index.html to your PC and open it from localhost. It will still work and receive updates.
In the example, the tx data containing the torrenthash is retrieved from a Bitcoin API service. All that would be required to make this work with CLAMs is a server to provide the same API for the CLAMs blockchain (assuming dooglus isn't already providing it).
Publishing by torrent is something of an interim measure. Less, ah, informal solutions are being developed: SOLID, IPFS amongst others.
Cheers
Graham