Tag: blogger sucks

Guffaw’s site shows that Blogger has deleted it.  Via email tonight:

I’m told one of my ads may have generated spam.
If that’s the reason, it’ll probably be restored in a couple days.
Will advise as I know more.
gfa

Let’s hope they fix this soon.  Don’t you think it would be a good idea to contact the site owner BEFORE you yank the plug on him?

UPDATE:  He’s back.

I haven’t used the “blogger sucks” tag in quite a while, but it appears at the moment that Blogger has eaten my last post from Thursday. Hopefully they’ll be restored at some point (I’m fearing that Blogger’s last backup has been corrupted), but I’m not counting on it.

Thankfully, one post I have in draft survived whatever happened yesterday. It’ll be going up tomorrow, assuming that it doesn’t get bloggered before then.

Oh well, anything free is worth what you pay for it.

UPDATE:  It’s back.  That’s good.

Really, for a free service, Blogger started off sucky but it’s gotten a lot better over time.  This is the first major problem I can recall in the last couple of years, and Blogger is hardly the only platform to have problems.  As noted in the comments to the post Busy below, Doc Russia is having issues with his host, and his blog Bloodletting has been unavailable for some time now.

I received this from Disqus tech support this afternoon:

Hi,

The reason why these comments from Echo aren’t importing is because they aren’t given a URL to link the comment to, unfortunately. We’d love to be able to offer a way to bring them in, but for now it’s not possible with this format. We’ve opened a ticket with our development team for any possible ideas of how to do this, but it’s still in the planning phases.

We’re sorry for any inconvenience, we know it’s important to import your existing comments, so hang onto those files.

Thanks again for using Disqus

So apparently the export files from Echo/JS-Kit don’t have identifying tags that Disqus can recognize. But Chris Byrne was able to successfully import his comments. I’m alone in having fvcked-up export files?

AAAAAAAAGGGGH!

Google: Still Evil

As most of you probably know, Google bought Blogsnot awhile back. Google also agreed to censor the web for those accessing it from China, at the insistence of the Chinese government.

I discovered something fascinating (in a creepy way) tonight. When I write a post, I put the title for it in a block marked “Title,” then repeat it as the header to the body of my post. The “Title” space, I suppose, goes out to RSS feeds and such, but if I don’t repeat the title in the body, you won’t see it. Whatever goes in the “Title” block is made part of the URL for that post, assuming, of course, that the title isn’t as long as many of my posts are. It’s truncated at twenty letters or so, and “the” and “a” are dropped out. My post last week “Made as China, Norinco”, should have carried a URL that reads:

http://smallestminority.blogspot.com/2009/02/made-as-china-norinco.html

It does not.

Google truncated the link to http://smallestminority.blogspot.com/2009/02/made-as.html

The words “China” and “Norinco” were redacted.

Kinda makes you wonder why, doesn’t it?

Working on a LONG Post.

Which just got eaten by a Firefox crash. And I was depending on Blogger’s autobackup to save me. Guess not. Dammit.

Y’all will just have to wait a bit longer.

You would think after five years I’d learn to BACK UP MY WORK. But noooooooo!

I just spent the last hour and a half working on a killer post, and I just deleted it – BY ACCIDENT.

Rule #1: Back up your work.

Rule #2: See rule #1.

It’s too late to generate it again tonight, but rest assured I’ll do it tomorrow.

DAMNIT!