A recruiter used the GitHub API to pull my email address out of Git commits
21–30 of 62 posts
Re: A recruiter used the GitHub API to pull my email address out of Git commits
#22https://github.blog/2017-04-11-private-emails-now-more-priva...
Re: A recruiter used the GitHub API to pull my email address out of Git commits
#23One of the things I hate about Git is that it requires an email address. It doesn't let you just leave a blank value, it needs something that resembles an email address. I get that email is how the kernel-devs do it. But IMO it's inappropriate for the version-control software to link a particular communication mechanism. Sure you can use a fake email address, and many of us do. Finally github has a feature to use the…
git config --global user.email no@email.invalid
And git happily accepts the value, yet the result is not useful to anyone (https://en.wikipedia.org/wiki/.invalid).Or, just edit your .gitconfig by hand after adding an email and change the value there to whatever you want.
Re: A recruiter used the GitHub API to pull my email address out of Git commits
#24Why is this a big deal? Of course recruiters search public information. Learn to live with it. If your outrage threshold is this low then you’re going to spent all your life in a state of outrage. It’s nit even interesting let alone important. Information in github, far from being surrounded by an invisible force field of integrity protection, is actually prime hunting territory for recruiters and any recruiter who d…
Re: A recruiter used the GitHub API to pull my email address out of Git commits
#25Emails in git commit logs are not a secret, which I wish more people understood and acknowledged. In general I don't think that expecting your email address to be private is reasonable. If you collaborate with others online, they should be able to get in touch. Stuff like this is an unfortunate consequence, but a manageable problem imo.
Email addresses in general are not supposed to be a secret. They’re supposed to be for people to send you electronic mail. Remember when there used to be books that contained everyone’s phone number? If you’re a high profile person or are particularly guarding of your personal communication, I think it’s your responsibility to maintain separate public and private email addresses. You should only be making commits to…
Re: A recruiter used the GitHub API to pull my email address out of Git commits
#26Re: A recruiter used the GitHub API to pull my email address out of Git commits
#27Re: A recruiter used the GitHub API to pull my email address out of Git commits
#28Why is this a big deal? Of course recruiters search public information. Learn to live with it. If your outrage threshold is this low then you’re going to spent all your life in a state of outrage. It’s nit even interesting let alone important. Information in github, far from being surrounded by an invisible force field of integrity protection, is actually prime hunting territory for recruiters and any recruiter who d…
Re: A recruiter used the GitHub API to pull my email address out of Git commits
#29Why is this a big deal? Of course recruiters search public information. Learn to live with it. If your outrage threshold is this low then you’re going to spent all your life in a state of outrage. It’s nit even interesting let alone important. Information in github, far from being surrounded by an invisible force field of integrity protection, is actually prime hunting territory for recruiters and any recruiter who d…
It seems to me that most good developers would ignore such spam—I get so much of this noise that I pay it no attention whatsoever.
If this is the best recruiters can do, then they can apparently provide no real value to the process.
Re: A recruiter used the GitHub API to pull my email address out of Git commits
#30I thought Mr Bernhardt was technical enough to know that pushing commits onto a public web server made those commits and their metadata public information. I get that you don't care for spam, but they used information you published.