You suggested Git based web page hosting would allow for local mirrors of content so they are available regardless of the availability of the original site.
I told you that is already happening in practice, without the overhead of Git.
in your example, i would not agree those two things are the same. Clicking a link that goes to a http:// url and clicking a link that goes to the same file via ftp:// i would say are reasonably similar for the end user.
you're right, i didn't read into #5 enough. so for the purposes of "easier dynamic ip hosting" you're suggesting that browsing to a sha1 hash means it can come from any computer that has a copy of it?
but nobody is going to remember hashes. so you need to use dns or similar, so say "foo.com" has a GIT record, the value of which is an sha1 hash.. but then the client needs to find somewhere to get that from... so presumably you're suggesting some kind of peer to peer system for hosting?
and all of that is somehow better than the existing model, where you simply have a DNS server that has an api to update the IP address of an A record quickly?
You've also skipped over a big issue here.. this whole concept relies on a website being nothing more than static files.
It also effectively removes the ability for the author to have any idea at all about how many people view his site.
Git is reasonably good at what it does. It has some flaws but for versioning text based content, and fostering collaborative working amongst developers/authors, its a reasonably good solution.
As a replacement for HTTP web pages, caching proxies, CDNs, parts of DNS? not so much.