Update 9: I updated the original article with dates and @natfriedman responses. https://t.co/f5mXUEScEn
— Hamed Saeedi (@Hamed) July 28, 2019
"Persons in and residents of these jurisdictions are prohibited from using IP proxies, VPNs, or other methods to disguise their location when accessing GitHub services " https://t.co/2e3ufMHroH
— Jay Graber (@arcalinea) July 27, 2019
When ppl started to leave Github, because MSFT bought them, I stated that this is an overreaction.
— ?️? Thorsten Butz (@thorstenbutz) July 28, 2019
Now it turns out, that it was not. But not because of MSFT itself, but because of US law.
This will likely grow to a major fire.https://t.co/XUtGqqEUaz https://t.co/3JBEuEqIxe
https://t.co/9ZkumFLm1T
— Emanuele Rampichini (@emanuele_r) July 28, 2019
How to loose your remote IT job in 3 easy step of you are in a not in a sanctioned Country:
- Go for an holiday to Cuba
- Check something on @github
- Go back home relaxed and discover you have been banned.
1/2
The restrictions are based on place of residence and location, not on nationality or heritage. If someone was flagged in error, they can fill out a form to get the restrictions lifted on their account within hours.
— Nat Friedman (@natfriedman) July 28, 2019
More info is on our policy page: https://t.co/fIobt1pU5E
To comply with US sanctions, we unfortunately had to implement new restrictions on private repos and paid accounts in Iran, Syria, and Crimea.
— Nat Friedman (@natfriedman) July 28, 2019
Public repos remain available to developers everywhere – open source repos are NOT affected.
We're not doing this because we want to; we're doing it because we have to. GitHub will continue to advocate vigorously with governments around the world for policies that protect software developers and the global open source community.
— Nat Friedman (@natfriedman) July 28, 2019
It is painful for me to hear how trade restrictions have hurt people. We have gone to great lengths to do no more than what is required by the law, but of course people are still affected. GitHub is subject to US trade law, just like any company that does business in the US.
— Nat Friedman (@natfriedman) July 28, 2019
Users with restricted private repos can also choose to make them public. Our understanding of the law does not give us the option to give anyone advance notice of restrictions.
— Nat Friedman (@natfriedman) July 28, 2019
Before anyone start hating on GitHub for this: GitLab does this too for their cloud offering too due to being on Google Cloud Platform (but they also offer a version that you can self-host)
— Terence Huynh ?️???✏️ (@terencehuynh) July 29, 2019
Attack the govt policy, not the businesses who are forced to follow them. https://t.co/t3kduN90OY
This is how you address a problem. Explain the context, explain what happened, explain how you are doing your best. https://t.co/2RYompwIkp
— Chris Albon (@chrisalbon) July 29, 2019
2/2 If a user believes that they have been flagged in error, then that user has the opportunity to appeal the flag by providing verification information to GitHub. Please see our FAQ for the appeals request form. https://t.co/MKCLJeUXmz - AG
— GitHub Support (@GitHubHelp) July 26, 2019
Github가 이란, 시리아, 크림 반도에서의 비공개 레포지터리 및 유료 서비스 사용을 차단했습니다. 이는 미국 무역법의 제재에 따른 것으로, 프록시나 VPN을 통한 우회도 불가능합니다.
— bpict (@bpict_) July 29, 2019
Slack 또한 이에 따라 지난달에 일부 국가에서 서비스를 중단한 바 있습니다.https://t.co/ZnDUB8EUlX
Thanks to @Hamed Now we are seen.https://t.co/aQYtjespCS
— Pemi ? o (@pemiphilo) July 29, 2019
GitHub Restricts Developers in Iran and Syria Following U.S. Sanctions - by @mehedih_ - https://t.co/8ocUrSF9Dk pic.twitter.com/mbq8kHe5m7
— Paul Thurrott (@thurrott) July 29, 2019
GitHub confirms heavy restrictions in U.S.-sanctioned regions like Iran and Syria #github #iran #syria https://t.co/iVtRPYc0dH pic.twitter.com/f4c2O1Mteu
— Neowin (@NeowinFeed) July 29, 2019
Github bans users from some regions such as Iran and Crimea due to "US Trade Control Restrictions". Users lamented the abruptness of the action and its unprecedented lack of transparency. #FOSS https://t.co/bs9qEYkgwB
— Satish Babu (@satish_babu) July 29, 2019
GitHub confirms it has blocked developers in Iran, Syria and Crimea #github @smartDataIncLtd https://t.co/LQ0q8qM4KO
— Jasvinder Singh Pathania (@Pathaniajasvin) July 29, 2019
??? We need Web3.0
— Sota Watanabe (渡辺創太) (@WatanabeSota) July 30, 2019
GitHubがイランやシリアで止められた件。公共性の高いサービスと国の意向は混在されるべきじゃない。https://t.co/Cfv6WpwEEa
GitHub confirms it has blocked developers in Iran, Syria and Crimea https://t.co/qb3NMV4rOr
— Ahmed Al Omran (@ahmed) July 29, 2019
GitHub confirms it has blocked developers in Iran, Syria and Crimea. https://t.co/Y5vyHa1ltL
— Winter is coming (@davewiner) July 30, 2019
So here is what we are going to do. We are going to mirror every bit of code from @github and provide it to those nations free of charge. Open source means open to all, not a select few American friendly people.#opensource #github #iran #crimea #cdnpolihttps://t.co/8xtupeuz36
— Squirrely Ron (@SquirrelyRon) July 29, 2019
GitHub confirms it has blocked developers in Iran, Syria and Crimea – TechCrunch https://t.co/pY80EfWfwm pic.twitter.com/34mSZse5Fg
— Rich Tehrani (@rtehrani) July 29, 2019