It sends usage data to Google Analytics. I can see how this can translate into you getting caught. Be careful.
Even if you don't have a 'trackingId' set it still sends GET requests to http://google.com/
It's not proof of piracy. It just proves that some bytes were downloaded. What, for example, if you could prove that you paid for the movie you're downloading? Lets say you buy a movie using the Video app on the Xbox, but want to watch it on your old Windows XP desktop, or on your Android phone?
Which is why copyright needs to be dragged, kicking and screaming, into the modern age.
Though if you personally join the peer queue and serve over 30s of a movie to them, you've just proved that someone using that IP is pirating that movie. Even if you own the movie elsewhere, if I recall correctly many jurisdictions do not protect the personal transfer you're talking about. The laws are quite stupid here, but that's just how it is.
I'd be very surprised to learn there's a legal way for you to do this considering the movie you download on your Xbox is going to be PlayReady DRM encumbered.
1. You're downloading. This may or may not be copyright infringement, even if you do already have other licence[s] for the media. Check the licences and the law, if you can understand either.
2. If you're seeding, you're allowing others to download from you. If you're not licensed to do this by the copyright holder [if any], you might be infringing in certain jurisdictions.
127.0.0.1 ssl.google-analytics.com
127.0.0.1 www.google-analytics.com
127.0.0.1 google-analytics.comNaturally this will also block you using google.
Its more of drastic stop tracking me measurement.
I block it with Ghostery.
Piwik with Nginx was easy enough to set up and provides the data I am interested in, including conversions of goals (something I was dubious about before installing). New version even more snazzy than previous.
I'm sure it's fine from a functional perspective.
The binary you download from Mega.co.nz uses "YIFY Torrents" website yts.re exclusively. Github code seems to be actually used. So it all runs via this single webserver (+Google analytics). Just to verify what a installed binary blob does on your Linux box. The ease of use is impressive, a new level for P2P-ish work since Napster/Kazaa/Limewire days.
curl http://someonewhocares.org/hosts/hosts | sudo tee -a /etc/hostsGiven the demographic of this site, I thought I'd be insulting everyone's intelligence by offering up a more verbose description. I mean the description is the command itself! And verifying the contents of the URL is as simple as viewing a web page (if anyone can't manage that then I wonder how they're reading that command to begin with :p).
With `curl http://someonewhocares.org/hosts/hosts | sudo tee -a /etc/hosts`, you know that the damage is contained to appending malicious data to /etc/hosts. Furthermore, the use of tee guarentees that you see the data that gets appended. Additionally the potential damage of malicious data in /etc/hosts is minimal if quickly detected and fixed.