TMP — Being Seen

Every Monday, Paula Light, with her The Monday Peeve prompt, gives us an opportunity to vent or rant about something that pisses us off.

It should come as no surprise to anyone who has perused my blog over the past four months that my rant today is about WordPress. On November 3rd last year, I wrote a post, “Another WordPress Bug,” in which I pissed and moaned about how WordPress had released an update to its iOS app for the iPhone. That release, version 16.0, had a bug in it.

When I went to my reader and then click to visit posts, I could no longer “like” certain posts. And if I tried to comment on those posts, it didn’t recognize that I was logged onto the app and it asked me to enter my name, email address, and blog URL. And sometimes, even when I did that, I still was unable to leave a comment. I’d never had to do any of that before from within the WordPress app on my iPhone.

Of course I’ve exchanged dozens of emails with the WordPress Happiness Engineers, who have assured me that they’re working on a fix. Almost four months have elapsed since that release and every time WordPress issues a new release, I get my hopes up that the bug will have been fixed.WordPress just released version 16.7 and, once again, my hopes have been dashed. The annoying, frustrating bug persists. But one of the “enhancements” introduced in version 16.7 is described as this…

We continue to improve the experience in your Reader, and you can now mark posts as “seen” as well as view your total of “unseen” posts.

Okay, what does that mean? Why would I want to mark posts as “seen”? Does that send a notification that to the blogger who wrote the post that I’ve seen it? Here’s an example of what it looks like:I can also mark a post I’ve seen as “unseen.”So much for the old saying that once you’ve seen something you can’t un-see it.

I’m hoping that someone out there can explain to me what the purpose of marking a post as “seen” or “unseen” could possibly be.

And I’m going to contact the Happiness Engineers and link to this post and ask them if they can explain how this new “feature” improves the Reader experience, and, more important, why they’re focusing their efforts on seemingly unnecessary features and not on fixing that goddam bug!

Hurry Up and Wait

I was excited the other day when I saw that WordPress had pushed out an update to its iOS app for the iPhone. I was sure that version 16.1.1 had a fix to the Reader issue that by now you are no doubt tired of hearing me whine about.

After it installed on my iPhone, I opened the app, went to my Reader, and clicked “Visit” on a post that I had been unable to like or comment on after the previous update. Unfortunately, even with this new update, I was still unable to like or comment. Bummer.

So I sent a message to the happiness engineers.

I was disappointed yesterday, after installing version 16.1.1 of the WordPress app for iOS, that the issue with the WordPress Reader that surfaced when version 16.0 was installed, and for which I’ve been exchanging messages with various happiness engineers since November 3rd, is still unresolved. I hope your team will be releasing a fix for this issue in short order.

The response I got essentially reminded me that Rome wasn’t built in a day. Here’s the answer I received:

We understand this is frustrating. But even with high priority issues, it does not mean the fix will be released in the next update. Some things take longer to fix than others. We don’t have an ETA on this one yet, but our developers are working on it. We appreciate your patience and apologize for the inconvenience.

So I guess I’m in a hurry up and wait mode and the happiness engineers at WordPress will be taking their sweet time getting around to fixing the issue. As the old song says, they’ll be coming ’round the mountain when they come.