Gunner's Blog

 
Armed Forces News Service

We Support Our Troops!

US Army * US Navy * US Marine Corps * US Coast Guard * US Air Force

News from Our Servicemembers
 
In the Air, On the Front or With the Fleet.

* * AFNS * *
Publishing News About Our Servicemembers since 2003

In the Air
On the Ground
With the Fleet
Please Support Our Troops
US Army      US Navy      US Marine Corps      US Coast Guard      US Air Force 

Main Menu:
Home ] [ Email Troops ] [ Blue Star Families ] [ Video Streaming News Links ] [ Photos Photos ] [ Art ] [ Links ] [ About Us ] [ Link to Us ] [ Privacy ] [ FAQ ] [ Email Bag ] [ Pictures From The Pentagon ] [ Military Humor ] [ Gunner's Blog ]

Military News Feeds by FeedDirect:
Iraq ] [ Mideast ] [ War-on-Terrorism ] [ Breaking Headlines ] [ US Air Force ] [ US Army ] [ US Coast Guard ] [ US Marine Corps ] [ US Navy ] [ National Guard ] [ US DoD ]

Military News Feed by Google Alerts:
Iraq ] [ Mideast ] [ War-on-Terrorism ] [ Breaking Headlines ] [ US Air Force ] [ US Army ] [ US Coast Guard ] [ US Marine Corps ] [ US Navy ] [ National Guard ] [ US DoD ]

Hometown News Releases - News about our Soldiers, Sailors, Marines, Airmen, and Coast Guardsmen - By Abbreviation of State of Residence:
AK ] [ AL ] [ AR ] [ AS ] [ AZ ] [ CA ] [ CO ] [ CT ] [ DC ] [ DE ] [ FL ] [ FM ] [ GA ] [ GU ] [ HI ] [ IA ] [ ID ] [ IL ] [ IN ] [ KS ] [ KY ] [ LA ] [ MA ] [ MD ] [ ME ] [ MH ] [ MI ] [ MN ] [ MO ] [ MP ] [ MS ] [ MT ] [ NC ] [ ND ] [ NE ] [ NH ] [ NJ ] [ NM ] [ NV ] [ NY ] [ OH ] [ OK ] [ OR ] [ PA ] [ PR ] [ PW ] [ RI ] [ SC ] [ SD ] [ TN ] [ TX ] [ UT ] [ VA ] [ VI ] [ VT ] [ WA ] [ WI ] [ WV ] [ WY ] [ APO-FPO ] [ Site Map ]

Both US Armed Forces News Service (USAFNS) and Web Independent News Service, L.L.C. are independent organizations, and are not part of, nor endorsed by, any agency of the United States government.
Best viewed with Internet Explorer, Version 4 or later. 1x1.gif
Recommend this page to a friend
Google Custom Search Searches USAFNS.com

users online.
 


Friday, September 30, 2005

 

CHINFO/FHTNC/USAFNS Debacle - #7 My Response to CHINFO's Second Unreasonable Request

I made a decision to shorten up the installments by compressing several events into one email.  I realized that with Katrina and the FOIA requests, the series was getting pretty long. So, I am trying to finish up the story with this installment and one other.

On Wednesday, 11 June 2003, I responded to the request that I delete all of the FHTNC releases on USAFNS.com and cease to publish them, I responded.  My response used arguments that have been included in earlier installments,  and ended with: 

Based upon the above, I respectfully decline your request to close down my website.  

Sincerely,

 

Charles F. Mitchell

webmaster@usafns.com 

252-633-0161

Mr. Goldstein answered with:

 Mr. Mitchell,

 

Thank you for responding to my e-mail.   I will forward it on to my boss, the Chief of Information, to apprise him of your position.

 

Sincerely,

 

Alan P. Goldstein
Assistant Chief of Information
 for Technology Integration
Navy Office of Information
Washington, D.C.  20350-1200

A Few minutes later, I received the following email from RAdm. Stephen R. Pietropaoli:

Mr. Mitchell -

 

 

While I understand your arguments and do not for a second question your intent, in my view the potential risk of this aggregated information outweighs the benefits.  Accordingly we will adjust our distribution to mitigate that risk.

 

Very respectfully,

SRP

The following day, 12 June 2003, I responded with:

Admiral Pietropaoli:

 

While your email neither requested nor directed me to remove the

releases from my website, I have removed all those releases from my

website that have been on the website more than 45 days.  This resulted

in the removal of 28,547 releases.  This leaves a total of  23,820

releases on the website.  A reduction in the number of emails should

reduce the risks.  I have left the life span parameter set to 45 days.

 

It is requested that you have your staff review the website, and

determine if the risks still outweigh the benefits. If so, please

advise, and I will remove another 15 days, or remove all of them.

 

In addition, I request a meeting with you and or your staff in a

co-operative effort to find a solution that will be mutually beneficial.

 

I don't see a problem, I see an opportunity!!

 

Very Respectfully,

Charles Mitchell

webmaster@usafns.com

252-633-0161

As of this writing, I still haven't had a response. So on 25 June 2003, I sent the following email:
 

Admiral Pietropaoli:

 

Since your decision to stop distribution from FHTNC to my website, I

have overhauled my websites privacy policy and audit trail.  This was

done with the end view of being able to provide competent authority with

the information that my website records for all releases.  This includes

all of the information listed on the privacy page of my website:

 

    http://www.usafns.com/privacy.htm

 

Specifically, this information includes:

 

  • Visitor domain name.
  • Visitor IP address
  • The type of browser and operating system  the visitor uses to

        access the site.

  • The date and time visitor accesses the site.
  • The Internet address or URL of the Web site from which visitor

        accessed this site.

  • The web pages visited on the site.

 

Upon request, I will provide all of the information for all visitors

that viewed a specific release.  The only information that I  need is

the individuals name (First, MI, Last), and from-to dates.

 

In view of the above and the reduction of release life time to 45 days,

it is requested that the distribution from FHTNC to USAFNS be restored.

 

Very Respectfully,

 

Charles Mitchell

webmaster@usafns.com

252-633-0161

I still haven't received a reply to that email either.  So, it is readily apparent that CHINFO isn't interested in recommendations that a member of the public might make.  I suppose that the good Admiral is surrounded by staff and contractors that always provide him with perfect recommendations and guidance that cannot possibly be improved upon. I must have taken leave of my senses when I penned:

In addition, I request a meeting with you and or your staff in a

co-operative effort to find a solution that will be mutually beneficial.

~G:  Stay Tuned - Next installment will include recommendations that I have been trying to get before CHINFO's eyes since 25 June 2003.  You should know that most correspondence directed to Admirals' is opened and filtered by staff members.  Email has come about since I left active duty,  and I cannot say for sure how it is handled, but I would wager that it is handled the same as US Mail was handled for decades before the invention of the Internet and email.


Comments:
Once information is released by the government or branches of the armed forces it becomes public domain. I would think posting carrier locations in oceans and seas would not be allowed while were at war, but it’s available. The armed forces can however deny access to on going operations, troop movements, etc. but once they post it, it belongs to anyone who wants to share it, i.e., media, you and me.

It would seem to me that publishing the current locations of US Aircraft Carriers within a mater a week or day would be more sensitive then what you’re doing, that is posting or linking past and current released US Navy and Marine Corps information.

To release information and then tell people to read it and throw it away afterwards without actually stating it, is the same thing the Navy is telling you.

http://eqneedf.blogspot.com
 
If it’s the compilation that is feared, well don’t release it because there will always be us compilers.

http://eqneedf.blogspot.com

I invite your attention to an article posted in the San Diego Community Forum:

http://community.fox6.com/forums/thread/654650.aspx

www.uscarrierhistory.com
 
Post a Comment

<< Home


Who links to me?

This page is powered by Blogger. Isn't yours?


 Prev | List | Random | Next
   Join - Powered by RingSurf!

© 2004-2005 Web Independent News Service, L.L.C. All Rights Reserved.