Fandango’s Flashback Friday — September 24th

Wouldn’t you like to expose your newer readers to some of your earlier posts that they might never have seen? Or remind your long term followers of posts that they might not remember? Each Friday I will publish a post I wrote on this exact date in a previous year.

How about you? Why don’t you reach back into your own archives and highlight a post that you wrote on this very date in a previous year? You can repost your Friday Flashback post on your blog and pingback to this post. Or you can just write a comment below with a link to the post you selected.

If you’ve been blogging for less than a year, go ahead and choose a post that you previously published on this day (the 24th) of any month within the past year and link to that post in a comment.

This was originally posted on September 24, 2017.

My Batteries Need Charging


I do almost everything on my iPhone. I barely use my laptop anymore because it’s simply more convenient to use my smart, handheld device than it is to chain myself to my desk and use my laptop. And, honestly, there’s very little that I need to do on my laptop that I can’t do on my iPhone. I’m even writing this post on my iPhone.

I have an iPhone 6, which is about two-and-half years old. That’s about 75 in human years. So it’s old. But it works.

A few days ago I downloaded and installed iOS 11.0 for my iPhone. I did it not because there was anything wrong with iOS 10-dot-whatever that was previously running on my iPhone. It was working just fine.

iOS 11.0 seems to be working just fine, as well. And it does have a handful of new features, one or two of which might even be useful once I discover what they are.

But I’m not writing this post to brag about iOS 11.0. I’m writing this post to warn you about it. If you have an iPhone, and it’s not the latest, greatest iPhone, don’t download and install the new operating system. It consumes your battery life at an astonishing rate.

You know that little battery icon in the upper right corner of your screen? With iOS 11.0, I can literally see the battery draining. Since installing the latest OS, my iPhone’s battery is usually down to about 20% within just a few hours. Previously, the battery lasted most of the day before I had to set it aside for a little while to recharge it.

And, by the way, recharging the battery back to 100% takes longer with iOS 11.0. A lot longer.

I think the problem is that the new OS is designed to run most efficiently on the newest hardware. So I guess there’s only one viable solution to this iOS 11.0 problem.

I am going to pamper myself and purchase a new iPhone X in November when it becomes available. I’m sure that will solve my battery life problems and all will once again be right with the world.

Written for today’s one-word prompt, “pamper.”

Post script September 24, 2012

I was fascinated when I found this post that I wrote exactly four years ago. Shortly after I wrote it, I noticed that my iPhone 6 was running much slower than it had before I upgraded to iOS 11.0. Apparently Apple had decided to intentionally (and without informing anyone) slow down the performance of its older iPhones in order to attempt to extend the batter life after iOS 11.0 started sucking the life out of the iPhones’ batteries.

I did buy a new iPhone in November, but it was an iPhone 8 Plus, not an iPhone X, and that saved me a couple of hundred dollars. I traded in my sluggish iPhone 6 for an iPhone 8 Plus because it was a larger device than my iPhone 6 and I figured that, as a newer device — albeit not the newest device — the battery would last longer, which it did. And, best of all, it was much faster than my older iPhone. Last year, I upgraded to the iPhone 12 Pro Max, an even larger device than my iPhone 8 Plus.

But what is most interesting to me, exactly four years later, is that Apple just introduced iOS 15.0 and I’ve been debating with myself about whether to install the new iOS or to wait for a while. If I learned anything from my experience from four years ago, it’s probably that I should wait. Unfortunately, I tend toward instant gratification, so the idea that this sexy new update to Apple iOS is available is gnawing at my desire to have the latest and greatest of whatever is available. I have a feeling that I’ll be installing iOS 15.0 sooner, rather than later.

Invasion of Privacy

“Some son of a bitch bastard attempted to hack into my laptop last night,” Randy griped. “Fortunately, whoever tried it didn’t have a clue about how to actually pull it off.”

“Yeah,” Tess agreed. “Hacking into computers seems to be the trend these days. It’s an invasion of privacy. The hackers either try to steal your personal data, including your passwords, or they install malware on your computer and then charge a ransom to remove it.”

“I’m lucky that I am using a VPN with a robust firewall that prevented a breach,” Randy said.

“I read that a lot of people are making the transition from laptops to smartphones for most of the tasks that they used to rely on their computers for,” Tess said.

“Are you kidding?” Randy said. “Using a smartphone instead of a computer would be like trying to pull a boat behind a car with twine rather than with a trailer hitch.”

“Not so, Randy,” Tess said. “There is literally nothing using a laptop that I can’t do just as well or better on my smartphone, including blogging by the way.”

Written for these daily prompts: Fandango’s One-Word Challenge (hack), The Daily Spur (clue), Word of the Day Challenge (trend), Ragtag Daily Prompt (breach), MMA Storytime (transition), and Your Daily Word Prompt (twine).

Do You Read Me?

I’m going to assume that if you’re reading these words that you read my blog, at least occasionally. I’m curious, though, how you’re reading my blog.

(I was going to include a poll in this post to ask you how you read my blog, which is something I could do using the old classic editor. But inserting a poll into a post does not seem to be an available block in the block editor. At least not on the iPhone version of the block editor. So I guess I’ll have to ask my questions the old fashioned way.

Do you read my posts…

  • from the WordPress reader?
  • from a laptop or desktop computer?
  • from a tablet?
  • from a smartphone?

The reason I’m asking this question is that I blog from an iPhone using the WordPress iOS app. I always preview my posts before I publish them. And when I preview them, the app gives me the option of previewing the post from a mobile device view, from a tablet view, or from a desktop view.

Because I use my iPhone to read posts, I preview my posts in Mobile view to make sure it looks the way I want it to. But I’ve noticed that if I go to Desktop view, it sometimes looks weird. Sometimes the images aren’t centered in desktop view as they appear to be in mobile view. Or the text, which looks fine when aligned left in the mobile view, seems lost in the desktop view.

And then there’s the reader view, which is pretty much non-formatted — at least via the iPhone app — and looks nothing like what the post looks like when you actually visit the site. I hate the reader view.

So, back to my question. When you read my posts, do you mostly read them from a desktop/laptop, from a tablet, or from a mobile device? Or do you read them via the WordPress reader?

And, for what it’s worth, I read all of your posts from my iPhone in mobile view.

It’s Not as Scary as It Appears to Be

I’m a big enough man to admit when I’m wrong. For the past year I have written a deluge of posts lambasting WordPress’ decision to “decommission” (their word) the reliable, easy to use classic editor and to force us to “embrace” its block (Gutenberg) editor, whether we wanted to or not. And I most certainly did not want to.

As most of you know, I blog from my iPhone. In fact, at this very moment, I am sitting on my couch in my family room, listening to classic rock music, and composing this post.

But I digress. I have vigorously resisted this whole block editor thing for the better part of a year. First, I didn’t see any need for the elimination of the tried and true classic editor. Why, if the developers at WordPress were so thrilled with the new block editor, couldn’t they offer it as a “new and better” option, while continuing to offer the (mostly) beloved classic editor?

Second, the block editor that WordPress first introduced last year was not designed for use on the relatively small screen of mobile device. Maybe it worked well on a laptop, but it was shit on an iPhone. I resented feeling that if I wanted to continue to blog on WordPress, I’d have to do so on a laptop because the block editor was close to impossible to use on an iPhone. I even wrote in response to one of Dr Tanya’s Blogging Insights posts last July, “If the day ever comes when WordPress no longer offers the classic editor, that will be the day I will either find a different platform for my blog or I will just stop blogging.”

Well, that day came for those of us using the iOS app on our iPhones last month, when, as I explained in this post, WordPress removed the classic editor option from its iOS app. And that’s when it was shit or get off the pot time for me.

So I decided that I was going to dedicate myself to figuring out how to blog on my iPhone using the dreaded block editor, as it had become my only option. And it’s now my duty, as a member of this great blogging community, to admit that, in my rants over the past year, I seemed to have been making that proverbial mountain out of a molehill.

The current version of the block editor in the WordPress iOS app is usable. I can pretty much do with it all of what I was able to do with the iOS version of the classic editor. In fact, I can do a few more things with the iOS block editor than I could with the iOS classic editor.

So now I have no excuse to whine and rant about the block editor. No reason to hunt for another blog hosting site to move to. I’ve been able to move forward with the block editor on my iPhone without too much pain.

What I’ve learned is that no matter how dark the corridor ahead appears to be, one shouldn’t be afraid to step into it and see where it leads.

(I hope you appreciate how I managed to fit my FOWC with Fandango daily prompt word, “corridor,” into this post despite the fact that it had no relevance to the rest of this post.)

Written for these daily prompts: Your Daily Word Prompt (deluge), The Daily Spur (duty), Word of the Day Challenge (proverbial), MMA Storytime (mountain), Ragtag Daily Prompt (excuse), and Fandango’s One-Word Challenge (corridor).

TMP — iOS App Changes

Every Monday, Paula Light, with her The Monday Peeve prompt, gives us an opportunity to vent or rant about something that pisses us off. And today I’m really pissed off. As a matter of fact, I’m standing at the precipice of ending my WordPress blog.

As most of you know, I blog using my iPhone and the WordPress iOS app for the iPhone. The block editor on the the iPhone is next to impossible to use because there is just not enough real estate on a relatively small smartphone screen to make it feasible to use. But the good news is that the WordPress iOS app has the option to create and edit our posts using the classic editor.

However, when I went to the App Store app this morning to see what updates were available for all of my apps, I saw that there is an updated version of the iOS app, version 16.9, that is available. And then I read with horror that “The classic editor will soon be unavailable for creating new posts.” WHAT?I have been sticking with WordPress since last August when it “decommissioned” the classic editor and tried to force us to use the block editor. I love blogging and WordPress is the best blog hosting site available, so I wanted to continue to blog on WordPress. Besides, the “wp-admin” site still supported the classic editor for new posts and to edit draft posts. And the iOS app for my iPhone still offered its version of the classic editor option for creating and editing posts.

As of today, if I go to my laptop, I still have the classic editor option  via “wp-admin,” although a number of my fellow bloggers have said that it’s no longer available to them, so it’s probably a matter of time (maybe days if not hours) before I, too, lose it.

But if they’re also taking it away from the iOS app, that’s the last straw for me. I give up. Trying to create posts on the iPhone using the block editor, and even the so-called “classic block” within the block editor on the iPhone is just not worth it anymore.

So if this is the way it’s going to be, I am either leaving WordPress altogether, or I’m going to cut back on blogging considerably. I won’t stop reading and commenting on your posts, but I probably won’t be posting much on my own. I’m sorry, because all of you, the community of bloggers I’ve come to know, are important to me. I consider you to be my friends. But I’m just not going to put myself through this block editor nonsense that WordPress is foisting upon us.

If it does come down to discontinuing my blog, I’ll let you all know.