The log of a "splog"
Not very pleasing, but, as I discovered, there's a "splog", meaning, a spam-blog, that's been siphoning content from my own blog for a few months now, probably by logging on to my RSS feed, I'm not sure. It's on a server called 120host, and here's the URL, where, with the possible exception of anything that involves javascript in the post, it's been copying off of my blog and, if I'm sending a trackback ping to some Wordpress blogs (it's powered by their software), it seems to follow suit.
According to this blogger here, who's also been getting content siphoned from this server:
According to this blogger here, who's also been getting content siphoned from this server:
It's a "splog", or a spam blog. A splogger syphons high-quality content from an original blog (We are talking high-quality in baesian terms. It can be utter trite as far as humans are concerned.) Visitors from search engines then visit the splog and drive the ad revenue.I still don't like it. Maybe it's possible to contact Wordpress administration about this, and ask if they can do anything about it, so I'll have to think about it sometime.
I have quite a few of them attached, although the 120host is unique because apparently it seeks me personally (e.g. it double-sourced my content from Advogato when available).
There's no way to complain to anyone about the 120host.net. It is a website run by sploggers (which also allows free registration for everyone, as a fig leaf).
Labels: technical matters