It looks like you're using an Ad Blocker.
Please white-list or disable AboveTopSecret.com in your ad-blocking tool.
Thank you.
Some features of ATS will be disabled while you continue to use an ad-blocker.
hurdygurdy
HumanPLC
reply to post by TruthxIsxInxThexMist
Yeah Sky News seen to be showing the coverage from Fox News so i assume its live their too.
Im also recording it all because... well as we already know, sometimes stories and accounts can change.
Has anyone noticed that the news broadcasters on Sky (Fox) have already mentioned Syria a few times, they seemed to be saying that due to the naval presence there and the fact it was the Naval Yard targeted this cant be ruled out.
Cant believe they are speculating about something like that with zero evidence.
edit on 16/9/13 by HumanPLC because: (no reason given)
Yes, the media is obviously following a script.
And isn't it odd one of the first posters here sternly warned us not to jump to conclusions but obediently follow the official story...
Why isn't the loss of lives and 1300 missing persons in Colorado at this very moment receiving as much attention?
2 cents.
Explain why they would use a "stock pic" today and call it a shot of the scene at the Navy Yard. Here's the link. Look at the file name.
MyHappyDogShiner
reply to post by Bilk22
That pic looks like a stock pic, nobody seems too worried about getting shot, while that guy is lying there after supposedly being shot. It looks like it's either a stock photo or a photo that wasn't pertinent to the event being discussed, those people don't look too worried just standing around like good little targets and all.
Michael Thacker, a spokesman for Hewlett-Packard, confirmed that Alexis worked for a company called "The Experts," a subcontractor working on an HP Enterprise Services job to refresh networking equipment for the Navy Marine Corps intranet. Thacker could not say whether Alexis was still employed by that company at the time of his death. But investigators were looking into claims that he recently lost that position, which they say may have set him off.
CirqueDeTruth
I'm assuming these screen captures were made today and not yesterday, because I'd expect to see some conspiracy threads made yesterday instead of today regarding said find.
You see - photo manipulation is simply to easy - now a days.
Or - considering the way the alternative news sources slams msm sources, perhaps, it's an intentional blurb/typo indicating yesterday's date - just so the msm in the know can sit back and watch us cook up our conspiratal theories. Get their kicks out ta watching us raise the false flag alarm? Maybe?
Where's the threads from yesterday in conspiracy circles on this mysterious misdating? Hmmmm? Where's the threads from yesterday stating - What shooting at the Navy yard?
CdT
Tucket
X rays? nope. there will be no autopsy...just like the Tsarnov suspect.
sirric
Looks like he was a disgruntle employee.
Michael Thacker, a spokesman for Hewlett-Packard, confirmed that Alexis worked for a company called "The Experts," a subcontractor working on an HP Enterprise Services job to refresh networking equipment for the Navy Marine Corps intranet. Thacker could not say whether Alexis was still employed by that company at the time of his death. But investigators were looking into claims that he recently lost that position, which they say may have set him off.
This is how he gained access, He has a Contractor CAC, it is the universal ID for military base access. It would be accepted to gain access to any part of the base short of Cypher areas. It has a Green stripe to differentiate between DOD/Military and Contractor. He also would have had a DOD Auto sticker since his job was on-board navy bases.
It would be up to "The Experts" to have retrieve his CAC ID if he was let go, But I know personally that many times the person fired would just leave and not turn in the ID.
By the time he made his way to the building, he was free and clear of initial base security.
My Pryers go out the all that are affected.
Sirricedit on 16/9/13 by sirric because: sp
MidnightTide
I maybe wrong, but these articles were written yesterday?
www.kelownadailycourier.ca...
abcnews.go.com...
MidnightTide
I maybe wrong, but these articles were written yesterday?
www.kelownadailycourier.ca...
abcnews.go.com...
NotAnAspie
sirric
Looks like he was a disgruntle employee.
Michael Thacker, a spokesman for Hewlett-Packard, confirmed that Alexis worked for a company called "The Experts," a subcontractor working on an HP Enterprise Services job to refresh networking equipment for the Navy Marine Corps intranet. Thacker could not say whether Alexis was still employed by that company at the time of his death. But investigators were looking into claims that he recently lost that position, which they say may have set him off.
This is how he gained access, He has a Contractor CAC, it is the universal ID for military base access. It would be accepted to gain access to any part of the base short of Cypher areas. It has a Green stripe to differentiate between DOD/Military and Contractor. He also would have had a DOD Auto sticker since his job was on-board navy bases.
It would be up to "The Experts" to have retrieve his CAC ID if he was let go, But I know personally that many times the person fired would just leave and not turn in the ID.
By the time he made his way to the building, he was free and clear of initial base security.
My Pryers go out the all that are affected.
Sirricedit on 16/9/13 by sirric because: sp
And his code or ID should have been disabled in the system and if he arrived, security should have immediately been there to greet him. The CAC should have contained a chip. I would think any ID used there would have a chip or bar code or something that could set off a computer warning that this person was no longer allowed on site... and working for dod contractors myself, I know the FIRST thing they would do is change the code on the door lock and have to go tell everyone there was a new code because they didn't issue personal cards... but they always did that right after they fired someone. Not within a day or two... immediately after the person was escorted out.
flyswatter
NotAnAspie
sirric
Looks like he was a disgruntle employee.
Michael Thacker, a spokesman for Hewlett-Packard, confirmed that Alexis worked for a company called "The Experts," a subcontractor working on an HP Enterprise Services job to refresh networking equipment for the Navy Marine Corps intranet. Thacker could not say whether Alexis was still employed by that company at the time of his death. But investigators were looking into claims that he recently lost that position, which they say may have set him off.
This is how he gained access, He has a Contractor CAC, it is the universal ID for military base access. It would be accepted to gain access to any part of the base short of Cypher areas. It has a Green stripe to differentiate between DOD/Military and Contractor. He also would have had a DOD Auto sticker since his job was on-board navy bases.
It would be up to "The Experts" to have retrieve his CAC ID if he was let go, But I know personally that many times the person fired would just leave and not turn in the ID.
By the time he made his way to the building, he was free and clear of initial base security.
My Pryers go out the all that are affected.
Sirricedit on 16/9/13 by sirric because: sp
And his code or ID should have been disabled in the system and if he arrived, security should have immediately been there to greet him. The CAC should have contained a chip. I would think any ID used there would have a chip or bar code or something that could set off a computer warning that this person was no longer allowed on site... and working for dod contractors myself, I know the FIRST thing they would do is change the code on the door lock and have to go tell everyone there was a new code because they didn't issue personal cards... but they always did that right after they fired someone. Not within a day or two... immediately after the person was escorted out.
Yes, both military and contractor CACs now have embedded chips in them. But one misconception is that these chips are "scanned" in order for you to get on base, but this is not the case. In most cases, when you arrive to the gate at the base, they simply take your CAC, look to make sure it is you, ask you what business you have on base, and let you pass on through. There are times of heightened security when they do random deep dives and car searches, but this is not the norm.
As for not being allowed on site, there wouldnt have been much of a reason for them to look out for him. Unless he was fired for some sort of serious breach of security or gross misconduct, word would not have been put out to all base locations to have them watch for him and stop him at the gate. If they did that every time a contractor gets canned across the country, they would have to increase the number of gateguards tenfold, because most of them would be spending their whole shift just checking lists.
"I wouldn't call him nice, but he seemed harmless, if really awkward," said Demby, the lead writer for NPR's Code Switch blog about race and culture. "He was insecure. He was like a barbershop conspiracy theorist, the kind of guy who believes he's smarter than everyone else. He also was kind of like perpetually aggrieved, but not megalomaniacal or delusional."
NotAnAspie
flyswatter
NotAnAspie
sirric
Looks like he was a disgruntle employee.
Michael Thacker, a spokesman for Hewlett-Packard, confirmed that Alexis worked for a company called "The Experts," a subcontractor working on an HP Enterprise Services job to refresh networking equipment for the Navy Marine Corps intranet. Thacker could not say whether Alexis was still employed by that company at the time of his death. But investigators were looking into claims that he recently lost that position, which they say may have set him off.
This is how he gained access, He has a Contractor CAC, it is the universal ID for military base access. It would be accepted to gain access to any part of the base short of Cypher areas. It has a Green stripe to differentiate between DOD/Military and Contractor. He also would have had a DOD Auto sticker since his job was on-board navy bases.
It would be up to "The Experts" to have retrieve his CAC ID if he was let go, But I know personally that many times the person fired would just leave and not turn in the ID.
By the time he made his way to the building, he was free and clear of initial base security.
My Pryers go out the all that are affected.
Sirricedit on 16/9/13 by sirric because: sp
And his code or ID should have been disabled in the system and if he arrived, security should have immediately been there to greet him. The CAC should have contained a chip. I would think any ID used there would have a chip or bar code or something that could set off a computer warning that this person was no longer allowed on site... and working for dod contractors myself, I know the FIRST thing they would do is change the code on the door lock and have to go tell everyone there was a new code because they didn't issue personal cards... but they always did that right after they fired someone. Not within a day or two... immediately after the person was escorted out.
Yes, both military and contractor CACs now have embedded chips in them. But one misconception is that these chips are "scanned" in order for you to get on base, but this is not the case. In most cases, when you arrive to the gate at the base, they simply take your CAC, look to make sure it is you, ask you what business you have on base, and let you pass on through. There are times of heightened security when they do random deep dives and car searches, but this is not the norm.
As for not being allowed on site, there wouldnt have been much of a reason for them to look out for him. Unless he was fired for some sort of serious breach of security or gross misconduct, word would not have been put out to all base locations to have them watch for him and stop him at the gate. If they did that every time a contractor gets canned across the country, they would have to increase the number of gateguards tenfold, because most of them would be spending their whole shift just checking lists.
If all they do is glance at the card, then they are a complete waste. They don't add security in that case, they take security away by giving the card holder a pass... and they have chips in them for nothing if they don't use them.
As for serious breach... in any place I've ever, ever, EVER worked in... if somebody gets fired, it is understood they are going to be pissed off...and security always looks out for them to come back. They escort them all the way out... they don't just let them leave. They may not always look for that person to come back angry, but especially right after it happens the person didn't have to do anything wrong. They just know they are going to be pissed.
As for the articles... the 2nd one in midnight tdes post said it was created on the 15th, but modified on the 16th. They could have made the page ready for a breaking news article, but they are not supposed to have the wrong date on them. So it could be explainable...although the excuse is a shoddy one unless they are just trying to make the gun toters paranoid...and I am still totally leaning on this possibility because of the other elements of this ordeal.
However, I think it is very strange that even if they had the page ready for an article on the 15th and neglected to change the date that the source code says it was last modified on the 16th at 8:49. This would have given them 29 minutes to find out all the info in that article and report it to the press and have them write the article and publish it... 29 minutes from the first shot fired. I find that kind of remarkable.
This report was made by a defence official who wanted to remain anonymous.
Why is this persons very first thought "hurry up and call the press"...???
Anyway... I'm certainly no expert. I just looked at the code and saw that it had a last modified time on it but I have no idea why their system would not automatically update the date to show the date the publish it on their servers. No idea what so ever. I would think they would have some kind of automatic check on that but perhaps not.
I tend to think someone is jerking our chain and they want us to think it is a conspiracy... and it I think it IS a conspiracy, just not the kind of conspiracy they want us to think it is.
That's the ONLY motive I can come up with.
The guy may have been pissed about something, but I think he was set up like a domino if this did in fact occur.