On today’s BradCast, Trita Parsi helps us make sense of the Israel/Syria attacks. I’m Angie Coiro of In Deep sitting in the host chair today.
Trita Parsi from the National Iranian American Council helps us get through the “they started it” claims around yesterday’s attacks. We spend some time deconstructing media reports and voices on the issue. He talks, too, about the Americans still held hostage in Iran, and potential long-term consequences of Trump pulling out of the nuclear agreement.
Then Brad Adams of Human Rights Watch talks about the release of American hostages from North Korea. I ask him about Israel kicking a Human Rights Watch employee out, based on his support of the Palestinian-led Boycott, Divestment, Sanctions (BDS) movement.
Then it’s back to Gina Haspel, as more news came out today about inaccuracies in her Senate testimony. Daphne Eviatar of Amnesty International details Amnesty’s call for Haspel’s CIA bid to be rejected.
Finally, we dig to the source of all those troublesome Scott Pruitt emails with Elena Saxonhouse, senior attorney with the Sierra Club. It was the Sierra Club’s dogged insistence on getting 24,000 pages of emails that opened up all those tales.
Download MP3 or listen online below…
[audio:http://bradblog.com/audio/BradCast_AngieCoiro_Trita Parsi_Brad Adams_Daphne Eviatar_Elena Saxonhouse_051018.mp3]
The genes of dictators comes to mind (The “It’s In Your Genes” Myth – 3).
I sent Brad some money last year, but I have been blocked from making any comments since I always get a message that I have already said the same thing. I guess you shouldn’t bite the hand that feeds you, Brad.
Larry Taylor @2:
Huh? No idea why your comments have been blocked, as you suggest. This one (obviously) went through fine. So, I’m not sure what you ran in to or why, but I haven’t done anything to you from being able to post and not sure what would.
The error message you describe sounds like one that might be built into WordPress to prevent someone from posting the same exact thing in quick succession (to avoid spammers). But I’d have to see the error message and what you were trying to post to even begin to guess.
Please feel free to drop me email with that info and I’ll see if something jumps out at me as to what could be causing it.
Sorry about whatever is causing the prob (as I would be to anyone, whether they donated or not!)
P.S. for Larry – I just took a quick look back and see about a dozen comments from you (with replies from myself, Desi and others) over the past year, so I’m even more befuddled. Sounds like your browser (or you) are somehow hitting the “Submit Comment” button twice in a row quickly, somehow, resulting in the error message you describe, rather than the page refreshing with the newly written comment showing. Not sure why that is and what browser you’re using that may be causing it. But that’s just a guess as to the prob. The comments themselves appear to be showing up just fine!