Agree mostly, but I do take issue with the idea that "an active GitHub account should be enough for most programming jobs." Recruiter or otherwise, that kind of assumption is a good way to miss out on talent.

At my current job I have a very active github account - but about 95% of that activity is in private repos.

I am just now starting to work more on contributing to github hosted OSS Projects but -- when I even had time previously -- those projects were often not hosted on github.

For my personal projects, I use my own git repos over ssh. I probably will decide to put them on github when and if I am ready to share them -- but that's not a given.

In my previous job, we didn't use github. Everything was closed source and internal.

Just because one service is the current fad (and don't get me wrong, I generally think github kicks ass) doesn't mean it's valid to assume that your next candidate is using it.