I Want to Punch Blogger in the Face Again,
Repeatedly, and This Time with a Cestus
Now, I'm not a violent person, but just as it did a couple of months back — and has frequently since, without me bothering to post about it — Blogger is really priming
my pugilistic pumps.
The closest I can come to acting on this impulse, of course, is ramming my fist into my laptop screen, which beyond giving me a very brief stress release will solve exactly zero problems and could in fact create an extremely big one. I don’t want to buy a new computer.
After believing I'd found a way to work around at least some of the quirks of Blogger's new editing interface — like having a smaller Normal size for the Georgia font than it used to, while Large is still much bigger than the old Normal — by pasting in HTML from old posts as a base for new ones, I went ahead and proclaimed that a new round
of blogging was underway. Ha!
When emending an entry the other day it became evident that simply going in to edit
an extant post, new or old, even before I changed a single thing, gave Blogger license to work its screw-up magic, eliminating line breaks, centering previously right-justified images, and wrapping text around those images oddly for no discernible reason — plus, as I mentioned at the end of that entry after finally correcting it by copying the entire code and pasting it into a new post (just because I figured it was worth a try; "luckily"
I learned to save the HTML of every post to my computer early on as insurance due to posts disappearing), if there's an errant tag in the HTML Blogger won't let me freaking save the post let alone flip over to Compose view without fixing said errant tag despite the fact that there's not necessarily any way to find it, leaving the process essentially frozen. Me trying to right one little typo was an exercise in total frustration that, after I employed the new-post workaround a second time, gave Blogger the last laugh because I had pasted in older code that predated the initial reposting and so the typo was fixed while the earlier change was undone, yet I can't scrap the post and put up a corrected version as a new post now without losing the comments that have since been left.
The irony is that in the past it seemed that whenever I’d announce some kind of hiatus in blogging the posts would start to flow again, whereas more recently if I'm so bold as to advertise my intention to resume activity I have immediate reason to regret doing so. Although scheduling posts in advance worked nicely a month ago, today I'd have no confidence in how they'd turn out upon going live, since the so-called Classic post editor has been yanked for good, while my stated hopes of two months back and just the other day were obviously foolish thinking.
Present efforts suggest that I should expect these problems to continue — right this minute there are random extra line breaks and size changes cropping up in the Preview window that aren't visible here in the Compose window, so to keep them from being as depleting and defeating as possible I'll probably stick to shorter posts with fewer or no graphics until finally abandoning ship. The situation with Blogger is bad enough now that I'd love to switch over to the new host yesterday, but that requires a more stable Internet connection, and I haven't been able to pick up the new gadget that will make that possible.
Clearly, I'm dealing with a cosmos that not only doesn't like me monkeying with my posts after they've been published, which is arguably understandable since perfection-ism isn't the most desirable trait in the blogging realm; it doesn't like me correcting posts at all, or trying to outwit Blogger in any fashion, or even dealing with a Blogger that's consistent in any way outside of maddeningly, consistently inconsistently mess-ing with things out of the blue, which are progressively less understandable unless the message is to stop talking about leaving Blogger and just do it already. I'm as tired of hearing me harp on this topic as you are.