In this case, you're the one that misunderstands the problem. Proxies
are part of the fabric of the internet, and aren't stealing your
content any more than the routers carrying the packets of this email
message.
It's unfortunate (or funny) that somehow the proxy ranks higher in
search engines than your site does, but you have the complete ability
to fix this yourself. You don't need Google's help.
The simple solution is to block requests from wapfree-ec. All
urlfetches from GAE include the appid in the User-Agent header.
Viola, problem solved. If you want to be heavy-handed, you can block
all requests from GAE.
If you want to be really clever about it, serve different content to
wapfree-ec. Like, say, a blank page with a big link pointing at your
website. You might improve your own SEO juice that way.
Last of all, stop blaming other people for your mistakes.
Jeff
Jeff
On Tue, Apr 17, 2012 at 9:29 PM, Brandon Wirtz <dra...@digerat.com> wrote:
> You can block URL Fetches from GAE by checking the request headers which
> will identify as both GAE and the Application ID that is making the request.
>
>
>
>
> --
> You received this message because you are subscribed to the Google Groups "Google App Engine" group.
> To post to this group, send email to google-a...@googlegroups.com.
> To unsubscribe from this group, send email to google-appengi...@googlegroups.com.
> For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en.
>
I always play the good cop. I beat the dumb people, they get smarter long
term. It's all about how long it takes to see that I'm right. ;-)
Oh you meant the "Nice" cop. Yeah well, I figure this guy is just passing
by. He won't be here in a week...
http://en.wikipedia.org/wiki/Canonical_link_element
Have to be careful there tho, as many proxies, will blindly rewrite
all links in a page to point to themselves (usually as relative links)
... I just checked. wapfree-ec alters the canonical tag.
So would have to find a way to defeat their link parser, but still
write it in such a way that search engines would still understand!
The theory that makes proxy servers OK under DMCA is that they are a § 512(a) Transitory Network Communications Safe Harbor
One of the requirements for that case is that the content " is not modified in any way,"
So I would recommend the the OP alert google that the app in question is modifying their content, creating a derivative work without authorization, and must be removed under DMCA.
-Joshua
He could argue about it for weeks with lawyers, or he could fix it
himself today. Only one of these approaches will actually solve the
problem.
Jeff
And although he can certainly defend himself now, that does nothing to help others who are being copied by the same not-really-a-proxy-server, and it doesn't do anything about his search results, which could take weeks or months to recover.
-Joshua
Good luck with that.
Jeff
If it rewrites the links then, I'm sorry, it *isn't* a proxy server.
Jeff Schnitzer: "Last of all, stop blaming other people for your mistakes."
Jeff Schnitzer: "The proxy just happened to rank higher in Google that the original content, probably due to the same technical ineptitude that caused him to rant here on this list. "