I am sad to report that my RSS feed for oracle-wtf definitely made me say WTF! but not in a good way. Actually visiting the site confirmed my suspicion, it’s been hi-jacked by a splogger. Take a look and be sure not to reward this guy by clicking anything.
If my memory serves, this has happened to some other high-profile bloggers in our community and although I forget the victims it was a difficult process for them to actually recover the articles; if I remember correctly google’s terrible customer service in this regard actually triggered quite an exodus of blogs away from the blogger platform. Doug – didn’t this affect you?
It will be interesting to see how google handles this now, perhaps they’ve learned something in the last year or two. In the meantime, Tony, Scott, Will, James, Thai and Adrian – best wishes and good luck from all of us here at Pythian. Let us know how you make it out of this mess.
And it strikes me that this might be a good time for all of us bloggers to take a second to verify that our passwords are secure… :-}
2 Comments. Leave new
>> Doug – didn’t this affect you?
It certainly did and it’ll be a while before I forget it. Your URL only has to be free for a nano-second (slight exaggeration, I think it might have been 10 minutes in my case) and some spammer parks there.
I knew this would happen to more and more people and whilst I wouldn’t wish it on anyone, it’s further evidence that Blogger handle this stuff badly. When there are alternatives, why would anyone put up with this?
The punchline in this particular case is that, if you note APC’s comment on my blog (click link above), it was the Blogger people who caused this! Apparently Oracle-WTF looked like a splog, but it’s been replaced by something that doesn’t??! If it wasn’t so pathetic, it would be funny.
Sorry, I should have said …
>> And it strikes me that this might be a good time for all of us bloggers to take a second to verify that our passwords are secure… :-}
I certainly kept my password secure and I’m sure William did the same – this can happen without any mistakes on the blogger’s part whatsoever – entirely Blogger’s fault!