Also, as we trace how these fever narratives spread, it's worth trying to catalog which corners (WH, Bannon, Nunes, others) fan the flames, to extent that's possible.
-
-
Replying to @emptywheel @TCleveland4Real
certainly. the goal of the piece was much more to trace the fanning of the flames; with the information we have, we can't really say to what extent Nunes et al were involved in the sourcing of the original piece.
1 reply 1 retweet 8 likes -
Replying to @qjurecic @TCleveland4Real
No. It's a critically important question, legally. But I respect Ross' reporting sufficiently to believe the story may have come via legit sources.
2 replies 1 retweet 6 likes -
Replying to @emptywheel @TCleveland4Real
right, at some point "a source familiar with the investigations" was involved, but it's not clear when. we tried to make that clear; hope we succeeded
2 replies 0 retweets 6 likes -
Replying to @qjurecic @TCleveland4Real
As
@benjaminwittes himself has written, that descriptive is more often than not a defense attorney. And particularly given Toensing's known "legal" tactics, I'd suggest defense attorney should remain default assumption.1 reply 1 retweet 12 likes -
Replying to @emptywheel @qjurecic and
Particularly given that she's got one client who demonstrably can be charged w/1001, at a minimum, and another, Clovis, in unknown amounts of jeopardy, plus visibility on a third.
2 replies 0 retweets 10 likes -
Replying to @emptywheel @qjurecic and
This is not a criticism of your piece. Just my nagging thought as I read it.
1 reply 0 retweets 4 likes -
of course. appreciate it!
1 reply 0 retweets 5 likes -
Far too often, our LE and intel wail about exposing secrets when what they're really complaining about is their opsec is bad enough to make reverse engineering possible if not easy. My gut feel is that's what went on here.
3 replies 4 retweets 10 likes
I'm absolutely NOT saying my OpSec is better. It's not. But I'm pretty good at reverse engineering tactics of LE and Intel myself.
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.