Rojo, Spam Splog
I’m getting somewhat annoyed with Rojo, the web-aggregator and personalized search engine, who are copying my content:
This would be ok if they used javascript to dynamically pull and parse my feed, but no, they write it into a page that’s publicly viewable. This means they’re essentially making their site run off the stolen content of millions of bloggers. Since I’m opposed to content-theft, copyright-infringement, etc, I sent them an email:
ATTN: Rojo
Several of your pages, including but not limited to:
www.rojo.com/feed/zZrv8kvc19zskDnK
contain copies of intellectual property belonging to the Elliott Back Blog Network. Please remove these and any other pages copying content from elliottback.com or any of its subdomains, and cease and desist any future copying.
Guess what I got back from Rojo, almost at once:
This message was created automatically by mail delivery software.
A message that you have sent could not be delivered to one or more
recipients. This is a permanent error. The following address failed:copyrightnotice @rojo.com: 550 5.7.0
So Rojo can’t be contacted at the address they list for copyright issues. What to do next? I think I’ll call someone high up there.
| This entry was posted on Tuesday, February 27th, 2007 at 10:02 pm and is tagged with mail delivery, delivery software, copyright infringement, copyright issues, subdomains, bloggers, aggregator, intellectual property, email, spam, search engine. You can follow any responses to this entry through the RSS 2.0 feed. You can leave a response, or trackback. |
4 Responses to “Rojo, Spam Splog”
Leave a Reply
[...] Original post by Elliott Back and a wordpress plugin by Elliott [...]
Unfortunately the number of websites stealing / copying content from other sites, with the soul purpose of generating traffic for their Google ads, has grown rapidly. They use multiple (sub)domain names, which makes it difficult to prevent these practices. Sending them (sites like Rojo) an e-mail won’t help; however it’s possible to report an AdSense policy violation to Google (adsense-abuse@google.com).
This is an issue that is going to spring up more and more often as we explore content syndication. Why do you think we even bother to call it syndication? Releasing your content as RSS opens the floodgates for this kind of behavior. In the end is it really so bad? Does Google not have quite a lot of people’s content stored locally? /Devil’s advocate
I hope you saw that Anil Dash announced in the comments on PlagiarismToday.com that Rojo & Nooz have updated copyright abuse contact info.
My most recent email didn’t bounce … but my content remains on their site.