Bag o' Burning Blogger
Tuesday, March 29, 2005
I'd been hearing rumblings around the blogosphere about my fellow bloggers having difficulties with Blogger, but so far, my difficulties had been minimal, probably owing to my whacked-out (read: frequently past midnight) posting schedule. But yesterday was horrid! I now understand, on a visceral level, why such heavyweights as the Belmont Club left. Closer to home, Martin Lindeskog has at least considered the possibility with dread at the implied prospect of having to change his URL. That post, dated March 18, quotes Blogger Status as saying,
Users with more than 500 posts are also being severely hampered at this time. We believe this is due to an improper use of system resources when users of such blogs either access the Edit Posts page or attempt to publish. We will be testing a potential fix to this problem over the next couple days and hope to push it to production early next week. Because of the extent of the change, we need to fully assess the impact on the service before deployment.
If anything, I've noticed a degradation in service since then. I was about to complain that it has been more than a weeks since that last post, but I checked Blogger Status just now and found a possible explanation for the agony I experienced last night in lieu of the ecstasy of a good blogging session: They made a bad kernel upgrade and are now in the process of rolling it back. If this is true, then they will be going back to the earlier operating system kernel that they obviously felt the need to upgrade! Yes, they have more servers now, but my confidence is quite understandably shaky at the moment.
So last night, I actually got home before 8:00 pm! The wife was hard at work on her dissertation, so I decided to make lemonade out of that lemon: "Wow!" I thought. "I have five hours to edit a post, maybe write another, and work on my blog template!" What actually happened in that five hours?
1. The post I thought I'd saved was gone. It took me at least ten login attempts to learn this sad truth.
2. In no mood to rewrite that one over a phone modem, I chose a quicker topic to write about. This time, I used my Mozilla editor (which I'm doing now) so that Blogger couldn't eat it, too.
3. After some outrageous number of logins and internal server errors, I finally got the post up. Twice. A third version was saved as a draft. This took at least 30 minutes to fix.
4. I got to remove the remodeling message from my template. I tried a few other edits, but these were going nowhere and it was already closing in on midnight.
5. I set a new record for Blogger logins!
2. In no mood to rewrite that one over a phone modem, I chose a quicker topic to write about. This time, I used my Mozilla editor (which I'm doing now) so that Blogger couldn't eat it, too.
3. After some outrageous number of logins and internal server errors, I finally got the post up. Twice. A third version was saved as a draft. This took at least 30 minutes to fix.
4. I got to remove the remodeling message from my template. I tried a few other edits, but these were going nowhere and it was already closing in on midnight.
5. I set a new record for Blogger logins!
Five hours, and the most noticeable long-term effect for me is that my wrists hurt a little, I have the lesser of two blog entries posted that I wrote, and my template is barely passable. For reasons I am keeping close to the vest, I will have an influx of new readers soon. Hopefully, the content will keep them coming back, 'cause the template probably won't exactly be eye candy by then.
So here's my gripe about Blogger right now. This is my hobby. I love to write. I like the fact that I have a chance to get intelligent feedback from my small, but loyal band of regular readers. I have even made a handful of new friends doing this. This has been a rewarding hobby, but Blogger managed to turn this delightful pastime into a penance last night. After that experience, I woke up hating my blog this morning and resenting having lost nearly a quarter of a day of my life (and a fun five hours it was supposed to have been).
Like Lindeskog, I'd rather stay put at this web address, but I won't if I come to dread every attempt to publish or make a small change to a template, or answer comments. He wants to throw eggs at Blogger. He's a lot nicer than I am. About now, I feel like touring the corporate offices of Google, or whoever else owns them and stopping at each office door with a little surprise.
Each occupant will hear a knock. He'll answer the door. And he'll be stamping out a burning bag of Blogger to the tune of the sounds of me running off!
Well. I feel better now. But then, I still have to publish.
And that's my long way of saying, "I might take the rest of this evening off from Blogger." I may write something, but if I do, it may save it for posting in the morn.
-- CAV
PS (aka Blogger User Testimonial, an abbreviation that happens to spell the conjunction most commonly used after praising Blogger's performance): I'm on Blogger now. Login and "new post" went quickly. The spellchecker has failed four times. I will try once more before just reading it. Make that five. Great. No spell-checker in this editor. And something is whacked about cut-and paste from there, so I can't use Star Office for that. Don't have the time or patience to figure out why. I'll just read the damned thing. Oh! Sixth time's the charm! Well, that's probably all the luck I'm going to have. No preview. Just .. publish ... after ... pasting .. into ... Mozilla's ... editor.
C'mon, Blogger guys! Customers who go through this don't remain customers for long. Please fix this. I want to stay.
3-30-05 - (1) Blogger is quite zippy today. This is quite nice. I hope it lasts! (2) Yes. Blogger is monetarily free. But since the owners either make money from it or hope to, the question becomes, "Why do they go through all the trouble of hosting the service at all?" Because they attract viewers and hence advertisers through the free content we bloggers provide. While we don't pay in money, a trade is going on. So my beef is completely legitimate. (In case anyone out there was starting to wonder whether I was some whining socialist idiot savant who has "writing hard-hitting Objectivist commentary" as his "splinter skill.")
Updates
3-30-05: Corrected a bunch of typos and added two more PS notes.
11 comments:
Who'd've thought that Google would go the way of Microsoft?
"Ah, but little grasshopper, weren't you listening...?"
----
I tried to update my last post with such a musing, but to no avail. I only barely managed to erase 6 or 7 duplicate postings.
I don't know if this comment will appear.
I'm ready to say "F-U Blogger!!!!!"
Here's the deal: why should we have any readers, when they can find updated posts, new posts, new comments, etc., at so many non-Blogger sites?
Who'd've thought that Google would go the way of Microsoft?
"Ah, but little grasshopper, weren't you listening...?"
----
I tried to update my last post with such a musing, but to no avail. I only barely managed to erase 6 or 7 duplicate postings.
I don't know if this comment will appear.
I'm ready to say "F-U Blogger!!!!!"
Here's the deal: why should we have any readers, when they can find updated posts, new posts, new comments, etc., at so many non-Blogger sites?
Who'd've thought that Google would go the way of Microsoft?
"Ah, but little grasshopper, weren't you listening...?"
----
I tried to update my last post with such a musing, but to no avail. I only barely managed to erase 6 or 7 duplicate postings.
I don't know if this comment will appear.
I'm ready to say "F-U Blogger!!!!!"
Here's the deal: why should we have any readers, when they can find updated posts, new posts, new comments, etc., at so many non-Blogger sites?
Who'd've thought that Google would go the way of Microsoft?
"Ah, but little grasshopper, weren't you listening...?"
----
I tried to update my last post with such a musing, but to no avail. I only barely managed to erase 6 or 7 duplicate postings.
I don't know if this comment will appear.
I'm ready to say "F-U Blogger!!!!!"
Here's the deal: why should we have any readers, when they can find updated posts, new posts, new comments, etc., at so many non-Blogger sites?
Who'd've thought that Google would go the way of Microsoft?
"Ah, but little grasshopper, weren't you listening...?"
----
I tried to update my last post with such a musing, but to no avail. I only barely managed to erase 6 or 7 duplicate postings.
I don't know if this comment will appear.
I'm ready to say "F-U Blogger!!!!!"
Here's the deal: why should we have any readers, when they can find updated posts, new posts, new comments, etc., at so many non-Blogger sites?
Who'd've thought that Google would go the way of Microsoft?
"Ah, but little grasshopper, weren't you listening...?"
----
I tried to update my last post with such a musing, but to no avail. I only barely managed to erase 6 or 7 duplicate postings.
I don't know if this comment will appear.
I'm ready to say "F-U Blogger!!!!!"
Here's the deal: why should we have any readers, when they can find updated posts, new posts, new comments, etc., at so many non-Blogger sites?
i'm banging my head to the same tune and tempo as you are apparently. i know that blogger is a freebie, but dayam, it's killing me to see the number of visits to my site, with no comments left behind. i figured it out when trying to comment on another blogger blog, and found that the lack of system response wasn't isolated to the original postings but the responses as well. oh well, they've got a bunch of whiz kids working over there, and they'll get it figured out soon enough, i hope. if not, i'm probably going to follow in the footsteps of those that have left before me, and end up at a new "pay" site, just to make sure my blog gets out and seen. arrrg.
Hmmm. I might be about to post twice, but I see that the other comment isn't up.
(1) I meant the title to be "Burning Bag of Blogger", but I'm too hacked off to fix it now.
(2) Curtis has multiple comments posted, making my point by demonstrating it -- unless some erasures are in a queue somewhere.
(3) Oh, and while I'm on, good to see you here, Bothenook!
(4) And yep, it's free, monetarily, to us, but they do make money from it or see the potential to do so, and it's because of all the free content we're providing. We have every right to gripe.
-- Gus
Hmmm. I might be about to post twice, but I see that the other comment isn't up.
(1) I meant the title to be "Burning Bag of Blogger", but I'm too hacked off to fix it now.
(2) Curtis has multiple comments posted, making my point by demonstrating it -- unless some erasures are in a queue somewhere.
(3) Oh, and while I'm on, good to see you here, Bothenook!
(4) And yep, it's free, monetarily, to us, but they do make money from it or see the potential to do so, and it's because of all the free content we're providing. We have every right to gripe.
-- Gus
I see I'm not alone in my doublespeak...
I'm wondering if my recent update of Firefox—to 1.0.2—exacerbated the problem. I kept getting "the document contains no data," in addition to timeouts. A search at Mozilla suggested I clear out the browser cache, which didn't work, and another search revealed the possibility that my Norton might have been involved. I've turned off my firewall long ago, but it continues to operate in some fashion. Taking the advice from Mozilla, I went into the firewall and changed the settings for Firefox to "permit all." Apparently, the update to the browser had confused Norton. Instantly, I've noticed a change in my access to Blogger: been able to tweak my template twice, with no problems, and this comment page loaded just fine.
Or, perhaps the folks at Blogger have fixed things.
Well, I'm getting ready to hit the "login and publish" button, so wish me luck!
Worked just fine.
Post a Comment