> "disabling port 80 is a great way to handle this"
It's been a disaster for a bunch of people I know.
git is distributed by nature so they all had extra remotes they could use.
github's issues and other project metadata wasn't distributed, since that's github's alone.
So all of the friends of mine who are corporate github users who were using git in a distributed style (a minority of their overall customer base, I would suspect) are more screwed by the web app's absence than they would have been by a repository problem.
I suspect github made the right choice for their customer base overall, but I still find the anecdata interesting.
In fact, all HTTP access redirects to HTTPS for just about everything. And most modern browsers (recent versions of Chrome and Safari) that have accessed a website over HTTPS once happen to _prefer_ HTTPS by default for that site.
It's been a disaster for a bunch of people I know.
git is distributed by nature so they all had extra remotes they could use.
github's issues and other project metadata wasn't distributed, since that's github's alone.
So all of the friends of mine who are corporate github users who were using git in a distributed style (a minority of their overall customer base, I would suspect) are more screwed by the web app's absence than they would have been by a repository problem.
I suspect github made the right choice for their customer base overall, but I still find the anecdata interesting.