1. GitHub‑scraped email spam is rampant
Many users report receiving unsolicited marketing, job offers, or phishing emails that clearly come from companies that have harvested their public GitHub email addresses.
“I’ve received the exact same email from that guy asking me to make open source PRs …” – foldr
“I got a spam email from a Github scraper while reading this thread” – elwebmaster
2. Legal and ethical questions are at the core
The discussion repeatedly turns to GDPR, CAN‑SPAM, and Y Combinator’s own ethics charter, with users asking whether these spammers are violating law or YC policy.
“I was also spammed … I wonder if what they're doing is actually illegal.” – pscanf
“Doesn't YC have some code of conduct or legal/ethical guidelines?” – WhatsName
3. GitHub’s policies and technical work‑arounds
Participants debate how GitHub’s “no‑reply” email feature, commit‑email privacy, and TOS enforcement can mitigate the problem, and whether GitHub should do more.
“GitHub can block pushes with any email other than the noreply one” – arcfour
“GitHub’s TOS explicitly forbids transmitting scraped data for spamming” – MartinWoodward
4. YC’s reputation and startup culture are under scrutiny
The thread is also a critique of YC‑funded companies’ marketing tactics, the “growth‑hacking” ethos, and the broader startup ecosystem’s willingness to blur ethical lines.
“YC is basically advising their startups to engage in shitty business practices” – callamdelaney
“The YC brand has been associated with hacking‑around and gaining advantage via rule breaking” – ryandrake
These four themes—spam prevalence, legal/ethical debate, GitHub policy/solutions, and YC culture criticism—capture the main concerns voiced in the discussion.