The Real Blogger Status

Many months ago, I discussed a legal (though highly antisocial) exploit of our blogs - a web site that devotes itself to hijacking those surfers who mistype "xxxxxxx.blogspot.com" as "xxxxxxx.blogpsot.com". Today, we see that in addition to "blogpsot.com", we have similarly "blogpot.com". It's the same deceitful trash, too. The same picture of the Holy Land, and the same phony biblical prophecy and assorted fraud. Please advise your readers to type your blog's URL with care. Type "xxxxxxx.blogspot.com" - not "xxxxxxx.blogpot.com", "xxxxxxx.blogpost.com", or "xxxxxxx.blogpsot.com".

Every week or so, you'll see a complaint from someone. Hey everybody - report http://somehateblog.blogspot.com - it's being used to spread lies about me (my employer, my girlfriend, etc). And right now, there's an ongoing problem with abusive network activity, and the way that Google is protecting itself, that's generated some nasty side effects . Each day, we see a few complaints It's been a week and I am still getting the sorry message: We're sorry... ... but your query looks similar to automated requests from a computer virus or spyware application. To protect our users, we can't process your request right now. The only way to BlogSpot for some readers, right now, may be PKBlogs, and other anonymising proxy servers. PKBlogs was previously developed to provide access to Blog*Spot web sites, when the Pakistan government had a block against "*.blogspot.com" . PKBlogs stepped up, and provided that access, as a public service. But they can be us...

A year or so ago, I started attending a new church. It's a small church, with an active core of members, and it needed a website. I decided that a Blogger website would be fitting, so I setup a web page. And after I had it working, the pastor announced its existence to the congregation.

Here's a link to PChuck's Kitchen . Here's what looks like a link to PChuck's Kitchen . To the unwary, who are like the blogpsot victims , this might be a reason to post Help! My blog has been hijacked by W3.org! Let's look a little closer at the two links above. The working link: http://nitecruzrrecipes.blogspot.com/ The "hijack" link: http://http//nitecruzrrecipes.blogspot.com/ See the extra "http//" in the second link? Now you know. So, the next time you setup a link in your post, and the link goes somewhere weird (and ALWAYS test every link after you add it, and this is why - and I learned this from experience), don't get into the forum of your choice and scream Help! My blog has been hijacked by W3.org! because it hasn't. W3.org is a very well respected member of the Internet community. The World Wide Web Consortium (W3C) develops interoperable technologies (specifications, guidelines, software, and tools) to lead the Web to i...

My blog (one of them anyway) was http://nitecruzrrecipes.blogspot.com/ (now, it's http://recipes.nitecruzr.net/ - but, I digress). Now, I'd hate to have to type that by hand. But that's MY blog.