Given that having an email address attached to commits is a fairly standard component of git, is there a way to prevent this?
Short of using burner/fake email addresses of course
Short of using burner/fake email addresses of course
8601934+judge2020@users.noreply.github.com
You can’t receive email at this address, so, hopefully, anyone that needs to contact you can find your real email elsewhere.
Thanks for the heads up.
Of course, the problems with this strategy are that the manual work scales poorly, there are two or more points of failure, and the best outcome is only marginally positive, doing nothing to deter future abuse.
This is the problem with virtually all spam remedies so far. If the penalty is that their success rate merely goes down, well it's already dismal, what's another few percent even matter? The economics are massively in their favor.
Until they start getting kicked off platforms for a certain number of spam complaints, the way creators get kicked off platforms for a certain number of DMCA strikes (which can be bogus, that's a problem I'd not like to copy), there's nothing incentivizing them to really, really hesitate and check with legal before pulling the trigger on an email.
Spammers should live in fear. Until we make that happen, nothing will change.
This is even far from a solution. The spam I get is always from a newsletter or "startup" I had never heard of before. This leads me to believe MyMachineLearningNewsletterForum will just rebrand under a new name if they were ever given some death penalty from the Internet (putting aside how infeasible that is).