4 ms·
The problem is spammers harvesting emails. Git* makes harvesting emails ridiculously easy. Therefore some solutions are needed (e.g. using Github-assigned email
by Ansil849 5y ago
The problem is spammers harvesting emails. Git* makes harvesting emails ridiculously easy. Therefore some solutions are needed (e.g. using Github-assigned email address aliases instead of user-supplied email addresses).
- fuzzy2 5y agoGit hosting services cannot change the address on the actual commits, so trying to hide it on the web frontend is pretty pointless. You could always just clone the repo to get the addresses. It will always be up to the user to set it up in a way they want. Well I guess GitHub could refuse non-GitHub e-mail addresses when pushing, but let's seriously not go there.
- MatthiasPortzel 5y ago> GitHub could refuse non-GitHub e-mail addresses when pushing This already exists as an option. GitHub does as much as they can to protect e-mail privacy without making it impossible to use an email.
- lmz 5y agoThe emails are part of the commit hash. https://blog.thoughtram.io/git/2014/11/18/the-anatomy-of-a-git-commit.html https://blog.thoughtram.io/git/2014/11/18/the-anatomy-of-a-g... - good luck comparing them when the emails have been rewritten.