I just noticed another incident of blog contents theft. This blog post I wrote in December 2006 has been copied and pasted into http://www.veryangel.cn/1034/use-the-freeking-condom-more-shameless-remarks-by-larko. No permission asked, not even a reference to the source. All of the “blog” seems to be stolen contents pepped up with Google ads, of course.
A WHOIS inquiry shows that the domain was registered just a few days ago and they are already busy steeling food from bloggers’ tables. The registrant organisation looks something like this 上海澳凯信息技术有限公司 and the registrant name is 徐光寅. I guess that would make it somewhat difficult to sue them.
My constructive suggestion (i.e. freedbacking) to the WordPress.com team is to block these contents thieves from access to WordPress.com blogs. My constructive suggestion to 徐光寅 would be to stop steeling my contents at once. Also, send me all your money and an I owe you where I can fill in the numbers.
There is another thief around whose robot monitors and steals posts from allover WordPress.com. I am not linking to this bastard but the URL is http://ultravb.com/arsiv/. The dude calls himself Webmaster Arşivi.
He did, however, make the mistake of pinging to one of my posts so I got his IP 220.127.116.11. Apparently, this clown sits in Turkey. My suggestion to WordPress team is to block all traffic from him.
Edit: Just as I expected, the jerk has even stolen this post: http://ultravb.com/arsiv/another-blog-contents-thief/
A week ago I wrote about a bold theft of my blog content. A couple of days later it looked like the thieves had taken down their page http://dogstrike.net/view.php?id=102481 but it was up again as I checked a moment ago. It very much looks to me like all of the site dogstrike.net consists of stolen posts from diffferent blogs in WordPress.com.
Looking at the WHOIS records of that site reveals that it very much looks like the domain has been registered with fake information. As far as I know, there is no Lenin Street in Istanbul and the phone number of the alleged registrant, who is supposed to be based in a non existing address in Istanbul, is Russian. The same goes for administrative, technical and billing contacts.
Interestingly, the same WHOIS lookup shows that the domain has been registered by KLIK MEDIA GMBH, a Berlin based business that Spamhuntress delivers interesting information about. They have been known to register regular spam sites but it now looks like they have also entered the business of stealing blog contents from bloggers like you and me.
Registering a web domain under so obviously fake coordinates as is the case with dogstrike.net is difficult unless the registrar plays along in the game. An honest registrar would have the interest of having the correct details. How else can they be sure that they are going to get their bills paid? The obvious answer is that they can not unless they are behind the site with fake initials themselves.
I know that there is no 100 % working way to get this sort of thieves out of business but I also know that their life can be made a bit more difficult. Therefore, my suggestion to the WordPress.com team is to have a look at the traffic from certain domains and IP’s and put up some blocks to make it that much more difficult to steal the contents of blogs hosted by WordPress.com.
And my suggestion to Staatsanwaltschaft Berlin is to investigate the background and business practice of this KLIK Media GmbH, Alt-Karow 3, 13125 Berlin, tel +49 30 9441 3291. I bet a thorough investigation would uncover interesting details for the prosecutors to work upon.
Tags: bloglines, freedbacking
I received this standard error message from Bloglines:
Internal Server Error
The server encountered an internal error or misconfiguration and was unable to complete your request.
Please contact the server administrator, email@example.com and inform them of the time the error occurred, and anything you might have done that may have caused the error.
More information about this error may be available in the server error log.
The time was 4th July, 2006 at 5.28 a.m. (GMT +3). I did indeed do something that may have caused the error. I clicked to one of my feeds hoping to read the posts. Repeating the action brought the site back on line. However, the posts in that particular feed were gone because the server obviously regarded them as read.
Tags: bloglines, freedbacking
Chris Pirillo recently introduced the term “freedbacking” to stand for free feedback from users to developers. Freedback has so far not spread widely neither in WordPress tags nor Technorati tags. But the first posts have seen the cyberlight so this great idea is sure to catch on eventually.
The Bloglines were not slow to announce that they expect to receive freedback from their users. At this moment I have little to provide them with. Apart from one of my own blog posts appearing to have been updated while I was sleeping yesterday, I have nothing of significance to report back.
But let us just test if this freedbacking concept would work within WordPress. I have noticed yesterday and today that automatic pingbacks to my posts work in a funny way. The pingback link points to the pinging post but the author is being displayed as anonymous and the comment field is empty. Manual trackbacks work as they are supposed to.
This is just a minor inconvenience but it gives me a good chance to test the new way of freedbacking.
Update (3rd July, 2006): The pingback feature seems to be working normally again.