It Happened Again: Antipiracy Outfit Asks Google To Delist 127.0.0.1 On Behalf Of Ukrainian TV Station

from the where-the-piracy-is dept

We’ve made this point before, but the moment you attempt to scale up copyright enforcement, you run into problems. Collateral damage from automated systems mistaking non-infringing content for infringing, the possibility of fraud and abuse, the blind eye towards Fair Use all become problems. But sometimes those problems are so silly that they expose what a pure fiasco this has become. Several years back, we discussed Universal Pictures asking Google to delist a bunch of supposedly infringing sites, listing one of them as 127.0.0.1. Depending on how computer savvy you are, you may recognize that this IP address is how a computer or system refers to itself. In other words, it essentially means “home.”

And, yet, despite how silly this all is, it just keeps happening. Most recently, the anti-piracy outfit used by a Ukrainian television broadcaster may have outed its own client by also asking Google to delist 127.0.0.1.

Ukrainian TV channel TRK has sent a rather bizarre takedown request to Google. The company’s anti-piracy partner Vindex asked the search engine to remove a search result that points to 127.0.0.1. Tech-savvy people will immediately recognize that the anti-piracy company apparently found copyright-infringing content on its own server.

The request was sent by TKR’s anti-piracy partner Vindex, which essentially flagged a file on its own machine. The ‘infringing’ link is 127.0.0.1:6878/ace/manifest.m3u. This points to a playlist file, possibly for the P2P streaming platform Ace Stream that’s often used to pirate content.

Now, a number of things here should be unsurprising to our regular readers. That an antipiracy outfit sucks at identifying proper sites for delisting is no surprise. Likewise, the idea that a company that is crying about copyright infringement might be guilty of infringement itself also fails to shock the mind. But what is surprising is that the antipiracy outfit may have accidentally outed its own client through its own stupidity as a party infringing copyrights so thoroughly.

Google obviously cannot delist the IP address, as there is nothing to delist. And, frankly, Vindex is known to suck at its one job.

Since 127.0.0.1 refers to the host computer, Google is technically asked to remove a file from its servers. A file that doesn’t exist. Needless to say, Google hasn’t taken any action in response.

The above suggests that Vindex may want to take a good look at its takedown bots. The company doesn’t have a stellar reputation when it comes to DMCA notices. Of all the links that were reported to Google, little more than 10% were removed by the search engine.

Adding to it that you imagine there are some uncomfortable conversations being had between Vindex and its client today and you’re left with the impression that there is a ton of egg on its face right now.

Filed Under: , , , , , ,
Companies: google, trk

Rate this comment as insightful
Rate this comment as funny
You have rated this comment as insightful
You have rated this comment as funny
Flag this comment as abusive/trolling/spam
You have flagged this comment
The first word has already been claimed
The last word has already been claimed
Insightful Lightbulb icon Funny Laughing icon Abusive/trolling/spam Flag icon Insightful badge Lightbulb icon Funny badge Laughing icon Comments icon

Comments on “It Happened Again: Antipiracy Outfit Asks Google To Delist 127.0.0.1 On Behalf Of Ukrainian TV Station”

Subscribe: RSS Leave a comment
32 Comments
Anonymous Coward says:

Wait, wait, wait: A possibly sketch playlist on a client’s own server is sent as a URL in a takedown notice as an infringement on that client’s copyrights?

There’s a whole other level of WTF here.

I mean, maybe the playlist had content from TRK? ¯_㋛_/¯

Also, was Vindex running the scan from the TRK server? I don’t even.

Anonymous Coward says:

Wait, wait, wait: A possibly sketch playlist on a client’s own server is sent as a URL in a takedown notice as an infringement on that client’s copyrights?

There’s a whole other level of WTF here.

I mean, maybe the playlist had content from TRK? ¯_㋛_/¯

Also, was Vindex running the scan from the TRK server? I don’t even.

This comment has been deemed insightful by the community.
Anonymous Coward says:

Re: Re: Re: Re:

and encourage them to at least spend some time checking their work before sending it in

Why would they do that, when they can pass that cost onto Google. Copyright maximalist do not care how much other people spend protecting their copyright, and indeed keep on getting laws passed to make others spend money policing their copyrights, like filters in the E.U.

This comment has been deemed insightful by the community.
James Burkhardt (profile) says:

Re: Re:

Listing 127.0.0.1 as containing an infring should be expressly be a Prima facie admission that no good faith inquiry was made. Not evidence, its an admission of guilt that they did so little inquiry they didn’t even exclude their own "legally obtained material" used as refrence.

bhull242 (profile) says:

Re: Re: Re:

Virtually always true, but you missed my point. The problem is being able to disprove an assertion of good faith made by the defendant to prevail on a claim made under DMCA §512(f). Courts have traditionally given copyright firms and copyright holders a lot of leeway regarding sending out clearly fraudulent DMCA takedown requests when interpreting this section, so plaintiffs rarely succeed with such a claim, usually not making it past summary judgment.

bhull242 (profile) says:

Re: Re:

Well, there are 2 differences.

  1. AFAICT, Vindex hasn’t sued anyone (yet); they’ve only sent out DMCA takedown requests. Prenda, OTOH, really only brought lawsuits, and (again, AFAICT) never sent any DMCA notices. So, to Vindex’s credit, they haven’t sued anyone for copyright infringement with their IP-tracking systems.
  2. OTOH, Prenda was never dumb enough to essentially admit or declare, under penalty of perjury, that they were using a honey pot. They were at least smart and competent enough not to sue the person at IP address 127.0.0.1 or claim that someone infringed their copyright using that IP address

Add Your Comment

Your email address will not be published. Required fields are marked *

Have a Techdirt Account? Sign in now. Want one? Register here

Comment Options:

Make this the or (get credits or sign in to see balance) what's this?

What's this?

Techdirt community members with Techdirt Credits can spotlight a comment as either the "First Word" or "Last Word" on a particular comment thread. Credits can be purchased at the Techdirt Insider Shop »

Follow Techdirt

Techdirt Daily Newsletter

Ctrl-Alt-Speech

A weekly news podcast from
Mike Masnick & Ben Whitelaw

Subscribe now to Ctrl-Alt-Speech »
Techdirt Deals
Techdirt Insider Discord
The latest chatter on the Techdirt Insider Discord channel...
Loading...