posted on Jun, 2 2013 @ 10:19 AM
reply to post by misschareesee
Legally they can haul you in the rest of your life for a breach of your security oaths. And when it comes to crypto etc. communications [I know from
my Navy job], they can be seriously to extremely fussy and petulant or worse.
It's not worth it. The benefit to the UFO community and public is miniscule to nonexistent.
At best you have only a microscopic part of the picture. And likely that part has been discussed publicly before from other sources.
All it would take would be for some watcher to be annoyed by such leaks and seek to make you an example.
And it might not have anything to do with the UFO type stuff. They could say to themselves that "IF SHE'D SHARE THAT--she might eventually share
XYZ . . . " that was on other msg traffic in your spaces whether you saw it specifically or not. So they might hassle you pre-emptively about some
other document that you'd been around--perhaps not even knowing it.
BTW, "they" have monitored with literally acres of computers EVERY electricity based comm circuit 24/7/365. There has been no privacy of any
significance for a long time.
It might be somewhat safer--MIGHT BE--for you to give your personal opinions as to what is going on with UFO sightings etc. but I wouldn't get
specific in any way related to highly classified msg traffic that you saw.
The fact that they already hauled you in is telling. You'd be wise to take that as more than an enormous hint.
For them to do that and then you post stuff on a thread like this COULD really anger some watchers and trigger a big slap-down of you as an example. I
don't care if the probabilities are only 5-25% likely--it's not worth the risk.
You have the rest of your life to live and loved ones . . . no need for such traumas to add to the traumas of daily life in our era.
I appreciate your courage and desire for information to be out. Leave it to folks who are better able to weather the storms.
edit on 2/6/2013 by BO XIAN because: addition
edit on 2/6/2013 by BO XIAN because: tag fix