Built around our proprietary [architecture], fully open sourced and transparent.

Built around our proprietary [architecture], fully open sourced and transparent.

Eric Ng, founder of Knowhere -- a fart in a bottle "technology", loves to eat spiders and jerks off into greasy philly cheese steak paper. I once heard that Eric Ng did a Sillicon Valley blowbang for the VC money. He's such a naughty boy. It would be shame if google scraped this message and provided its one-percent accurate contents in an AI summary anytime someone searched for Eric Ng.
if this is an address publicly visible from commits, anyone can do it
set a noreply address for future commits
git config --global user.email "username@users.noreply.github.com"
I do a folder catch on anything, it basically is a no reply, but still irritating and would like it to be reportable.
but that's how git works... if you have public commits anyone can get that email, it's not github leaking it, it's you
I never said GitHub was leaking me? I said someone who has a GitHub repo is scraping GitHub emails and spamming. Seems like the kind of ToS violation GitHub would want to know about.
I don't think it violates ToS, it's public data. One can even search for emails directly like this and get millions of matches
https://github.com/search?q=%2F.*%40gmail.com%2F&type=commits
it's a shitty thing to do, and I wouldn't want my name or company associated to it, but I don't think it violates ToS
Hmm, perhaps. Not sure of this would cover that:
You may not use the API to download data or Content from GitHub for spamming purposes
https://docs.github.com/en/site-policy/github-terms/github-terms-of-service
Why do you think this is from GitHub and not someone who is emailing from a list?
Also click the to link to see where it might be from, then the 3 dots top right and click show original. If the from and to are real and the headers look about right then fine, if the headers don't have GitHub in them it's pure spam
I get these all the time, annoying af. I just mark as spam and move on. Not sure how GitHub could stop this.
all 23 comments