5 ms·

I don't live in the USA, why should I be affected by the RIAA and DMCA outside the USA? If I ping github.com, it is resolved as lb-140-82-121-4-fra.github.com ,

by aries1980 6y ago

I don't live in the USA, why should I be affected by the RIAA and DMCA outside the USA? If I ping github.com, it is resolved as lb-140-82-121-4-fra.github.com , so what is the rational behind the global takedown?

explodingcamera 6y ago
Most Countries don't care about where your server are, as long as you're registered as a company somewhere, you need to stick to those laws.
- aries1980 6y ago
  This doesn't stand for many legal cases, including copyright, work rights, taxation, etc. I don't see why this case should be an exception with having an effect outside the US jurisdiction.
cricalix 6y ago
Based on the DNS name, I'd guess that's a load balancer either in a Frankfurt (DE) point of presence, or a Frankfurt data center. If it's a POP, then it's probably just a cache to the servers in the DC, which could still be in the USA. End of the day, Github is a US-based business, and they are subject to US laws, and thus all of their customers/users are affected by those laws, whether or not they're in the USA.
zadokshi 6y ago
A company is liable in multiple places. - Where the servers are located. - Where the comparably offices are located, - where the business is registered, - where the employees live or travel to/from - employees in any country who are quite happy to ship people to the US even when that employee has not broken any law.
dredmorbius 6y ago
Though the claim is made under US law, similar anti-circumvention provisions exist in international law, which is highly standardised in large part thanks to the RIAA, MPAA (video), SIIA (software), WIPO, and other copyright monopoly cartels' special-interest deep-pockets lobbying. Offshore legal safe havens are limited and vulnerable. Defence within DMCA /anti-circ / WIPO / Berne regions is unfortunately necessary. Simply hosting the repository outside US jurisdiction is not sufficient, though a valid immediate response. From TFA. I supect this was included by the author in anticipation of such questions.
- aries1980 6y ago
  Thank you for the clarification.

explodingcamera 6y ago

Most Countries don't care about where your server are, as long as you're registered as a company somewhere, you need to stick to those laws.

aries1980 6y ago
This doesn't stand for many legal cases, including copyright, work rights, taxation, etc. I don't see why this case should be an exception with having an effect outside the US jurisdiction.

cricalix 6y ago

Based on the DNS name, I'd guess that's a load balancer either in a Frankfurt (DE) point of presence, or a Frankfurt data center. If it's a POP, then it's probably just a cache to the servers in the DC, which could still be in the USA. End of the day, Github is a US-based business, and they are subject to US laws, and thus all of their customers/users are affected by those laws, whether or not they're in the USA.

zadokshi 6y ago

A company is liable in multiple places. - Where the servers are located. - Where the comparably offices are located, - where the business is registered, - where the employees live or travel to/from - employees in any country who are quite happy to ship people to the US even when that employee has not broken any law.

dredmorbius 6y ago

Though the claim is made under US law, similar anti-circumvention provisions exist in international law, which is highly standardised in large part thanks to the RIAA, MPAA (video), SIIA (software), WIPO, and other copyright monopoly cartels' special-interest deep-pockets lobbying. Offshore legal safe havens are limited and vulnerable. Defence within DMCA /anti-circ / WIPO / Berne regions is unfortunately necessary. Simply hosting the repository outside US jurisdiction is not sufficient, though a valid immediate response. From TFA. I supect this was included by the author in anticipation of such questions.

aries1980 6y ago
Thank you for the clarification.