My old Audiovox CDM 9000 and Trail Magic on the AT

I recently saw an article about our mobile phones from the past. It got me to thinking about the mobile phones I have had over the years.

When I graduated from the local Technical College, I decided to reward myself with a mobile phone. Work had me tethered via a pager, but if I ever needed to call into work I would either have to go home or go to a payphone (yes, payphones still sort of existed when I got my first mobile phone).

Here is a link to a PC Mag review

My first cell phone was an Audiovox CDM 9000. It was a candy bar phone. This was before smart phones existed. Steve Jobs had not even talked about the iPhone. Bluetooth wasn’t a thing yet either. So I had this phone, which worked great. It was both digital and analog. So where it could it make digital calls and where it couldn’t it made analog. The funny thing about this phone is that it could receive text messages but could not send them. I do not know why. I never figured out why. But it was such a good phone that I had a car kit installed into my car (a Chevy Impala at the time). My ImpalaIt was a nice car. I love the phone as it seemed to be the only phone among my friends that could actually make a call when we were hiking.

 

 

Warning: This next part is a little graphic, a littleClick To Tweet

In fact, when a group of friends and I hiked a part of the Appalachian Trail in Georgia we happened upon an elderly man at the top of Justus Mountain. This man motioned toward us as we reached the top as if something was wrong. So we went over to inquire. He told us he needed help, he was peeing blood, and that he needed water. So luckily we had just filled up so I offered him some of mine. I then called 911 from the top of the mountain. We had all pulled our phones out and mine was the only one that had gotten enough bars to make a call. So we called the 911 dispatcher and luckily, while we often didn’t on this hike, we actually knew where we were. So I told the dispatcher we were on Justus Mountain and that we had just crossed a forestry road that cross the AT. So Gary and I took the man’s pack and helped him descend down the mountain while the others waited with our stuff at the top of the mountain. This was in April of 2001. Luckily an ambulance was able to make it to our location and carry the man out on a stretcher. I gave the man my address as we were all curious to know what happened afterwards. Months passed and we heard nothing.

Two weeks after September 11 I received a package at the post office. I wasn’t expecting one and being so close to 9/11, I was concerned. But I decided, I am a nobody so why would I get a mysterious package. So I opened up the package and found four jars of homemade strawberry preserves and a letter. The man told me he had hiked a trail in Florida two weeks before his trip on the AT and with the drought that year, he had a hard time finding water and basically wound up drinking out of a mud puddle or two. He felt he must have caught some time of intestinal bug because of it and he spent a week in the hospital from that and dehydration. The preserves were a thank you gift for helping him. I gave the jars out to the others. Though they were scared to try them, again so close to 9/11. So I opened my jar and it was great. Everyone else hopefully tried theirs or else they missed out.

Gary And I On AT

 

Here is a picture from that trip. I am not sure what mountain this was on but it was the same trip.

WordPress, Plugin Updates, and Security

I Love WordPress
Adriano Gasparri CC License 2006

When you care about something, you want to give it proper love and attention. You love your WordPress site, right?

WordPress Security

In this day and age it isn’t a matter of if your site will be hacked, it is a matter of when. So you have to do your best to put the right things in place to protect your site to prevent or minimize the damage. Lately everything and every plugin has suffered from Cross Site Scripting attacks.

Backups are your single best defence to protect your site. Seriously. If something crashes your site or compromises your site, backups are how you can get back up and running the quickest. And you need to back up often. You also need to be able to compare your backups. By observing what files were on your site when it was working fine and what files are there now, you can perhaps spot what if anything has been compromised. Or in the case of something being broke about your site, what broke it.

I have written previously about backups: Backup before going forward (Part 1) and Backup befor going Forward (part2). These just scratch the surface and talk about the free and cheap ways to backup your site. You may also want to look at plugins such as BackupBuddy that will let you backup to your favorite cloud drive and that provide automation of your backups. It costs money but being able to restore your site to working order is a big thing, right?

And WordPress (the self hosted version) has taken a beating as well and many valiant programmers have stepped up to the challenge to be sure it is as safe as possible. Hence 4.1, 4.2, and now 4.2.2 have all come out very quickly even in WordPress update terms. Read that article if you need more details.

So there are two things you have to think about, 1) Do I let WordPress auto-update everytime they release a new version? 2) Do I let my plugins auto-update every time there is a new version? Perhaps you have build your site(s) on an older version of WordPress. It may be time to get current or advise your customers to get current. Sure, some of the updates have broken “features” you have come to know and love. Often WordPress releases new features as a plugin first and then it winds up being part of the core. Again, if you backup often, you can perhaps afford to allow WordPress to auto-update.

Always Backup before moving ForwardClick To Tweet

Next Plugins: You have to decide what is your strategy. Do you have a testing site before you roll in changes to your production site? Or do you perform everything on your “Live” server? The safest approach is perform all changes on your staging/test server first and then once tested, allow these updates on your live/production site. To make life easier, you should back up both your test site and production site before any updates so you won’t lose so much sleep putting it back to working order. Every made that “rut roh” change. You know, the one that happens in the “Oh No Second” Rats, I shouldn’t have done that. You know the last change you made that shouldn’t have but did break your site?

Conversely though, security is important and so many zero day attacks often happen to our favorite WordPress plugins. For my site, this is so important I have installed a plugin to allow auto-update of plugins. I know this comes with a level of risk but I backup often so I don’t have as much fear. The one I am currently using is called “Automatic Plugin Updates”  Automatic Plugin UpdatesI will not say it is the best and it has not been updated in a bit but it works and it works consistently, so that makes me happy. You can also exclude certain plugins so if you know one plugin updating might break something, you can exclude it from auto-updating. It also sends you an update every time it updates something. I am sure there are other plugins that do the same thing and perhaps they are better but the point is, if you are concerned about security to that level, this is a good tool to have in the arsenal.

You should also consider some type of security plugins to protect your site even more. Here is a great article I wrote about what I do to protect my site: My WordPress Security Essentials

What is your strategy to protect your WordPress site?