It's completely unenforceable, and there are millions of loopholes like the one you just said that will let them skate around the restrictions both legally and in action.
This seems like an addition because of the "GeekedIn leak"[0] of a bunch of scraped GitHub data from Nov of last year, but I just don't get what it's trying to do. Bad actors are just going to ignore it like normal (or find loopholes) and good actors weren't doing this in the first place.
Personally, I wish they left out the "what you can do with the data" and focused their ToS only on the "how you are allowed to scrape it". Give solid limits on amounts and speeds and other various aspects of the scraping, make them restrictive enough to prevent a service like that from working, then provide a point of contact so that an "archivist" can be allowed to do more on a case-by-case basis.
[0]https://www.troyhunt.com/8-million-github-profiles-were-leak...
I've seen many very cool, creative, and useful tools pop up on top of GitHub and sites like it, and I just fear that changes like this will have the (perhaps unintended) side effect of shutting them down.
Things like CommitPrint [https://commitprint.com/], or Commits.io [https://commits.io/] come to mind.
GitHub has an API. Use of an API is not 'scraping'. The act of scraping involves pulling full HTML pages and parsing out data. Because scraping and API usage are different, there are different ToS for each.
I suggest that useful tools are sticking to the API.
If Alice's archive gets no traffic, and Roger's recruiting firm does 40% of their business using Alice's data, and Alice and Roger get dinner together every week, Alice seems to be doing something wrong.
Even on his own, Roger is still scraping Github. The defense "It wasn't me, it was the Python program that was in the wrong!" is just as ludicrous as trying to hide behind the fact that Alice's archive is scraping the site itself. They're putting limitations on the information, not limitations on how computers are allowed to talk to each other.
Sure, in hindsight, it'll all be obvious..
They're not trying to keep you from scraping, they're trying to keep you from using the data in ways that would be distasteful to their users.
There is, unfortunately, precedent. So GitHub can say, "Only scrape if you do x, y, z."
But... You can't access the TOS without first requesting the data.
Consider it.
You cannot request and view data but in a way acceptable to the TOS.
You cannot view the TOS without first requesting and viewing the data.
Like 4chan has archives of posts, same concept I think.
Joke aside: Working in a library I guess ?
> Researchers may scrape public, non-personal information from GitHub for academic research purposes, only if any publications resulting from that research are open access.
> Archivists may scrape GitHub for public data for archival purposes.
> It is prohibited to scrape GitHub for spamming purposes, including for the purposes of selling GitHub users' personal information, such as to recruiters, headhunters, and job boards.
How about a level of indirection?
Alice the Archivist scrapes GitHub and compiles a compendium of names / emails. She then publishes this information in bulk for anybody who'd like to use. Alice's cousin Roger the Recruiter downloads the archive and does what he does best. Alice isn't selling anything, she's just providing the information bundled up. Roger isn't getting it from GitHub, he's getting it from the public feed (say via Bitorrent or a public data set posted somewhere).