Live data from Hacker News

GitHub confirms it has blocked developers in Iran, Syria and Crimea

techcrunch.com

201–210 of 336 posts

Re: GitHub confirms it has blocked developers in Iran, Syria and Crimea

#201
post #30

Earlier quoted context omitted.

Not like the US government is any better right now

As long as the government just calls people names instead of invading them, I am completely fine with that. Progress, I guess.

Because the US government hasn't invaded other countries...?

Of course they call it something different, but they do tend to start wars periodically. For flimsy reasons.

Re: GitHub confirms it has blocked developers in Iran, Syria and Crimea

#202
post #98

Earlier quoted context omitted.

You realize that sanctions also kill people through lack of supplies like medicine being available, people being unable to economically support themselves, and, if the sanctions cause the government to collapse, all the death that results from that. So let’s not pretend sanctions are somehow nonviolent.

Everything that reduces quality of life kills people in some way. Heck, I commute through a town that back in the day was rich enough to prevent the highway from being expanded. I bet a couple people have died in ambulances in gridlock there. Sanctions are a heck of a lot less violent than bombs, or some tit for tat response (which would probably eventually escalate to bombs). They're basically one step up from taxes…

But how many lives were saved from not having a fast moving road running alongside the town.

Everything is good and bad.

Re: GitHub confirms it has blocked developers in Iran, Syria and Crimea

#203
I think it is interesting and a shame that we accept centralized issue tracking at all. Git is wonderfully distributed, probably in more than most of the github users realize. Unless they've gone out of their way to learn about it.

When things like this (github's ban) happen, I think it is too bad that we don't have a widely accepted issue tracker built into git. To be a little more clear, you'd get all of the source and all the issues when you clone or pull. Updating would work just like updating files when you push.

Microsoft has appeared to start loving open source. I'm sure there are people there that do, but Microsoft itself I wouldn't be so sure. The are certainly embracing it. https://en.wikipedia.org/wiki/Embrace,_extend,_and_extinguis...

Re: GitHub confirms it has blocked developers in Iran, Syria and Crimea

#204
Saw some other debate in here about whether the law applies only to countries or also to individuals... Here's two federal govt lists of banned individuals:

https://www.bis.doc.gov/index.php/the-denied-persons-list

https://www.treasury.gov/resource-center/sanctions/SDN-List/...

Re: GitHub confirms it has blocked developers in Iran, Syria and Crimea

#205

I'm curious.. why is this very suddenly an issue? Haven't countries like Iran and Syria been under embargo for years? Have more restrictive laws around sanctions been passed in recent weeks?

[flagged]

That's an interesting way to jump.

Re: GitHub confirms it has blocked developers in Iran, Syria and Crimea

#206
post #2

Same as Gitlab then[0]. US Sanctions should not affect internet services (so long as they are provided for free)[1], but political pressure appears to be very strong. Personally I find it quite abhorrent, and would cite this as a reason not to use US based companies in future. [0]: https://about.gitlab.com/2018/07/19/gcp-move-update/ [1]: https://www.treasury.gov/resource-center/sanctions/Programs/...

Like I wrote somewhere else, the Gitlab case is both worse and better. Gitlab did not make a specific decision to block Iranian users, it merely made a technical decision to move to Google Cloud, and Google Cloud is blocking sanctioned countries on a network level (which is abhorrent). But I don't see Gitlab making an active decision that they have to do this for sanctions compliance reasons, it was just a side-effec…

See comments in this previous thread from 31 days ago [1]...

Google Safety & Security Blog: An update on state-sponsored activity (2018) ...

Detecting and terminating activity on Google properties

"Actors engaged in this type of influence operation violate our policies, and we swiftly remove such content from our services and terminate these actors’ accounts. Additionally, we use a number of robust methods, including IP blocking, to prevent individuals or entities in Iran from opening advertising accounts."

---//---

[1] "An Open Letter to Google and Apple: Stop Hindering Iranian Entrepreneurs"

https://news.ycombinator.com/item?id=20302547

Re: GitHub confirms it has blocked developers in Iran, Syria and Crimea

#207
post #11

We made it point now to avoid all US-based services. While we're not affected by the sanctions yet, it seems like it is a possibility in the future. There's really not a lot of reasons to use Gitlab or Github or Slack or a number of other services. They're not exceptional in any way and can be replaced by other open-source or commercial projects.

Convenience and speed aren't reasons? You're handicapping yourself against your competitors, and no one who does that lasts very long.

Don't see it that way. If I set up a process once, using software that's been tested and been around for a while, it's extremely convenient. And free. And there's no risk of deplatforming.

Re: GitHub confirms it has blocked developers in Iran, Syria and Crimea

#208
Posting Nat Friedman's tweets here so they're easier to read - they're doing more than most companies about the whole thing, not sure where the vitriol in these comments is coming from:

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.

To comply with US sanctions, we unfortunately had to implement new restrictions on private repos and paid accounts in Iran, Syria, and Crimea.

Public repos remain available to developers everywhere – open source repos are NOT affected.

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.

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.

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.

Re: GitHub confirms it has blocked developers in Iran, Syria and Crimea

#209
post #166

Earlier quoted context omitted.

If I recall right from previous thread they can still create and commit to public repo but can't delete them. They also can't touch even their own private repo anymore.

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.

>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.

Post reply on HN