SocraticGadfly: Beltway stenos
Showing posts with label Beltway stenos. Show all posts
Showing posts with label Beltway stenos. Show all posts

October 21, 2024

Biden OKs new Israel attack on Iran; MSM, others complicit

Per the second half of the header, I want to expand on a restack note I did about Ken Klippenstein's piece last Saturday about the first half of the header.

First, the meat, which gets at both halves of the header:

Two Top Secret documents outlining Israel’s preparations for a large-scale attack on Iran – which would be Israel’s largest, and here’s what’s most interesting: the mainstream media is silent. Colleagues at some of the biggest media outlets, from The New York Times to NBC, tell me that their outlets are aware of the documents. But it’s been days and no one in the sanctioned elite press is reporting on them (Axios only just reported their existence but declined to publish the documents themselves). As with the J.D. Vance Dossier, which the entire media knew about but refused to publish, it appears the media has once again lost its nerve – and its sense of what’s news.
The mainstream media has generally decided that it won’t publish classified material, in effect deputizing themselves as enforcers of the national security state’s secrecy regime. They did this last year with highly classified Ukraine documents they refused to publish (which my editor published at Newsweek).
To put it bluntly, major media are petrified of running afoul of the national security state. And not without reason. My decision to publish the Vance Dossier got me thrown off X (Twitter) and links to the story were blocked on the platform along with Meta’s Facebook, Instagram and even Google Docs. Let’s see if that happens again here.

There you go.

First, the second half.

Although Ken didn't use the word "cowed," I did in my note. I think that's a fair inference of his implication, as he DID use the word "petrified."

(And, so far, neither he nor I appear to be thrown off Twitter.)

Rather, as noted in the second half of the header, "complicit" is the word.

This is different than the Vance dossier. This is Israel, and the mainstream media run that up the flagpole and salute that, period and end of story.

It may be in part fears about the national security state/deep state, but I think that's secondary, and even the secondary falls into two parts.

The bigger of those two parts is fear of loss of access. The "elite press," as Ken calls them, is also the "inside the Beltway" media, as Ken knows. Or "access journalism," as Ken also knows.

Within that, the stenos of the Nat-Sec Nutsacks™ Fighting 101st Keyboarders (thanks, Atrios), definitely don't want to lose access to insider intelligence sources. It's like a domestic version of being embedded.

Now, the leaks themselves.

As Ken knows, DC is a one-industry town, and the coin of the realm / grease that oils the machines, after money itself, is leaks.

From the White House and executive branch, leaks are almost always deliberate with political purpose.

(Genocide Joe now says he is "deeply concerned" about this, and his Nat-Sec Nutsacks™ spox John Kirby says the Waffle House doesn't know whether it was a hack or a leak. Sure you don't. That said, the Beeb says it explicitly mentioned Israel's nukes. But, that's a head fake to think that makes it a hack, not a leak. Could it be forged? Different question, but still highly doubtful.)

So, what IS that purpose?

One, per the "complicit," is to test just how complicit the MSM is. Now we have an update on that.

Two and related, is to prep the stenos for when the attack might actually happen and know what to ask.

Three? A pseudo-shot across Bibi's bow. As Ken notes, we spy on Israel. This lets them know what we know. But, per the oath for trial witnesses about the truth, the whole truth and nothing but the truth, it surely does NOT tell ALL that we know. And, it may not have only truth in there, as far as the "nothing but," either.

As a pseudo-shot, in other words, this is another of those red lines that Genocide Joe continues to lay down on Israel for US public consumption that he has no intention of enforcing. This also is in the context of the presidential election, with early voting underway in many states. It's another way, via Genocide Joe, for Kamala is a Zionist Cop to look tough as well, even as she continues moving her own Overton Window right. Darth Cheney and the kiddies and sellout adults at Voters of Tomorrow who have Lincoln Project connections surely approve.

Three, part 2? Let's not forget, as many people know, and as Ken put in a previous post, but didn't link to in this one, that Merikkka just put a THAAD battery in Israel — with a US crew to run it to boot. That basically says "Do what you want to, Bibi, I got your back." That said, both that THAAD and the Iron Dome must suck if a Hezbollah drone was able to target Bibi's house.

Four? Ken calls out the Beltway stenos again in a new piece. Here's a key takeaway:

“Covert UAV operations” were observed on October 15, the NGA says, indicating that Israel’s RA-01 stealth drone was initiating a flight or returning from one, likely over Iran. Israel is flying stealth (covert) drones over Iran? That’s a story in itself. This would be a capability similar to the U.S. RQ-170/180 drones, which are super secret and barely ever mentioned in the U.S. media. But they are known to operate out of Chabelley airfield in Djibouti. Are they overflying Israel to take a look and thwart its “concealment” methods?

Complicit indeed is the MSM for not reporting this.

Ken also notes how part of US spying ON Israel is informed BY Israeli intelligence.

With that all in mind? And, the explicit mention of "nuclear"? We're now at the point of discussing what type of leak this is, as in, "political" or "principled"? (That said, principled leaks still have political angles.)

These docs showing up on an Iranian Telegram channel could be seen as supporting the "principled" angle, if the leaker is deeply serious about making sure all the Middle East players know. And, the "nuclear" is probably part of what pisses Biden off. The US now knows that Israel, and the rest of the world, knows that, behind closed doors at least, we openly discuss that Israel has nukes.

And, with all this? Any idea that a Harris administration could restart some sort of 2015 non-proliferation deal with Iran is toast.

December 29, 2018

Top blog posting of 2018 —
A year heavy on refuting conspiracy theories

Below are a few of my top 10, by volume, blog posts of 2018, with a bit of summary and a final wrap at the end.

They're all at least somewhat related to conspiracy thinking, which bloomed in profusion this year, as much as rapid-response tweeting on various issues from President Trump.

Speaking of ...

This summer, I called out Marcy Wheeler, aka Emptywheel, along with other Kossack alumni Dead-End Kids, for her absolutist claims backed by less than absolutist evidence that Donald Trump conspired with Vladimir Putin to get Trump elected.

A month later, I called out the presumably non-existent Forensicator, along with Tim Leonard/Adam Carter and anybody else invested in his likely creation, such as Disobedient Media, as well as people involved with propagating his claims that Guccifer 2.0 was NOT a Russian intelligence asset — such call-outs including Bill Binney, Ray McGovern and other members of the majority faction of Veteran Intelligence Professionals for Sanity and Patrick Lawrence for his credulous reporting, all of this indulged in detail at Consortium News. I also called out much of this consortium, abetted by the likes of ShirtLost DumbShit Zach Haller, for being the likely originator of Seth Rich conspiracy theories. (That said, Consortium News is a mare's nest of conspiracy thinking.)

Speaking of Seth Rich conspiracy theories, back in February, I called out idiot lawyer Jared Beck and his DNC fraud lawsuit filing, which sounds like it was written with a crayon.

Starting in February, and compiling more evidence throughout the year, I called out Beto O'Rourke for being a Fauxgressive ConservaDem.

When Schmuck Talk Express John McCain died, I called out Beltway media stenographers, bipartisan foreign policy think tanks and the like for failing to tell the truth about a person who was an Islamophobe and a warmonger, among other things.

Fortified by that, later I called out the Beltway stenos and allies for similar hagiography when Iran-Contra and October Surprise co-conspirator Poppy Bush died.

All call-outs, right?

With that pattern, I invite you to read my 2015 post on practicing philosophical Neo-Cynicism, my update on Diogenes' original Cynicism, and rejecting the conventional wisdom — and not just in politics — of the chattering classes.

December 24, 2018

Ocasio-Cortez has another unforced error:
This time, she botches government shutdown info

Alexandria-Ocasio Cortez, red rose Congressional queen of the House of Lancaster, I mean, the Democratic Socialists of America, has had several unforced errors since beating Joe Crowley to essentially win election to her 14th Congressional District.

First and most notable for people like me who bat outside the duopoly on foreign as well as domestic policy, was her retreat from words of support for BDS.

Second and related was her gushing over the Schmuck Talk Express™,  John McCain, when he died.

Well, now, she's shown that she should tweet less, research more, including knowing some basic constitutional facts, on the government shutdown.

AOC has a set of tweets that The Hill "reported" into a story, and oh, there's so much wrong.

First, she says Congresscritters should have salary cut off, after decrying partisan nature of shutdown (yet being already bipartisan enough to not call out Freedom Fries Caucus head Jim Jordan by name).

Second, she ignores a problem (which The Hill itself gets wrong as to the "why"). You can't cut Congressional salaries.

That relates to her not even mentioning the president's salary during the shutdown. Which, yes, also falls under the same rubric as that of Congresscritters, which The Hill got wrong.

It's not just illegal, which The Hill claims; it is unconstitutional, which is an entirely different kettle of fish. Explicitly so with the president. And for good reason. Although the president wound up much stronger than most members of Team Philadelphia 1787 not named Hamilton intended, the founders didn't want Congress forcing a president to their will by hacking his pay. (Of course, they objected when George III tried to insulate colonial governors from colonial legislative control, so, and far from the only time in America's founding, hypocrisy was at play.)

As for Congress, per the same link, in the current Congress, it's illegal to cut their pay, explicitly, by the 27th Amendment, which The Hill also gets wrong. When the new Congress starts, AOC could push a bill on the first day of the session that they don't get paid until the shutdown ends. She could also ask for it to be part of the standing rules in House and Senate. If I am engaging in correct constitutional interpretation, that could pass muster. But, short of an amendment, she still can't do anything about the president's salary.

Finally, if we're going to criticize Beltway stenos for "reporting" on Trump's tweets, should we not hold the stenos to the same standard re Ocasio-Cortez? I say yes. That piece had no actual reporting and was inaccurate. I've already Tweeted to the particular Beltway steno who "reported" this, specifically on the error, and got no response.

Update, Feb. 20, 2018: She's had other unforced errors, like throwing Rep. Omar halfway under the bus on Israel-Palestine issues.