211–220 of 278 posts
General advice would be to mark the email as spam or junk and hopefully their email platform penalizes them, but this has been working less and less. Email has truly become pay to play now.
I find it interesting that a substantial number of people seem to think it's wrong or unethical to cold-email someone about a potential recruitment or business opportunity if they post their email in a public place, such as commits in a public Github repo. I feel like if you don't want companies to cold-email you, you shouldn't make your email public. Github provides noreply email addresses for this purpose.
Scraping emails is also against the GitHub terms of service.
If you don't know what jurisdiction the owner of the email address resides in, it may also be illegal.
So whether it is scraping emails off a website or finding yourself on a private island with beautiful people "made available" to you, "consent" requires more than just having access.
Earlier quoted context omitted.
How would you know whether the account that did the scraping was banned?
By visiting the account and noticing that it still has activity long after the report.
Or do you mean going after the accounts of companies that make use of a likely scraped email address? That's not a bad idea either, but it has risks and isn't the same thing.
And them claiming "they didn't know" can be dismissed given that many dev on GH have location information set.
It also in general doesn't change anything. the law doesn't care if you know or didn't.
Startups starting out their journey by committing crime is always a grate sign for their trustability.
Just got a SPAM email from a Github scraper while reading this thread: From: james@techglobal.website Quick note – your GitHub profile Hi X, I came across your profile on GitHub. Given you're based in the US, I thought it might be relevant to reach out. Profile: I run a technical team (full-stack, cloud, DevOps) that delivers for clients. We're looking to work with an engineer based in the US on client-facing coordin…
I'm curious, what leads you to North Korean from that email? Is it that there's an anonymous team, which has a US "front"?
Earlier quoted context omitted.
They already do[0] 62114487+david-allison@users.noreply.github.com this includes a unique ID which survives account renames, and the name of the GitHub account at the time. [0] https://docs.github.com/en/account-and-profile/reference/ema...
How does the spammer get through this then?
Martin from GitHub here. This type of behaviour is explicitly against the GitHub terms of service, when we catch the accounts doing this we can (and do) take action against those accounts including banning the accounts. It's a game of whack-a-mole for sure, and it's not just start-ups that take part in this sketchy behaviour to be honest. I've been plenty of examples in my time across the board. The fundamental natur…
I don't have any specific suggestions, but I do want to give thanks for implementing functionality to block pushes if the email field is *not* using an anonymized mail address. It's one thing to offer anonymous e-mail addresses, but it's also awesome that GitHub can help prevent mistakes that would otherwise leak a user's e-mail address. I am not sure how many people try to be privacy conscious on GitHub, but I assum…
And not all devs want or need anonymity on github.
In general just because information is publicly accessible in some form doesn't make it okay or legal to abuse it (accessible doesn't mean any form of usage rights are transferred to you weather it's in context of GDPR or in context of copy right).
Earlier quoted context omitted.
By visiting the account and noticing that it still has activity long after the report.
I'm confused. How do you know what account scraped your email address from github in order to send you an email? Or do you mean going after the accounts of companies that make use of a likely scraped email address? That's not a bad idea either, but it has risks and isn't the same thing.
> I came across your profile on GitHub. Given you're based in the US, I thought it might be relevant to reach out. > > Profile: https://github.com/tedivm
They aren't doing anything to hide it.
I wish github could ammend the email of my commits to the private noreply address during push so they _never_ have any other email associated to them. May not be feasible due to the commit changing, confusing local branch and such? They have this other thing where they reject pushes for the 'known' emails you've told them you have, but kinda seems there should be a setting to do that for any email that is not your no…
They literally have a setting to block pushes with any email other than the noreply one, lol.
They only do that if you set up that specific email on your account. Not if its 'any email other than the noreply one'.
> When you push to GitHub, we’ll check the most recent commit. If the author email on that commit is a private email on your GitHub account, we will block the push and warn you about exposing your private email.
Perhaps my usecase is niche, but I sometimes work with other git servers from the same machine with different emails and I don't want to set up all those on GH. Global settings don't help here, per-repo settings help but this doesn't come along when you clone a new one.