>>Counter measures please, just like we neutered the Helms Burton act at the time. It's simple:
Any person/company in Europe that suffers losses due to a unilateral domain seizure in the US, can sue for damage any US company (and all their holdings in Europe) for damages + costs, and maybe even plus punitive damages. Board members of such companies would be denied entry in the EU/EEA.
It worked for Helms Burton it will work for SOPA / PROTECT-IP / E-PARASITES or whatever bullshit name they give that act.
<<
>EU law also applied sanctions against US companies and their executives for making Title III complaints.
>The United Kingdom had previously introduced provisions by statutory instrument[8] extending its Protection of Trading Interests Act 1980 (originally passed in the wake of extraterritorial claims by the U.S. in the 1970s) to United States rules on trade with Cuba. United Kingdom law was later extended to counter-act the Helms–Burton Act as well.
>Mexico passed a law in October 1996 aimed at neutralizing the Helms–Burton Act. The law provides for a fine of 2.2 million pesos, or $280,254, against anyone who while in Mexican territory obeys another country's laws aimed at reducing Mexican trade or foreign investment in a third country.
>Similarly, Canada passed a law to counteract the effect of Helms-Burton
Not the same counter measures as the ones proposed by the original user but it seems to have the same effect of "neutering" a foreign law.
For some reason, my browser didn't trust the https certificate for this site. Rather than continuing anyway, I simply removed the 's' in the 'https' portion of the url, and it resolved. Not sure why the https version was linked in any case.
I use HTTPS Everywhere and it converts a lot of domains to the HTTPS version, including TorrentFreak. Maybe the OP uses this extension, too. I didn't get a certificate error, though.
Sorry for being dense, but could you elaborate on what I should learn from that thread you linked? Is there some kind of solution there, maybe if I was using Chrome, that I might have missed?
To summarize the linked thread: Some browsers, when you load an "https" page will complain if any of the elements on that page load over "http". For example, the story above loads some Twitter-y stuff from http://platform.twitter.com.
The technically correct fix is for the site owner to modify the page to load all these resources over https when the page is accessed over https. Until they do that, as a workaround, you could install an extension like the one mentioned by fl3tch[1] to do it in your browser.
N.B. That only works if the resource is available over https, many are not. In that case there is no fix.
The technically correct fix is for the site owner to modify the page to load all these resources over https when the page is accessed over https.
The easiest way to do that is with protocol-relative URLs. You're probably familiar with relative paths in URLs, e.g. if example.com/test/test.html loads an image at pics/pic1.png, it will really look in https://example.com/test/pics/pic1.png if you loaded it over https, or http: if you loaded over http.
Simple, right? Well, you can use the same idea for absolute paths and even resources from other sites! So if a different site links to the URL //example.com/test/pics/pic1.png (note the lack of protocol before the double-slash), then it will use https: if you loaded the page over https and http: if you loaded it using http.
This is really just a vague complaint more than anything.
It would be interesting if this resulted in .com/.org/.net becoming de jure international (they are de facto international domain names now), and removing them from US control.
This is an EU parliament resolution, and the EU parliament has very little real power. That doesn't make it politically meaningless, but it in no way compels the European Commission or the joint EU governments to actually do anything about it.
The Parliament must approve the EU's budget (and has rejected it for political reasons before), approve the Commission's staff, the Parliament has even taken the Council to court about its failure to propose a budget on-time, 80% of all laws must be passed by the Parliament to come into force, has made plenty of amendments to directives, and it most famously had its forthcoming vote of no confidence force the Commission to quit in the 1980s. [1]
In this case, it can use its influence over the Commission to get it to propose legislature. Has done very similar things in the past. And don't forget, these MEPs can influence the direction of Council, especially via countries like Italy who are really keen for the European Parliament to have more power and influence.
This obviously doesn't mean a directive will appear tomorrow, but such resolutions are an essential and powerful step towards change in European Politics.
>>Counter measures please, just like we neutered the Helms Burton act at the time. It's simple:
Any person/company in Europe that suffers losses due to a unilateral domain seizure in the US, can sue for damage any US company (and all their holdings in Europe) for damages + costs, and maybe even plus punitive damages. Board members of such companies would be denied entry in the EU/EEA.
It worked for Helms Burton it will work for SOPA / PROTECT-IP / E-PARASITES or whatever bullshit name they give that act. <<
Link to Helms-Burton:
http://en.wikipedia.org/wiki/Helms–Burton_Act#Reactions