It's not a technical problem, it's a social one.
It's not a technical problem, it's a social one.
I started to write out an example of what it would look like to fix the problem by adding some more layers around the BitTorrent layer, but it got a bit long; sort of turned into a feature spec:
https://gist.github.com/tsutsu/0441fffa6b989121018b5f970d1f4...
It might even allow for benefits like people who post torrents get tipped every time someone upvotes.
It wouldn't stop the domain name wack-a-mole, but it would allow a server hosting the domain to just host static files that pull in data from a distributed ethereum based API.
It would also allow for local applications to operate that work off the same chain so people could still use the service even if the servers powering the HTTP based interfaces are shut down.