Flight Information and a Warning!

We've had several of our friends ask for our flight information, so I'm posting it below.

But first, for anyone considering taking advantage of our being away from home...  
BE WARNED!  We have two overly protective dogs, a cat with a history of injuring full-grown adults, a whole-house alarm system, a watchful former Marine next-door neighbor, and a house-sitter with a very low tolerance for B.S..  At least two of the aforementioned will be armed!  Think again and live to tell about it, Bub.

Thursday 10 February 2011			Air
Continental Airlines Inc - Flight CO 7655		Status:	Confirmed
OPERATED BY /UNITED EXPRESS/TRANS STATES AIRLINES
Depart:	Washington Dulles Int'l Airport	Airline Ref:	AS2CZP
	Washington, DC, US	Seat:	08A 08B 08C
	8:17 AM	Class:	H-Economy/Coach
		Mileage:	215
Arrive:	Newark Int'l Airport	Travel Time:	1:13
	Newark, NJ, US	Stopovers:	0
	9:30 AM	Aircraft:	ER4
	Terminal A	Meal:

Thursday 10 February 2011			Air
Continental Airlines Inc - Flight CO 0089		Status:	Confirmed
Depart:	Newark Int'l Airport	Airline Ref:	AS2CZP
	Newark, NJ, US	Seat:	43D 43E 43F
	11:50 AM	Class:	H-Economy/Coach
	Terminal C	Mileage:	6817
Arrive:	Beijing Capital Airport	Travel Time:	13:45
	Beijing, CN	Stopovers:	0
	Friday, February 11, 2011
	2:35 PM	Aircraft:	Boeing 777-200/300
	Terminal 3	Meal:	Lunch

Friday 25 February 2011			Air
Continental Airlines Inc - Flight CO 0098		Status:	Confirmed
Depart:	Hong Kong Int'l Airport	Airline Ref:	AS2CZP
	Hong Kong, CN	Seat:	20D 20E 20F
	11:25 AM	Class:	H-Economy/Coach
	Terminal 1	Mileage:	8055
Arrive:	Newark Int'l Airport	Travel Time:	15:20
	Newark, NJ, US	Stopovers:	0
	1:45 PM	Aircraft:	Boeing 777-200/300
	Terminal B	Meal:	Lunch

Friday 25 February 2011			Air
Continental Airlines Inc - Flight CO 3262		Status:	Confirmed
OPERATED BY /COLGAN AIR DBA CONTINENTAL CONNECTION
Depart:	Newark Int'l Airport	Airline Ref:	AS2CZP
	Newark, NJ, US	Seat:	06A 06B 06C
	3:25 PM	Class:	H-Economy/Coach
	Terminal C	Mileage:	215
Arrive:	Washington Dulles Int'l Airport	Travel Time:	1:30
	Washington, DC, US	Stopovers:	0
	4:55 PM	Aircraft:	BOMBARDIER Q400 TURBOPROP-2 ENGINES
		Meal:

To Post, or not to Post... (or TMI?)

So in the course of authoring my very first blog post, it occurred to me that the world of Algore's Amazing Internetz has become a tad more scary over the years; in terms of personal privacy that is.  In layman's English, I was posting the information we have received about our new daughter and it hit me that I might be putting too much personal info online.  Could someone use this information for nefarious purposes?

I know I could get around a lot of my concerns by restricting access to the blog, but I'm trying to intentionally leave it "open".  When we went to get Lucy, our blog was open only to "authorized users" and it meant that some people never got to our blog.  In the years since, many of our technology-phobic friends have gingerly entered the waters of Facebook and other social media.  We want to reach as many of these friends as possible, so restricting access isn't the preferred control method.

Another method of keeping information private is to use code for the individuals mentioned. DH, DW, DD, etc. are used on many blogs.  Heck, even the Secret Service uses code names for the people they protect (despite the fact that the code names are public information about 30 seconds after they're first assigned).  Yet, I don't think I want to require anyone reading this to have to use a decoder ring.  My everyday rantings confuse most everyone as it is.  Using "CB handles" or "call signs" would border on absurd.  And not on the good side of absurd either.

That leaves the old-fashioned approach of just keeping some information private - an almost heretical notion on the Information Superhighway.  Thus the challenge becomes how to share as much information as possible with the world with neither restricting the blog to "members only", nor writing in some weird code language.

For right now, I'm choosing to use first names for my family, but nothing more. I have to presume that you already know a little of who we are, especially if you are taking the time to suffer through my ramblings.  If you need more details, let me know.  I'll post the extra information, if I'm comfortable; otherwise, I'll email you the answers.  If I decide to alter my blog security strategery, I'll let you know in advance so I can start compiling a user list. Hopefully we can avoid that nuisance.