Re:GitHub confirms it has blocked developers in Iran, Syria ...
by theturtletalks on Monday July 29, 2019 @09:18AM
(#20554281)
They added the option to make private repos public so you can back it up. But again, you can’t delete the now public repo.
[ Parent
| on HN ]
Re:GitHub confirms it has blocked developers in Iran, Syria ...
by emilfihlman on Monday July 29, 2019 @09:40AM
(#20554464)
>They added the option to make private repos public so you can back it up.
And allow all to see their contents, likes business and trade secrets. Top tier.
Re:GitHub confirms it has blocked developers in Iran, Syria ...
by theturtletalks on Monday July 29, 2019 @09:43AM
(#20554489)
Yep. If you want to access your blocked private repo, you literally have to let everyone access it. And you can’t even delete it afterwards.
Re:GitHub confirms it has blocked developers in Iran, Syria ...
by mieseratte on Monday July 29, 2019 @10:08AM
(#20554722)
> Yep. If you want to access your blocked private repo, you literally have to let everyone access it. And you can’t even delete it afterwards.
One must wonder just how many companies with juicy trade secrets situated in a nation with adversarial relations to the US are hosting that juicy data in the US, with a US corporation.
Given that the public, open-source situation is not changed this is starting to sound like a tempest in a teacup.
Re:GitHub confirms it has blocked developers in Iran, Syria ...
by tedmiston on Monday July 29, 2019 @02:52PM
(#20558003)
Couldn't one temporarily travel outside of the affected regions to access their private repos normally?
Re:GitHub confirms it has blocked developers in Iran, Syria ...
by theturtletalks on Monday July 29, 2019 @04:15PM
(#20558898)
Github does have an appeal process if the algorithm mistakenly tagged you. I’m not sure what proof they ask for.