The issue is that BitTorrent as a protocol converts hashes into files, but it's got no mechanism to associate a hash with some other identity. That means you do

The issue is that BitTorrent as a protocol converts hashes into files, but it's got no mechanism to associate a hash with some other identity. That means you don't need trust to operate it, but conversely there's no way make changes to a torrent after it's been seeded. A system like Bitcoin+BitTorrent could do what you're describing, with Bitcoin filling in the missing distributed hash identification function. I don't really follow the distributed web scene, but I'm sure that's an area of active research.