I know that I will get some flack for all of you for this confession but it has gotten in the way of me posting here - and I need to because I love the valuable advice I get. This post is not meant to ruffle feathers it is merely to defend the post and the mission that my husband is going on.
My confession:
Last week (maybe the week before) I posted my questions on how to deal with my first deployment. I gave details of the deployment that in my opinion fell within the appropriate realm of OPSEC - due to the public nature of this specific deployment (BSRF-12). I heard from a few people that they believed that I gave too many details away. In my opinion, I didn't give any details that weren't on (both) the deployments WIKIPEDIA page as well as the PUBLIC FACEBOOK page created for the mission - including how long the mission is and the exact months that the guys are gone. I was upset at the comments because I took a lot of care in writing the post - so I deleted it for fear of upsetting people. I went on to speak with our FRO about my concerns and she replied, "While we understand where you are coming from regarding OpSec and appreciate your vigilance, the Black Sea Rotational Force is a training mission that we openly and enthusiastically want and need to communicate about. We do want to let our friends, allies, and partners know about our growing ties with our friends in the region and the great work we do to increase security and partnership in the region" I will admit that maybe I was posting details that could give someone too close of an idea of when they are leaving and I should take greater care in posting about dates (or months).
I just wanted to get my concerns off my chest because I hadn't even looked at this board since I deleted that post, because I was upset. I appreciate all of you dedicated military spouses being concerned about the OpSec - and I am of course still learning...as this is our first deployment.
I don't mean to ruffle anyone's feathers - and I still value the opinions I have gotten when I have posted here. BSRF-12 is a pretty unique mission and the purpose is to make people aware of the positive things we are hoping to do over there. I don't want to put our men and women in danger by posting details that could get anyone hurt. I appreciate all of the advice - even the advice about OpSec as it gave me cause to look closer at what I wrote (even though at the time I felt that it fell within the appropriate guidelines) and I will be even more conscious about it from now on.
Thank you
Re: I have a confession...and I know I will get some opinions on it..
I think in general people want to be safe, and they want you to be safe. Very few people have knowledge of that particular mission, and so they were unaware that public dissemination is encouraged. That's all you really need to say. ETA: In general, whether it's on a public FB, or in news articles, etc., I am not in charge of information dissemination, so while those who are may choose to put information out, I choose not to. It also can often be a PERSEC issue.
I think you should examine why you're so sensitive to what was said. I don't think anything was said meanly (though I don't remember much about the post), and people were trying to look out for you. Getting that upset shouldn't happen. It's just a message board with mostly well meaning people participating.
The folks on this board are pretty tight about OpSec. And, I'll admit, it is usually important to maintain - it's way too easy to snag information on public boards, so we want to keep it to a minimum. And, frankly, while some commands are very vocal when discussing OpSec to family members, a lot of them don't talk about it much, or a spouse misses that briefing, and they just don't know.
So, we approached your prior post with that thinking. If the FRO is OK with it being discussed on public boards, I'd say this particular mission is an unusual example of that. On the other hand, getting into the practice of watching what you share might not be a bad idea - future missions might not be so public. And, regarding personal security, you might want to be cautious with telling people when you will be home alone - it can make you a target. (I don't always follow this one as well as I should, but it is something I keep in mind.)
I was one of the ones that mentioned OpSec to you in that post. I tried to do it as nicely as possible, so I am sorry if you felt jumped on about it. Dealing with deployments/separations from your spouse are never easy, and having yet one more point of stress about is the last thing you need.
Exactly what Stan said. As a general rule, we encourage everyone to practice good Opsec and Persec at all times. We'd rather err on the side of caution and it's not meant to become a big deal when we point out something that seems like "too much."
A good rule for the mission that you mentioned may be to post only what you feel is necessary in order to raise general awareness about the mission. In other words, start with the least amount and build on that, rather than starting with the most detail and subtracting from that. Hope that helps.
I wasn't on when you posted the original message, but I'm sorry you felt ganged up on. The people here do genuinely care about your safety, as well as the safety of all the people involved in any particular mission. PERSEC and OPSEC really are all about puzzle pieces, and I'm sure you know now that you've had a chance to look further into it, it can be so easy for one seemingly innocent detail to lead to a whole trail of cookie crumbs.
Stick around. We're getting better about not ganging up on people.
A military message board universal is that people are too loose with PERSEC and too overwound with OPSEC. Both generate from a place of ignorance.
Please feel free to say a simple "I told you so!", OP. You're far too polite.
http://community.thenest.com/cs/ks/forums/thread/59917924.aspx
There was also an incident at Offutt AFB in the last few months.
Based on your post count, I see you bring many positive things to the community.
I'm not familiar with the mission that you are talking about and am too lazy to look it up. If someone is giving specific information about a first deployment, you can't fault other wives to think that it's just a newbie error. I think they were just trying to help you learn. With that being said, I really do think you need to read that story about the wife who gave out too much information.
I personally don't post any information relating to my husband's job anywhere on the internet because a very public attack and subsequent attempted attacks at Ft. Hood have made me uneasy about announcing the location of my DH. However, I was unnecessarily scolded by a girl on a wedding website once for posting that DH was at Ft. Hood...which doesn't violate OPSEC and was super annoying. I don't think it's that big of a secret that there are military personnel at Ft. Hood
Photo bomb, yeah!
Nope, WeddingBee.
Photo bomb, yeah!
Yes, the OP should totally be rude to everyone who was just trying to help her out and keep her H safe. Maturity, you do not have it.
Eh, OP I think it's a little ridiculous that you got so upset and offended by strangers on the internet trying to help you be safe. Also, that you would go to the FRG to ask about the mean women on the internet. Even if they want to promote the dates, it doesn't mean you have to actively post them on the internet and message boards. My H is on an an aircraft carrier, and their deployments and homecomings are blasted all over the media for weeks before they leave and come home. It still doesn't mean that I come on message boards or FB and blast about my H leaving or being gone, which then means that I am alone. In general it's much better to be safe than sorry, and I really don't get being so hurt and upset over people trying to nicely talk to you about that.
I do, thank you. As it turns out, quality is not a number, and a community far exceeds a message board.
Of course I do. You, however, have now called me a name, called the OP ridiculous, and have spurned the OP's emotions. Go on with your mature self!