Bulk-Deleting Facebook Data

I’ve finally found a solution that works.

Years ago, I decided I wanted less personal data on Facebook. I figured I’d delete posts from past years, so only posts from the past year or so would remain. I’d do this regularly, at least once a year, to get rid of the old stuff. At least that was the plan.

Discovering that there was no built-in bulk delete feature really put a damper on my plans. You see, on Facebook, if you want to delete you posted or “unlike” something you “liked,” you had to make three clicks for each item. Click a menu, click an option, click a confirmation button. The folks at Facebook obviously did that to make removing old content as difficult and tedious as possible so the average person just wouldn’t do it.

Not being “average,” I’d periodically delete about a month’s worth of stuff. But then even I succumbed to the futility of it all. I figured that the best way to minimize stuff on Facebook was to post less there — which is what I do now. (I basically just share links to my blog posts.)

I tried other solutions I’d found via Google. None of them worked reliably.

Until yesterday. I found a Chrome extension called Social Post Book Manager. It looked so promising, I downloaded Chrome just so I could install and try it.

It isn’t sleek or fast, but it is functional. Here’s how it works.

Start by logging in and going to the Activity Log for your account. Use the filter options on the left side of the page to display just the type of thing you want to delete. For example, if you want to unlike everything you’ve liked, click Likes. Facebook displays only the items that meet the criteria you specified in the filter.

Now go up to the URL bar in the Chrome browser. You’ll see a tiny blue and red icon there. Click it to display Social Post Book Manager’s options.

Social Post Book Manager

Set the options as desired. This enables you to filter by year, month, and search word or phrase. If you’re brave, turn off the check box so you don’t review the changes before they’re made. (I’m a coward and left it turned on for the first few times I used it, but it really slows things down.) Then click the appropriate button at the bottom of the box and stand back.

The longer the period you’re working with, the longer it takes to do the job. I first deleted posts that included the word “twittering” from 2007; those were automatically posted by an app that took Twitter content and posted it to Facebook. The search took about 10 minutes. When I clicked the confirm button, it took another 10 minutes for those to be deleted. Deleting all Likes from 2012 took considerably longer. Like hours.

While the extension is running, you basically have to leave it alone. The screen will flash with a dialog box that disappears before you can click anything. Do something else — but not on Facebook. You must keep that page open without changes while the extension works.

When it’s done, the items it found are permanently gone.

Using it for the past few days has taught me that the extension works best when set to slower speeds. When left at the default speed, it often misses many items. So it’s necessary to redo a period over and over to get it all removed. But no matter how long it takes, it’s a lot quicker than manually deleting or unliking content. Best of all, you can set it up to do a long period of time and then leave it while you do other things. I think of it as a multitasking partner.

And the one thing I’ve learned from this experience: I’ve shared and liked way too much crap on Facebook. Seriously. What was I thinking?

Tired of having Facebook share your life and preferences with the world? Give this a try and get some of that data off Facebook.

The Joys of Having an Expired SSL Certificate

A frustrating waste of time.

A few months ago, when it became clear that the Republican led congress was going to allow ISPs to sell our browsing history to the highest bidders, I got a bit more concerned about security. In my research, I came across an article that recommended that users never visit a website without an SSL certificate.

If you don’t know how to tell whether a site has an SSL certificate, the easiest way is to look at the full URL. If it starts with https:// instead of http:// it has an SSL certificate. Think of that extra character, the s, as standing for secure.

Also, some web browsers display a special icon — such as a lock — near the URL or possibly in the status bar at the bottom of the page.

One thing is for sure: You should only enter personal data in pages that are SSL-protected. So if you don’t know how to check for a secure page in your browser, learn.

Of course, at the time, this blog did not have an SSL certificate. I’d done some research in the past and decided it wasn’t worth the cost. After all, although I do get a few donations — thank you generous supporters! — it isn’t as if this site earns any money for me. Hosting costs enough money; buying a certificate wasn’t in the budget.

Still that article made me wonder if I were losing visitors because I didn’t have that certificate. So I did some more research and discovered that my WordPress host, Bluehost, offered a free SSL certificate for subscribers. I made a few calls, clicked a few links, installed a WordPress plugin, and voila! I had a coveted https:// URL.

And then I pretty much forgot about it. After all, typing in the old URL (without the s) still pointed people to the new one. And who types in the whole thing anyway? If you put in any combination of URLs to get to this site — or if you clicked a link that took you here — some sort of behind-the-scenes magic put you on a secure page.

Yesterday changed that. I went to check the site and was faced with the following message:

Page is Not Secure

WTF?

Of course, I discovered this about 30 minutes before a friend was due to arrive to detail my helicopter and I had about a half dozen other things I wanted/needed to do before he arrived — like get dressed? (It was 5:30 AM.) So I did the easy thing: I called Bluehost and asked them what the hell was going on.

The support guy I got was very fond of the hold button. I don’t know if it’s because he really needed help or if he was working on more than one call at a time. I was on hold for most of the 45 minutes our call lasted. While I waited, my friend came, I greeted him in my pajamas, I made him coffee, and I put a bowl of cherries in front of him, occasionally interrupting our conversation to speak with the Bluehost support guy when he came back on the phone.

My big concern was this: people would be scared away by that message. They’d click a link, get to my site, and leave, thinking they’d get a virus or something. I needed the problem resolved quickly.

I was told that Comodo, the organization that provided the SSL certificates, had sent me some sort of verification email that I needed to click a link in. I told him I’d never gotten a message, although it could have been sorted into spam and automatically deleted. He asked me to check a specific email address. I told him I didn’t have that email address. “Well, that’s where the message was sent.”

This made no sense. It was not the email address I had on file with Bluehost. It was an email address on my domain that I had never set up. I checked and verified that it didn’t exist. Comodo had sent an email message to an address that I’d never created or used.

Seriously: WTF?

Mr Hold Button told me to create the address, which I did while he waited. Then, after putting me on hold for a while longer, he told me they’d send a new message and that I should follow the instruction in it.

By this time, I was tired of dealing with the problem. I needed to get dressed. I needed to pull the helicopter out so my friend could get started on it. I needed to do the other things I needed to do. So I told him I’d check in a while and hung up.

And then I forgot about it.

You see, I have a life and that life does not revolve around dealing with computer issues. That was my old life. My new life is far more interesting.

Besides, I had no intention of adding that new email address to any of my email clients on any of my devices. That meant I had to sit at a computer and go to the Webmail feature on Bluehost to check the message. Not exactly something I’m likely to remember.

But I got reminded again this morning when it still didn’t work right. One of my readers emailed me. I also noticed when I attempted to approve two comments.

I checked that stupid email inbox. Empty.

I got on the phone with Bluehost.

This time I got a guy who didn’t like touching the hold button. He stuck with me while we worked through the problem. There was a lot of silent time. He was texting with Comodo. I was starting to write this blog post. Occasionally, he would update me. Occasionally I’d whine to him about how ridiculous the whole thing was. He was suitably sympathetic. I was as apologetic as I could be. After all, it wasn’t his fault.

In the end, the email message finally came. I clicked the link — but not after lecturing him about how we’re not supposed to click links in email messages. I entered the secret code. He confirmed some stuff on his end. I snacked on some cherries. When he said, “Try now,” I did.

The problem was fixed. It had taken 22 minutes.

We wished each other a nice day. When I got the survey at the end of the call, I gave him a good score.

So it looks like this site is secure again — at least until the next time Comodo decides it needs to verify me.

And yes, this did impact site traffic. I had less than half my usual visitors yesterday and started today at about one quarter the traffic I should have had by noon.

Another Waste of Taxpayer Money

I knew the FAA was slow, but this is ridiculous.

I’m terrible about opening my mail. I routinely fetch it from my mailbox (which is two miles from my home) and leave it on the dashboard of whatever vehicle I’m driving. Or toss it behind the seat. Or bring it inside, but leave it in my “inbox” pile. No matter where it enters my life, it sits there for a long time. Truth be told, there’s a six-month period in early 2014 when I just stuffed it all in a box and lost it in my garage. (I honestly think there’s a black hole in there.)

This time of year, when I’m actually expecting checks, I pay a little closer attention to what comes in the mail. That’s why I noticed the letter from the FAA and opened it within two weeks of receipt. (Heck, I knew the FAA wasn’t sending a check, so why rush?)

Inside was the letter dated 5/19/2017 that you can see below.

FAA Letter
So the FAA basically waited 17 years to give me an opportunity to opt out of releasing my address to the public.

It basically says that back on April 5, 2000 (not a typo), Congress and the President — Bush 43, I guess — enacted a law that required the FAA to make pilot addresses available to the public. Fortunately, I can opt-out of this invasion of my privacy by signing the letter and sending it back to the FAA.

But I have to hurry! Even though it took them 17 years to send me this letter, I only have 90 days to respond.

Can you believe this crap?

My first thought was what a waste of taxpayer money this is. Wikipedia reports that there were 590,039 certificated pilots in the United States as of 2015 year-end. That means the FAA had to print and mail 590,039 letters just like the one I got.

Maybe that’s why it took so long? Maybe they just got up to the Ls?

So the FAA has blown through 1181 reams of paper and a similar number of boxes of envelopes. Even if they got bulk rate on mailing all those envelopes, they’ve still spent well over $100,000 on postage. Somebody had to handle the mailing — even if a machine stuffed the envelopes, someone still had to tend to that machine and get them to the post office. How many trips to the Post Office is that? Do they have trucks standing by for mass mailings like this?

So how much money have they pissed away on this so far? A quarter million? More?

And then there’s the processing. I’m not going to the website. I’m going to sign the letter and mail it back. There’s got to be some poor slob in Oklahoma City who’s sitting at a desk just waiting for envelopes with signed letters to come in. He or she has to look up each one in the system and toggle a check box to say we want our addresses kept private. And then what? Do they actually file all that paper? Stick it in filing cabinets? How many filing cabinets do they have? How many rooms does that fill? Do they have buildings filled with filing cabinets of paper?

Paper!

And for what? What gives Congress and the President the right to decide that the public is entitled to the addresses of certificated pilots? What is the benefit of such a rule? Why would they even do this?

And who the hell wouldn’t opt out?

This is stupid from start to end. it’s wallpapered with stupid.

But that’s our tax dollars at work. Imagine how many educational programs the cost of this mailing would have funded. How many Meals on Wheels dinners. How many airport improvements, for Pete’s sake.

Why are the people in Washington so damn stupid with our money?