Drones and privacy–will you allow it, or shoot them down?

There’s quite a bit of talk these days about drones, or unmanned aircraft (UAS).  These have several problems, when you get right down to it.

  1. Noise pollution – it’s annoying enough when Sherrif’s helicopters fly overhead and loiter for awhile, but while a UAS would probably be quieter, it’s still not silent.
  2. Safety – If one of these malfunctions or the remote pilot makes a mistake, they can crash, doing damage to persons and property
  3. Privacy – are you comfortable having cameras over your home or business, watching you and recording what you are doing?  If you are, perhaps Russia would be a better place for you to live.

I am mainly concerned about #3, though the first two certainly are things to think about.  As time go by we (as a nation) are slowly giving up our privacy by allowing our lives to become more public (we post personal stuff on Facebook or Twitter and then wonder how stalkers know about us for example).  Todays youth has grown up with this pervasive social network and doesn’t even give a thought to how their personal privacy is compromised by participating.  It seems it’s only us old farts who grew up before this became prevalent who look at it and say “wow, that’s not good, nope, I’m not doing that”.

Unmanned drones are another thing that is starting to take off (ok, sorry, couldn’t resist that).  If we sit idly by and allow this to happen, then there will be no concept of privacy, even in your own back yard.

One town in Colorado has a proposal drafted by resident Phillip Steel to do something about this, in a very American manner.  According to Steel, “We do not want drones in town.  They fly in town, they get shot down”.  Excellent!

The proposal was to sell $25 hunting licenses, and offered a $100 reward to anyone who shot down a drone “known to be owned or operated by the United States Government”.  Wow, how cool is THAT??

The FAA of course (in their traditional role as spoilsports) takes issue with this, stating “Shooting at an unmanned aircraft could result in criminal or civil liability, just as would firing at a manned airplane”.  They claim that they are responsible for airspace and safety and that a damaged aircraft could crash and hurt somebody or damage property (hmm… kinda like my #2 above even without the gunman, but I’m sure they feel THOSE risks are acceptable).

Personally, I think that if everybody took the attitude that Mr. Steel has, that the FAA would find it difficult or impossible to enforce on a large scale, the government would find that they are spending a LOT of money to replace these expensive planes, and the whole thing would fizzle, much to the delight of privacy loving folks everywhere.

Here’s another entertaining alternative, borrowed from WWII.  The Germans had flying bombs which had no pilot and would fly across the channel, run out of Petrol (it’s England, folks), then crash and explode.  They were quite terrifying as weapons because of their random targets and because you could hear them and knew you were safe… until the engine stopped.  Very Hitchcock-esque from a terror standpoint, but I digress.  The allies came up with a good solution.  They’d fly up next to these things, put a wingtip under their wing and then roll their plane.  This caused the bomb to bank, veer off course, and crash in the channel.  Wouldn’t it be fun to do that with a Drone?  Of course I never would do such a terrible thing, and I would never recommend that anybody else do such a terrible and rebellious act, but it’s fun to think about isn’t it?  I bet there are a number of other fun scenarios that don’t involve something as direct as shooting a drone down.  This could be a fun video game!!

Here’s a short article in AVWEB about this amusing Colorado proposal.

Advertisement

Is it worth the time–a great analysis!

Geeks especially have a propensity toward spending time making a task more efficient and less time consuming.  But how many of us have ever analyzed how often that task needs to be performed in order to make the time and effort spent optimizing it worthwhile?  I haven’t, I sheepishly admit.  Fortunately, xkcd.com came to the rescue!

Is It Worth the Time?

Internet Explorer End Of Life (lifecycle) dates

Usually, Microsoft is pretty good about letting you know about the lifecycle dates on their products.  For some reason, Internet Explorer seems to be the exception to that rule.  If you look at Microsoft’s reference document on Internet Software Lifecycles, you’ll see that they list all the Internet Explorer version dates as “Review Note”, and the note says “For support dates for specific Internet Explorer 6 and operating system versions and their service packs, visit the Lifecycle Supported Service Packs site at http://support.microsoft.com/lifecycle/#tab2.”

Nowhere that I was able to find on Microsoft’s site do they actually list which version shipped with which O/S.  C’mon guys, why does this have to be made so difficult?

After some digging, I’ll save you the effort if you are interested to know.  NOTE: these reflect the last date and O/S for each version, and the final end of support date.  Deployments for prior versions of Windows will hit end of support prior to these dates.

IE6 – XP – April 8 2014 end of extended support

IE7 – Vista – April 11, 2017 end of extended support

IE 8 – Win 7 – January 14 – 2020 end of extended support

IE 9 – Win 7 – January 14 – 2020 end of extended support

UPDATE 10/21/2013:

IE 10 – included with Windows 8 and Windows Server 2012, and available for Windows 7.  It will not be available for Windows 8.1 or Windows Server 2012 R2 – October 2015 end of support.

IE11 – included with Windows 8.1 and Windows Server 2012 R2, and available for Windows 7.  It will not be available for Windows 8 or Windows Server 2012 – Jan 2023 end of support.