Human rights

Error message

  • Deprecated function: The each() function is deprecated. This message will be suppressed on further calls in _menu_load_objects() (line 579 of /var/www/drupal-7.x/includes/menu.inc).
  • Notice: Trying to access array offset on value of type int in element_children() (line 6600 of /var/www/drupal-7.x/includes/common.inc).
  • Notice: Trying to access array offset on value of type int in element_children() (line 6600 of /var/www/drupal-7.x/includes/common.inc).
  • Notice: Trying to access array offset on value of type int in element_children() (line 6600 of /var/www/drupal-7.x/includes/common.inc).
  • Notice: Trying to access array offset on value of type int in element_children() (line 6600 of /var/www/drupal-7.x/includes/common.inc).
  • Notice: Trying to access array offset on value of type int in element_children() (line 6600 of /var/www/drupal-7.x/includes/common.inc).
  • Notice: Trying to access array offset on value of type int in element_children() (line 6600 of /var/www/drupal-7.x/includes/common.inc).
  • Notice: Trying to access array offset on value of type int in element_children() (line 6600 of /var/www/drupal-7.x/includes/common.inc).
  • Notice: Trying to access array offset on value of type int in element_children() (line 6600 of /var/www/drupal-7.x/includes/common.inc).
  • Notice: Trying to access array offset on value of type int in element_children() (line 6600 of /var/www/drupal-7.x/includes/common.inc).
  • Notice: Trying to access array offset on value of type int in element_children() (line 6600 of /var/www/drupal-7.x/includes/common.inc).
  • Notice: Trying to access array offset on value of type int in element_children() (line 6600 of /var/www/drupal-7.x/includes/common.inc).
  • Notice: Trying to access array offset on value of type int in element_children() (line 6600 of /var/www/drupal-7.x/includes/common.inc).
  • Notice: Trying to access array offset on value of type int in element_children() (line 6600 of /var/www/drupal-7.x/includes/common.inc).
  • Notice: Trying to access array offset on value of type int in element_children() (line 6600 of /var/www/drupal-7.x/includes/common.inc).
  • Notice: Trying to access array offset on value of type int in element_children() (line 6600 of /var/www/drupal-7.x/includes/common.inc).
  • Notice: Trying to access array offset on value of type int in element_children() (line 6600 of /var/www/drupal-7.x/includes/common.inc).
  • Notice: Trying to access array offset on value of type int in element_children() (line 6600 of /var/www/drupal-7.x/includes/common.inc).
  • Notice: Trying to access array offset on value of type int in element_children() (line 6600 of /var/www/drupal-7.x/includes/common.inc).
  • Notice: Trying to access array offset on value of type int in element_children() (line 6600 of /var/www/drupal-7.x/includes/common.inc).
  • Notice: Trying to access array offset on value of type int in element_children() (line 6600 of /var/www/drupal-7.x/includes/common.inc).
  • Notice: Trying to access array offset on value of type int in element_children() (line 6600 of /var/www/drupal-7.x/includes/common.inc).
  • Notice: Trying to access array offset on value of type int in element_children() (line 6600 of /var/www/drupal-7.x/includes/common.inc).
  • Notice: Trying to access array offset on value of type int in element_children() (line 6600 of /var/www/drupal-7.x/includes/common.inc).
  • Notice: Trying to access array offset on value of type int in element_children() (line 6600 of /var/www/drupal-7.x/includes/common.inc).
  • Notice: Trying to access array offset on value of type int in element_children() (line 6600 of /var/www/drupal-7.x/includes/common.inc).
  • Notice: Trying to access array offset on value of type int in element_children() (line 6600 of /var/www/drupal-7.x/includes/common.inc).
  • Notice: Trying to access array offset on value of type int in element_children() (line 6600 of /var/www/drupal-7.x/includes/common.inc).
  • Notice: Trying to access array offset on value of type int in element_children() (line 6600 of /var/www/drupal-7.x/includes/common.inc).
  • Notice: Trying to access array offset on value of type int in element_children() (line 6600 of /var/www/drupal-7.x/includes/common.inc).
  • Notice: Trying to access array offset on value of type int in element_children() (line 6600 of /var/www/drupal-7.x/includes/common.inc).
  • Notice: Trying to access array offset on value of type int in element_children() (line 6600 of /var/www/drupal-7.x/includes/common.inc).
  • Notice: Trying to access array offset on value of type int in element_children() (line 6600 of /var/www/drupal-7.x/includes/common.inc).
  • Notice: Trying to access array offset on value of type int in element_children() (line 6600 of /var/www/drupal-7.x/includes/common.inc).
  • Notice: Trying to access array offset on value of type int in element_children() (line 6600 of /var/www/drupal-7.x/includes/common.inc).
  • Notice: Trying to access array offset on value of type int in element_children() (line 6600 of /var/www/drupal-7.x/includes/common.inc).
  • Notice: Trying to access array offset on value of type int in element_children() (line 6600 of /var/www/drupal-7.x/includes/common.inc).
  • Notice: Trying to access array offset on value of type int in element_children() (line 6600 of /var/www/drupal-7.x/includes/common.inc).
  • Notice: Trying to access array offset on value of type int in element_children() (line 6600 of /var/www/drupal-7.x/includes/common.inc).
  • Notice: Trying to access array offset on value of type int in element_children() (line 6600 of /var/www/drupal-7.x/includes/common.inc).
  • Notice: Trying to access array offset on value of type int in element_children() (line 6600 of /var/www/drupal-7.x/includes/common.inc).
  • Notice: Trying to access array offset on value of type int in element_children() (line 6600 of /var/www/drupal-7.x/includes/common.inc).
  • Notice: Trying to access array offset on value of type int in element_children() (line 6600 of /var/www/drupal-7.x/includes/common.inc).
  • Notice: Trying to access array offset on value of type int in element_children() (line 6600 of /var/www/drupal-7.x/includes/common.inc).
  • Notice: Trying to access array offset on value of type int in element_children() (line 6600 of /var/www/drupal-7.x/includes/common.inc).
  • Notice: Trying to access array offset on value of type int in element_children() (line 6600 of /var/www/drupal-7.x/includes/common.inc).
  • Notice: Trying to access array offset on value of type int in element_children() (line 6600 of /var/www/drupal-7.x/includes/common.inc).
  • Notice: Trying to access array offset on value of type int in element_children() (line 6600 of /var/www/drupal-7.x/includes/common.inc).
  • Notice: Trying to access array offset on value of type int in element_children() (line 6600 of /var/www/drupal-7.x/includes/common.inc).
  • Notice: Trying to access array offset on value of type int in element_children() (line 6600 of /var/www/drupal-7.x/includes/common.inc).
  • Notice: Trying to access array offset on value of type int in element_children() (line 6600 of /var/www/drupal-7.x/includes/common.inc).
  • Notice: Trying to access array offset on value of type int in element_children() (line 6600 of /var/www/drupal-7.x/includes/common.inc).
  • Notice: Trying to access array offset on value of type int in element_children() (line 6600 of /var/www/drupal-7.x/includes/common.inc).
  • Notice: Trying to access array offset on value of type int in element_children() (line 6600 of /var/www/drupal-7.x/includes/common.inc).
  • Notice: Trying to access array offset on value of type int in element_children() (line 6600 of /var/www/drupal-7.x/includes/common.inc).
  • Notice: Trying to access array offset on value of type int in element_children() (line 6600 of /var/www/drupal-7.x/includes/common.inc).
  • Notice: Trying to access array offset on value of type int in element_children() (line 6600 of /var/www/drupal-7.x/includes/common.inc).
  • Notice: Trying to access array offset on value of type int in element_children() (line 6600 of /var/www/drupal-7.x/includes/common.inc).
  • Notice: Trying to access array offset on value of type int in element_children() (line 6600 of /var/www/drupal-7.x/includes/common.inc).
  • Notice: Trying to access array offset on value of type int in element_children() (line 6600 of /var/www/drupal-7.x/includes/common.inc).
  • Notice: Trying to access array offset on value of type int in element_children() (line 6600 of /var/www/drupal-7.x/includes/common.inc).
  • Notice: Trying to access array offset on value of type int in element_children() (line 6600 of /var/www/drupal-7.x/includes/common.inc).
  • Notice: Trying to access array offset on value of type int in element_children() (line 6600 of /var/www/drupal-7.x/includes/common.inc).
  • Notice: Trying to access array offset on value of type int in element_children() (line 6600 of /var/www/drupal-7.x/includes/common.inc).
  • Notice: Trying to access array offset on value of type int in element_children() (line 6600 of /var/www/drupal-7.x/includes/common.inc).
  • Notice: Trying to access array offset on value of type int in element_children() (line 6600 of /var/www/drupal-7.x/includes/common.inc).
  • Notice: Trying to access array offset on value of type int in element_children() (line 6600 of /var/www/drupal-7.x/includes/common.inc).
  • Notice: Trying to access array offset on value of type int in element_children() (line 6600 of /var/www/drupal-7.x/includes/common.inc).
  • Notice: Trying to access array offset on value of type int in element_children() (line 6600 of /var/www/drupal-7.x/includes/common.inc).
  • Notice: Trying to access array offset on value of type int in element_children() (line 6600 of /var/www/drupal-7.x/includes/common.inc).
  • Notice: Trying to access array offset on value of type int in element_children() (line 6600 of /var/www/drupal-7.x/includes/common.inc).
  • Notice: Trying to access array offset on value of type int in element_children() (line 6600 of /var/www/drupal-7.x/includes/common.inc).
  • Notice: Trying to access array offset on value of type int in element_children() (line 6600 of /var/www/drupal-7.x/includes/common.inc).
  • Notice: Trying to access array offset on value of type int in element_children() (line 6600 of /var/www/drupal-7.x/includes/common.inc).
  • Notice: Trying to access array offset on value of type int in element_children() (line 6600 of /var/www/drupal-7.x/includes/common.inc).
  • Notice: Trying to access array offset on value of type int in element_children() (line 6600 of /var/www/drupal-7.x/includes/common.inc).
  • Notice: Trying to access array offset on value of type int in element_children() (line 6600 of /var/www/drupal-7.x/includes/common.inc).
  • Notice: Trying to access array offset on value of type int in element_children() (line 6600 of /var/www/drupal-7.x/includes/common.inc).
  • Notice: Trying to access array offset on value of type int in element_children() (line 6600 of /var/www/drupal-7.x/includes/common.inc).
  • Notice: Trying to access array offset on value of type int in element_children() (line 6600 of /var/www/drupal-7.x/includes/common.inc).
  • Notice: Trying to access array offset on value of type int in element_children() (line 6600 of /var/www/drupal-7.x/includes/common.inc).
  • Notice: Trying to access array offset on value of type int in element_children() (line 6600 of /var/www/drupal-7.x/includes/common.inc).
  • Notice: Trying to access array offset on value of type int in element_children() (line 6600 of /var/www/drupal-7.x/includes/common.inc).
  • Notice: Trying to access array offset on value of type int in element_children() (line 6600 of /var/www/drupal-7.x/includes/common.inc).
  • Notice: Trying to access array offset on value of type int in element_children() (line 6600 of /var/www/drupal-7.x/includes/common.inc).
  • Notice: Trying to access array offset on value of type int in element_children() (line 6600 of /var/www/drupal-7.x/includes/common.inc).
  • Notice: Trying to access array offset on value of type int in element_children() (line 6600 of /var/www/drupal-7.x/includes/common.inc).
  • Notice: Trying to access array offset on value of type int in element_children() (line 6600 of /var/www/drupal-7.x/includes/common.inc).
  • Notice: Trying to access array offset on value of type int in element_children() (line 6600 of /var/www/drupal-7.x/includes/common.inc).
  • Notice: Trying to access array offset on value of type int in element_children() (line 6600 of /var/www/drupal-7.x/includes/common.inc).
  • Notice: Trying to access array offset on value of type int in element_children() (line 6600 of /var/www/drupal-7.x/includes/common.inc).
  • Notice: Trying to access array offset on value of type int in element_children() (line 6600 of /var/www/drupal-7.x/includes/common.inc).
  • Notice: Trying to access array offset on value of type int in element_children() (line 6600 of /var/www/drupal-7.x/includes/common.inc).
  • Notice: Trying to access array offset on value of type int in element_children() (line 6600 of /var/www/drupal-7.x/includes/common.inc).
  • Notice: Trying to access array offset on value of type int in element_children() (line 6600 of /var/www/drupal-7.x/includes/common.inc).
  • Notice: Trying to access array offset on value of type int in element_children() (line 6600 of /var/www/drupal-7.x/includes/common.inc).
  • Notice: Trying to access array offset on value of type int in element_children() (line 6600 of /var/www/drupal-7.x/includes/common.inc).
  • Notice: Trying to access array offset on value of type int in element_children() (line 6600 of /var/www/drupal-7.x/includes/common.inc).
  • Notice: Trying to access array offset on value of type int in element_children() (line 6600 of /var/www/drupal-7.x/includes/common.inc).
  • Notice: Trying to access array offset on value of type int in element_children() (line 6600 of /var/www/drupal-7.x/includes/common.inc).
  • Notice: Trying to access array offset on value of type int in element_children() (line 6600 of /var/www/drupal-7.x/includes/common.inc).
  • Notice: Trying to access array offset on value of type int in element_children() (line 6600 of /var/www/drupal-7.x/includes/common.inc).
  • Notice: Trying to access array offset on value of type int in element_children() (line 6600 of /var/www/drupal-7.x/includes/common.inc).
  • Notice: Trying to access array offset on value of type int in element_children() (line 6600 of /var/www/drupal-7.x/includes/common.inc).
  • Notice: Trying to access array offset on value of type int in element_children() (line 6600 of /var/www/drupal-7.x/includes/common.inc).
  • Notice: Trying to access array offset on value of type int in element_children() (line 6600 of /var/www/drupal-7.x/includes/common.inc).
  • Notice: Trying to access array offset on value of type int in element_children() (line 6600 of /var/www/drupal-7.x/includes/common.inc).
  • Notice: Trying to access array offset on value of type int in element_children() (line 6600 of /var/www/drupal-7.x/includes/common.inc).
  • Notice: Trying to access array offset on value of type int in element_children() (line 6600 of /var/www/drupal-7.x/includes/common.inc).
  • Notice: Trying to access array offset on value of type int in element_children() (line 6600 of /var/www/drupal-7.x/includes/common.inc).
  • Deprecated function: implode(): Passing glue string after array is deprecated. Swap the parameters in drupal_get_feeds() (line 394 of /var/www/drupal-7.x/includes/common.inc).

Do as I say, not as I do

Published by Anonymous (not verified) on Fri, 03/05/2024 - 4:54am in

Antony Blinken megaphoned the United States’ complaints about China in advance of his visit this week. They included Beijing’s unfair economic and trade practices, ‘industrial over-capacity’, and ‘genocide and crimes against humanity’ against Uyghurs. Coming from the nation most complicit in Israel’s human rights violations and potential genocide against Palestinians, the Secretary of State’s hypocrisy Continue reading »

Inside Job? Ominous New Questions Surround Navalny’s Death

On April 27, the Wall Street Journal published an investigation based on as yet unpublished U.S. intelligence community assessments and anonymous briefings courtesy of “security officials from several European capitals,” which concluded that Vladimir Putin neither orchestrated Russian opposition activist Alexei Navalny’s death in prison two months earlier nor desired it to happen.

It was a belated and confounding intervention in a case that, after an initially intense frenzy of mainstream speculation and accusations, quickly went cold before vanishing from mainstream consideration entirely.

While exerting little domestic influence outside atypically liberal enclaves in Moscow, St. Petersburg and other major cities, Navalny was the U.S. and Europe’s most cherished and prominent Putin detractor by some margin for over a decade before his death. His every publicity stunt garnered universal media attention, and the regular publications of his Anti-Corruption Foundation (FBK) on state official embezzlement and grift in Russia invariably broke the internet. Western human rights awards were routinely forthcoming.

After purportedly being poisoned on an inter-Russian flight by the FSB in August 2020, then recovering in Germany, he made a much-publicized “hero’s return” to Moscow, at which point, he was summarily jailed. Despite giving regular interviews to the Western media from prison and testifying to the rotten conditions in which he was held, Navalny had largely faded from public consciousness by the time news of his death broke on February 16.

Immediately, the entire Western political, media, and pundit sphere was apoplectic. “Make no mistake. Putin is responsible for Navalny’s death!” U.S. President Joe Biden forcefully declared. Meanwhile, Navalny’s widow, Yulia, accused Russian authorities of “hiding his body” as they were “waiting for the traces of yet another of Putin’s novichoks to disappear”:

My husband could not be broken. And that’s exactly why Putin killed him. Shameful, cowardly, not daring to look into his eyes or simply say his name. We will tell you about it soon. We will definitely find out who exactly carried out this crime and how exactly. We will name the names and show the faces.”

Yet, on February 26, Ukrainian military chief Kyrylo Budanov “disappointed” everyone by announcing Navalny, in fact, died as a result of simple health complications – namely, a blood clot. The U.S. intelligence assessments cited by the Wall Street Journal, based on “some classified intelligence and an analysis of public facts,” reportedly draw the same conclusion. Quite why this apparent confirmation took so long to surface isn’t clear, although it delivered a “coup de grâce” to any and all suggestions Navalny was deliberately assassinated.

Since the invasion of Ukraine began, Western spying agencies and officials in Kiev have relentlessly spewed oft-intelligence insulting, illogical black propaganda about the proxy conflict. We must ask ourselves why the same sources that would have us believe Russian forces were at one point fighting with shovels, and Moscow blew up its own Nord Stream 2 pipeline, seek to shut down suggestions Navalny was murdered.

 

‘Cataclysmic Loss’

Budanov’s declaration decisively shunted Navalny’s demise from international headlines. Such is the pace with which events move these days that it is perhaps forgotten that immediately following February 16, there was a concerted campaign by highly influential Western anti-Russian actors for the EU and U.S. to adopt a “Navalny Act.” Under its auspices, the approximately $300 billion Russian assets frozen by Western financial institutions in the wake of Moscow’s invasion would be seized and given to Ukraine.

At the forefront of this effort was billionaire Bill Browder, an investment manager who reaped untold sums from privatization and asset stripping in Russia during the 1990s and supported Putin’s rise to power before being turfed from the country in 2005 on national security grounds. Since then, he has transformed himself into the Kremlin’s most pugnacious overseas critic and an “anti-corruption” campaigner, despite giving up his U.S. citizenship to evade tax. Speaking to UnHerd on February 20, Browder talked a big game:

Now is the moment…Putin is willing to lose one million men, but to lose $300 billion would be a cataclysmic loss. All world leaders are looking for a way to hit Putin back for this murder. I’ve been working on confiscating these assets for the last two years, and the Navalny murder is the impetus to get it done.”

Browder had good reason to believe this campaign would bear fruit. For almost 15 years, he has traveled the world telling journalists, lawmakers, and human rights organizations a shocking story of corruption, fraud, and murder at the highest levels of the Kremlin. In brief, he claims local officials forcibly seized the Russian division of his company, Hermitage Capital Management, to carry out a massive tax scam, reaping $230 million in the process.

According to Browder’s narrative, he then set his “friend” Sergei Magnitsky, a gifted lawyer, on the case to determine what happened. The diligent sleuth duly uncovered the fraud and alerted authorities but ended up jailed on bogus charges for his courageous whistleblowing. He was then viciously tortured in prison in an attempt to make him retract his testimony before being beaten to death by guards for refusing.

Typically, Browder’s audiences have been highly receptive. Over the years, his story has been immortalized in multiple articles, books, official reports and documentaries, influencing legislation and prosecutions in numerous countries. Every member of the “Five Eyes” global spying network and the EU have been successfully lobbied to adopt a “Magnitsky Act,” which sanctions government officials overseas—particularly in Russia—for purported human rights abuses.

 

‘Navalny Act’

In reality, Browder’s entire Magnitsky fable is a tangled web of lies, fabrications, distortions, exaggerations, and libel. From the very moment he started spinning this deceptive yarn, sufficient open-source, public-domain evidence was available to disprove its every aspect comprehensively. Yet, it took a decade for mainstream journalists to conduct serious due diligence on his assertions. In November 2019, leading German news outlet Der Spiegel published a comprehensive demolition job, savagely indicting Browder’s integrity in the process.

In the publication’s words, Brodwer “has a talent for selling a set of facts so it supports his own version of events.” Magnitsky was, in fact, neither a lawyer nor a whistleblower. He was a crooked accountant who had long-abetted Browder’s fraudulent financial dealings in Russia and was justly imprisoned for these activities. This was confirmed by a damning ruling in August of that year by the European Court of Human Rights in a case brought by Browder and Magnitsky’s family.

While the ECHR ordered Moscow to pay Magnitsky’s relatives $37,500 due to a failure to protect his life and health, having identified shortcomings in the medical treatment he was provided in prison, no mention of murder or even unlawful killing was made in the judgment. Conversely, the court rejected suggestions his arrest and subsequent detention were “manifestly ill-founded” or that “authorities had…acted with bad faith or deception:”

The Court reiterated the general principles on arbitrary detention…It found no such elements in this case. The decision to arrest him had only been made after investigators learned he’d previously applied for a UK visa, booked tickets to Kiev, and hadn’t been residing at his registered address. Furthermore, the evidence against him, including witness testimony, had been enough to satisfy an objective observer that he might have committed the offense in question.”

Der Spiegel’s investigation contained a striking passage, the obvious import of which was bizarrely ignored by the outlet. In it, Zoya Svetova, a Moscow-based human-rights activist who investigated Magnitsky’s death in 2009, said:

What sense would it make to murder him? Magnitsky did not reveal any secret. They wanted testimonies against Browder. That was the motivation. He should have accused Browder of not paying taxes. Magnitsky was a hostage. He himself was of no interest to them. They wanted Browder.”

Bill BrowderAnti-Russia campaigner Bill Browder speaking to the media outside the Old Bailey in London, December 19, 2018. Mr Perepilichnyy, 44, Dominic Lipinski | PA Wire

In other words, it was Browder who benefited from Magnitsky’s death, not Russian authorities, which raises the grave prospect that it was the “anti-corruption” campaigner himself who was, one way or another, responsible for his accountant’s tragic passing. Such a reading is amply reinforced by the sworn deposition of Russian opposition activist Oleg Lurie in a failed legal case brought by U.S. authorities against Russian-owned company Prevezon, based on Browder’s bogus claim the firm’s owners were beneficiaries of the $230 million fraud.

Lurie was concurrently incarcerated in the same prison as Magnitsky, and the pair crossed paths twice. The first time, the accountant was in a “happy mood,” boasting of how he was held in a “big special block” for “white crime inmates,” where cells had “plasma TV sets, refrigerators, kettles” and illegally installed telephones. The reason for his buoyancy, Magnitsky explained to Lurie, was that his Western employers would “save him…they would take him out of there” in a matter of days.

As Browder et al. wished for Magnitsky to “keep silence about their actions” and his own crime to be “not serious,” he seemed assured that freedom was impending. Lurie warned him that “his attorneys and people who claim to be standing behind him are lying to him,” but the accountant was unconvinced. Fast-forward a few weeks, and they met again. Magnitsky was “a completely different person at that time…a tangle of nerves,” Lurie testified.

Magnitsky revealed that the “Western people who stood behind him deceived him…they demanded him to sign various documents” completely unrelated to his case, which would’ve implicated him in numerous serious crimes he didn’t commit. As a result, “he had a feeling that he would never get out.” Navalny, like Magnitsky, wasn’t leaving prison anytime soon and almost certainly knew too much. Did his Western backers similarly consider it necessary to silence him?

At the very least, it is supremely puzzling that the Ukrainian government effectively torpedoed the “Navalny Act.” After all, Kiev has, since the start of the proxy conflict, implored Western leaders to hand Russia’s frozen assets to them in service of the country’s reconstruction and the purchase of ever-more weapons and ammunition. The Act would’ve delivered on those demands. There was no clear need at all for Budanov to electively sabotage the narrative of Navalny as a Kremlin murder victim.

 

‘British Spy’

There are also sinister echoes in the sudden mainstream “reverse ferret” on Navalny’s untimely demise with the similarly mysterious and abrupt November 2019 passing of James Lemesurier, longtime British mercenary and military intelligence operative. Immediately following his fatal fall from the window of his lavish Istanbul apartment, Western sources rushed to convict Russia without evidence, claiming his death may have been – or was likely – a targeted assassination. The most prominent was Mark Urban, veteran BBC “defence” editor.

Within hours of Lemesurier’s lethal crash landing, Urban took to Twitter, urging Turkish authorities to “conduct a thorough investigation” and “ascertain whether there was state involvement.” His misgivings were in part perked by an “extensive black propaganda campaign by Russian and Assad media and their acolytes” in the months prior. In other words, critical, independent reporting raises grave questions about whether Lemesurier’s “White Helmets” were the crusading humanitarian group universally portrayed in the mainstream or something far darker.

More substantively, “a former colleague” – whether of Lemesurier or Urban isn’t clear – told the BBC journeyman, “I know the flat well, [and] it’s not possible to ‘fall’ from that balcony.” They strongly suspected foul play as a result. Seismic stuff, although curiously, these posts were quickly deleted due to Urban allegedly receiving “new information.” The nature of this “information” and who supplied it has never been revealed. But immediately after that, the same sources that hitherto cried murder began labeling Lemesurier’s death an unambiguous suicide.

To say the least, Urban is extremely well-connected in the Western military, security, and intelligence sphere and highly adept at withholding salient facts from public view. In July 2018, he revealed he’d serendipitously spent much of the previous year interviewing Sergei Skripal, who, along with his daughter, was purportedly poisoned in the British city of Salisbury three months earlier. In the intervening time, Urban fronted multiple BBC Newsnight reports about the incident without ever mentioning his personal relationship with the GRU defector.

For Urban – coincidentally once part of the same British Army tank regiment as Pablo Miller, Skripal’s MI6 recruiter, handler, and Salisbury neighbor – to delete his incendiary tweets surely required a high-level intervention. At that time, as now, blaming Russia or Putin for anything and everything – including quite literally the weather – was a thoroughly safe option in the West, without any consequences attached. We are thus left to ponder how and why a long-serving, spook-adjacent British state ‘journalist’ was compelled to retract these charges.

Evidently, though, Urban’s sources – the “former colleague” who clearly said too much aside – were keen that Lemesurier’s end not be perceived or investigated as murder by anyone. Turkish media reports in the aftermath may provide a rationale for this. One article revealed James and his wife, Emma Winberg, a self-professed MI6 operative, “fought violently” outside an Istanbul restaurant just before his deadly plunge. Another suggested Lemesurier – a “British spy” – was “likely running away from someone before his death.”

Fast forward to today, and again, interested parties are eager to dismiss suggestions a high-profile Western asset’s death was the result of foul play. In Navalny’s case, as with Lemesurier, those shadowy elements – the Ukrainian government and the CIA being just two publicly confirmed so far – had every reason to accuse Moscow of murder. Yet, they not only didn’t but instead went to great lengths to remove any insinuation of deliberate killing from the equation. Make of that what you will.

Feature photo | Illustration by MintPress News

Kit Klarenberg is an investigative journalist and MintPress News contributor exploring the role of intelligence services in shaping politics and perceptions. His work has previously appeared in The Cradle, Declassified UK, and Grayzone. Follow him on Twitter @KitKlarenberg.

The post Inside Job? Ominous New Questions Surround Navalny’s Death appeared first on MintPress News.

Breaking video: LA police smash UCLA camp, violently arrest peaceful students

US state mobilises to break protest after taking hours to act against violent pro-Israel mob last night

Los Angeles police have stormed the pro-Gaza protest camp set up by peaceful student protesters at the University of California Los Angeles (UCLA).

Riot-clad police are violently arresting students and faculty taking part in the protest against the university’s complicity in Israel’s genocide – which has killed well over 40,000 civilians, mostly women and children – and is smashing up tents and makeshift buildings, despite free speech and association rights being guaranteed by the US Constitution:

Video by Middle East Eye

Solidarity with the people of Gaza and with students everywhere demonstrating against genocide and for peace.

If you wish to republish this post for non-commercial use, you are welcome to do so – see here for more.

America is Rising for Gaza: What Should We Expect?

Published by Anonymous (not verified) on Thu, 02/05/2024 - 11:31pm in

The mass protests at dozens of U.S. universities cannot be reduced to a stifling and misleading conversation about antisemitism.

Thousands of American students across the country are not protesting, risking their futures and very safety, because of some pathological hate for the Jewish people. They are doing so in a complete rejection of, and justifiable outrage over, the mass killing carried out by the state of Israel against defenseless Palestinians in Gaza.

They are angry because the bloodbath in the Gaza Strip, starting on October 7, is fully funded and backed by the U.S. government.

These mass protests began at the University of Columbia on April 17 before covering all of U.S. geography, from New York to Texas and North Carolina to California.

The protests are being compared, in terms of their nature and intensity, to the anti-war demonstrations in the U.S. against the Vietnam War in the 1960s and 70s.

While the comparison is apt, it is critical to note the ethnic diversity and social inclusiveness in the current protests. On many campuses, Arab, Muslim, Jewish, Black, Native American and White students are standing shoulder to shoulder with their Palestinian peers in a unified stance against the war.

None of them is motivated by fear that they could be drafted to fight in Gaza, as was, indeed, the case for many American students during the Vietnam War era. Instead, they are united around a clear set of priorities: ending the war, ending U.S. support of Israel, ending their universities’ direct investment in Israel and the recognition of their right to protest. This is not idealism but humanity at its finest moments.

Despite mass arrests, starting in Columbia, and the direct violence against peaceful protesters everywhere, the movement has only grown stronger.

On the other side, U.S. politicians, starting with President Joe Biden, accused the protesters of antisemitism without engaging with any of their reasonable and globally-supported demands.

Once again, the Democratic and Republican establishments stood together in blind support for Israel.

Biden condemned the “antisemitic protests,” describing them as “reprehensible and dangerous.”

Israel Palestinians Campus ProtestsPolice advance on pro-Palestinian demonstrators in an encampment on the UCLA campus, May 2, 2024, in Los Angeles. Jae C. Hong | AP

A few days later, the U.S. House of Representatives speaker, Mike Johnson, visited the university under tight security, using language hardly suitable for a country that claims to embrace democracy, respect, freedom of expression and the right to assembly.

“We just can’t allow this kind of hatred and antisemitism to flourish on our campuses,” he said, adding: “I am here today joining my colleagues and calling on President (Minouche) Shafik to resign if she cannot immediately bring order to this chaos.”

Shafik, however, was already on board, as she was the one who had called for the New York Police Department to crack down on the protesters, falsely accusing them of antisemitism.

U.S. mainstream media has contributed to the confusion and misinformation regarding the reasons behind the protests.

The Wall Street Journal, once more, allowed writers such as Steven Stalinsky to smear young justice activists for daring to criticize Israel’s horrendous genocide in Gaza.

“Hamas, Hezbollah, the Houthis and others are grooming activists in the U.S. and across the West,” he alleged, thus once more taking a critical conversation about U.S. support of genocide into bizarre and unsubstantiated directions.

U.S. establishment writers may wish to continue fooling themselves and their readers. Still, the truth is that neither Hezbollah nor Hamas ‘recruiters’ are active in Ivy League universities, where young people are often groomed to become leaders in government and large corporations.

All such distractions are meant to avoid the undeniable shift in American society, one that promises a long-term paradigm shift in popular views of Israel and Palestine.

For years before the current war, Americans have been changing their opinions on Israel and their country’s so-called ‘special relationship‘ with Tel Aviv.

Young Democrats have led the trend, which can also be observed among independents and, to some extent, young Republicans.

A statement that asserts that “sympathies in the Middle East now lie more with the Palestinians than the Israelis” would have been unthinkable in the past. But it is the new normal, and the latest opinion polls regarding the subject and Biden’s dwindling approval ratings continue to attest to this fact.

Israel Palestinians Campus ProtestsPro-Palestinian demonstrators from the Columbia University are held in an NYPD corrections bus on April 30, 2024. John Lamparski | NurPhoto | AP

The older generations of American politicians, who have built and sustained careers based on their unconditional support for Israel, are overwhelmed by the new reality. Their language is confused and riddled with falsehoods. Yet, they are willing to go as far as defaming a whole generation of their own people – the future leaders of America – to satisfy the demands of the Israeli government.

In a televised statement on April 24, Israeli Prime Minister Benjamin Netanyahu described the protesters as “antisemitic mobs” who “have taken over leading universities,” alleging that the peaceful protesters are calling “for the annihilation of Israel.” His words should have outraged all Americans, regardless of their politics and ideology. Instead, more U.S. politicians began parroting Netanyahu’s words.

However, this political opportunism will generate a blowback effect, not just in the distant future but also in the coming weeks and months, especially in the run-up to the presidential elections.

Millions of Americans are fed up with war, with their government’s allegiance to a foreign country, with militarism, with police violence and with the unprecedented restrictions on freedom of speech in the U.S. and more.

Young Americans, who are not beholden to the self-interests or historical and spiritual illusions of previous generations, are declaring: ‘Enough is enough.’ They are doing more than chanting. They are rising in unison, demanding answers, moral and legal accountability and an immediate end to the war.

Now that the U.S. government has taken no action and continues to feed the Israeli war machine in its onslaught against millions of Palestinians, these brave students are acting themselves. This is certainly an awe-inspiring watershed moment in the history of the United States.

Feature photo | People stand atop a pile of barricades as they lead a chant at an encampment by students protesting against Israel at George Washington University, April 30, 2024. Mark Schiefelbein | AP

Dr. Ramzy Baroud is a journalist, author and the Editor of The Palestine Chronicle. He is the author of six books. His latest book, co-edited with Ilan Pappé, is ‘Our Vision for Liberation: Engaged Palestinian Leaders and Intellectuals Speak Out.’ His other books include ‘My Father Was a Freedom Fighter’ and ‘The Last Earth’. Baroud is a Non-resident Senior Research Fellow at the Center for Islam and Global Affairs (CIGA). His website is www.ramzybaroud.net 

The post America is Rising for Gaza: What Should We Expect? appeared first on MintPress News.

America’s informal empire – what really went wrong in the Middle East

Published by Anonymous (not verified) on Thu, 02/05/2024 - 7:52pm in

In this edited excerpt from the introduction to What Really Went WrongFawaz A Gerges argues that US interventionism during the Cold War – especially in Iran and Egypt – steered the Middle East away from democracy towards authoritarianism, shaping the region’s political and economic landscape for decades to come.

What Really Went Wrong: The West and the Failure of Democracy in the Middle East. Fawaz A Gerges. Yale University Press. 2024. 

What Really Went Wrong by Fawaz A Gerges book coverAt the end of the colonial era after World War Two, the Middle East was on the cusp of a new awakening. Imperial Britain, France, and Italy were discredited and exhausted. Hope filled the air in newly independent countries around the world. Like people across the decolonised Global South, Middle Easterners had great expectations and the material and spiritual energy needed to seize their destiny and modernise their societies. Few could have imagined events unfolding as disastrously as they did. Yet by the late 1950s, the Middle East had descended into geostrategic rivalries, authoritarianism and civil strife.

What clouded this promising horizon? Digging deep into the historical record, What Really Went Wrong critically examines flashpoints like the US Central Intelligence Agency (CIA)’s ousting of Iranian Prime Minister Mohammad Mosaddeq in August 1953 and the US confrontation with Egyptian President Gamal Abdel Nasser in the mid-1950s. My argument is that such flashpoints sowed the seeds of subsequent discontent, hubris and conflict. I zero in on these historical ruptures to reconstruct a radically different story of what went wrong in the region, thus correcting the dominant narrative. My goal is to engender a debate about the past that can make us see the present differently.

What Really Went Wrong critically examines flashpoints like the US Central Intelligence Agency (CIA)’s ousting of Iranian Prime Minister Mohammad Mosaddeq in August 1953 and the US confrontation with Egyptian President Gamal Abdel Nasser in the mid-1950s.

I argue that the defeat and marginalisation of secular-leaning nationalist visions in Iran and Egypt in the 1950s and ’60s allowed for Sunni and Shia pan-Islamism to gain momentum throughout the Middle East and beyond. Because of bad decisions made in the White House, power passed from popular leaders and sincere patriots to unpopular and subservient rulers, and the sympathy of the people was hijacked by Islamist leaders and movements. The consequences of events in both Iran and Egypt still haunt the Middle East today.

The dawn of US interventionism

The book’s core concern is with the legacy and impact of US foreign policy during the early years of the Cold War on political and economic development in the Middle East. It focuses on two major pieces of the puzzle: momentous events in Iran and Egypt in which America played a decisive role. Examining these, it shows how Anglo-American interventions in the internal affairs of the Middle East from the early 1950s (till the present) stunted political development and social change there and led the region down the wrong path to authoritarianism and militarism. The Middle East was reimagined as a Cold War chessboard, which left a legacy marked by dependencies, weak political institutions, low levels of civil and human rights protection, lopsided economic growth and political systems prone to authoritarianism. This is the antithesis of often-stated Western values rooted in democracy, human rights and the rule of law.

An informal empire emerges

Developing countries emerged into independence from a history that left its mark on their future. It was difficult enough for countries emerging from colonialism to build sound institutions, gain public trust and extend state authority, and America’s imperial ambitions and actions during and after the Cold War made this all the more difficult, if not impossible. With the foundations of imperialism far from completely dismantled, old structures persisted under new names. In some cases, it was more than just structures that perpetuated dependence. It was the very leaders and their descendants who were co-opted into a neocolonial reality. Anyone challenging that order was swiftly marked as an enemy of democracy and free markets.

With the foundations of imperialism far from completely dismantled, old structures persisted under new names.

Within living memory, the peoples of the Middle East viewed the US with awe and optimism. Unlike its European allies, America had never ruled over Muslim lands and appeared to have no imperial ambitions. Instead, Americans had built hospitals and major universities in the region. Washington could have built relations on the basis of mutual interests and respect, not dependency and domination. When the US signed an agreement with Saudi Arabia to begin oil exploration in 1933, the people of the region saw it as an opportunity to decrease their dependence on the “imperial colossus,” Great Britain. But from the Middle East to Africa and Asia, newly decolonised countries discovered that formal independence did not translate into full sovereignty. A creeping form of colonialism kept tying these countries to their old European masters and the new American power.

As the historian Rashid Khalidi noted, the US was following in the footprints of European colonialism. In his book Imperialism and the Developing World, Atul Kohli compares British imperialism during 19th century with America’s informal empire in the 20th. It might not have been formally called colonialism, but the effects were the same: Washington – often backed by London – pursued its interests at the cost of the right to self-determination and sovereignty of other peoples and countries.

Cold War divisions, US opportunism

Setting up defence pacts in the Middle East in the early 1950s to encircle Russia’s southern flank, Eisenhower’s Cold Warriors pressured friends and foes to join in America’s network of alliances against Soviet communism. Newly decolonised states like Iraq, Egypt, Iran (which was not formally colonised), and Pakistan had to choose between jumping on Uncle Sam’s informal empire bandwagon or being trampled under its wheels.

The Truman and Eisenhower administrations laid the foundation of an imperial foreign policy which was hardened by the Nixon and Reagan presidencies. The US provided arms, aid and security protection to the shah and to Israeli and Saudi leaders during the Cold War. This led to economic growth, but as Kohli notes, it was not evenly distributed throughout the region. After the end of the Cold War in 1989, US imperial foreign policy persisted with George W. Bush, who waged a global war on terror that saw the US invade and occupy Afghanistan and Iraq.

The US foreign policy establishment saw the world through imperial lenses that divided everything into binary terms – black and white, good and evil. In their eyes, the existential struggle against Soviet communism justified violence, collective punishment and all other means to achieve their ideological ends. In June 1961, then-CIA director Allen Dulles, declared that the destruction of the “system of colonialism” was the first step to defeat the “Free World.”

While establishing this foreign policy strategy, the US […] was also building the postwar international financial and trading and security institutions that allowed its competitive corporations to outperform others.

While establishing this foreign policy strategy, the US – as the dominant capitalistic superpower – was also building the postwar international financial and trading and security institutions that allowed its competitive corporations to outperform others. This global system of open, imperial economies disproportionately steered the fruits of the world’s economic growth to the citizens of the West, particularly Americans. Kohli argues that the US sought to tame sovereign and effective state power in the newly decolonised world. Regime change, covert and overt military interventions, sanctions to create open economies and acquiescent governments were all among the weapons of the informal Cold War imperialism, all wielded with the soundtrack of piercing alarm about the spectre of a Soviet communist threat.

The “Free World” fallacy

The project was not without opposition, however. Nationalist forces resisted the new imperialism, and US leaders escalated their military efforts to defeat indigenous opposition. With its thinly veiled imperialism, insubstantial justification for using military force and vague claims about impending threats to the “homeland”, the US began to lose credibility. Washington’s shortsighted views ultimately backfired, undermining security globally and forestalling good governance in the Middle East and beyond.

This imperial vision had ramifications for the West’s self-appointed role as the leader of the free world and defender of human rights, going well beyond reputation.

This imperial vision had ramifications for the West’s self-appointed role as the leader of the free world and defender of human rights, going well beyond reputation. Mistrust in the international liberal order has weakened international institutions and eroded deference to norms such as respect for human rights. What unfolds in Guantánamo Bay or Gaza, Palestine does more than hurt the individuals unjustly subject to illegal torture or civilians slaughtered by the thousands; it raises the global public’s tolerance for such abhorrent acts by having them unfold in the heart of the democratic West.

Understanding what happened in the Middle East

The book does not argue that democracy was bound to flourish in the Middle East if the US had not subverted the nascent democratic and anticolonial movements. Rather, America’s military intervention, its backing of authoritarian, reactionary regimes and neglect of local concerns, and its imperial ambitions created conditions that undermined the lengthy, turbulent processes that constitutionalism, inclusive economic progress, and democratisation require. The political scientist Lisa Anderson notes that “it is usually decades, if not centuries, of slow, subtle, and often violent change” that create the conditions for meaningful state sovereignty.

Though the experiences of the Middle East are not wholly unique, some characteristics are specific to the region, such as its contiguity to Europe and its vast quantities of petroleum, strategic waterways and markets which have proved irresistible to Western powers. Western powers have thus persistently intervened in the internal affairs of Middle Eastern countries as they have not in other parts of the world. This “oil curse” has triggered a similar geostrategic curse in the Middle East, pitting external and local powers against each other in a struggle for competitive advantage and influence. As the book explores, this convergence of curses has had far-reaching and lasting political and economic consequences for Middle Eastern states.

The book eschews historical determinism and offers a robust reconstruction of the international relations of the Middle East as well as social and political developments in the region. It also encourages us to reimagine the present in light of revisiting the past. In so doing, we can begin to see lost opportunities and new possibilities for healing and reconciliation.

Note: This excerpt from the introduction to What Really Went Wrong: The West and the Failure of Democracy in the Middle East by Fawaz A Gerges is copyrighted to Yale University Press and the author, and is reproduced here with their permission.

This book extract gives the views of the author, not the position of the LSE Review of Books blog, or of the London School of Economics and Political Science.

Read an interview with Fawaz A Gerges, “What really went wrong in the Middle East” from March 2024 for LSE Research for the World.

Watch Fawaz A Gerges interviewed by Christiane Amanpour about the US’s role in the Israel-Gaza war from December 2023 and by Fareed Zakaria about the prospect of a regional war in the Middle East from January 2024, both on CNN.

Main image: Secretary Dean Acheson (right) confers with Prime Minister Mohammed Mossadegh of Iran (left) at the Walter Reed Army Medical Center in Washington D.C., 1951. Credit: The Harry S. Truman library.

 

Why is violence against Australian women not rated as terrorism?

Published by Anonymous (not verified) on Wed, 01/05/2024 - 4:59am in

Weekend rallies highlighted the anger and fear of thousands of women and men about the ongoing violence against Australian women. It is a crisis, and it is occurring day and night in homes and suburbs across the country where police are struggling to keep up with reporting of male violence and too many offenders avoid Continue reading »

ACTU statement on Gaza

Published by Anonymous (not verified) on Tue, 30/04/2024 - 4:55am in

The Australian Union movement is a movement of peace and respect for all races and nationalities. We oppose war, racism, and oppression. We act in solidarity. The Australian Union movement is horrified by the escalating violence and death toll of civilians in Gaza. The ACTU reiterates its statements and resolution of 19 October 2023 and Continue reading »

Israeli AI ‘using WhatsApp data’ to target Gaza families for bomb strikes

‘Lavender’ AI set to prioritise hitting targets at home with their families and is said to be using WhatsApp data for its process – but how is Israel getting hold of it?

Israel’s AI system for targeting people for murder in Gaza uses WhatsApp data among its targeting criteria, according to a report in the Israeli 972 magazine and analysis by Paul Biggar of Tech for Palestine.

The platform is marketed as encrypted ‘end to end’, supposedly offering complete security, and WhatsApp told Middle East Monitor that:

WhatsApp has no backdoors and we do not provide bulk information to any government. For over a decade, Meta has provided consistent transparency reports and those include the limited circumstances when WhatsApp information has been requested. Our principles are firm – we carefully review, validate and respond to law enforcement requests based on applicable law and consistent with internationally recognized standards, including human rights.

However, a 2021 Freedom of Information Request to the FBI revealed that WhatsApp’s owner provides ‘near real-time’ information to US authorities – not the content of messages in most cases, but of who is sending and receiving messages:

WhatsApp will produce certain user metadata, though not actual message content, every 15 minutes in response to a pen register [a special type of federal request], the FBI says. The FBI guide explains that most messaging services do not or cannot do this and instead provide data with a lag and not in anything close to real time: “Return data provided by the companies listed below, with the exception of WhatsApp, are actually logs of latent data that are provided to law enforcement in a non-real-time manner and may impact investigations due to delivery delays.”

This potentially fits with reports in Israeli media that Israel is using an artificial intelligence platform named ‘Lavender’ to identify thousands of human targets in Gaza and flag them for an airstrike, with WhatsApp data forming a key part of the AI’s decision process, based on the WhatsApp connections of supposed ‘militants’ – and that the system is designed to kill large numbers of civilians. One source told 972 that when Lavender identifies a target, Israeli forces:

bombed them in homes without hesitation, as a first option. It’s much easier to bomb a family’s home. The system is built to look for them in these situations.

But of course, people are in WhatsApp groups of all kinds of topics and for all kind of reasons – and merely being in a group which has a ‘militant’ member is no guarantee of any kind of ‘guilt’ – even if the right to resist occupation is disregarded, as Israel, the US and UK do.

This pattern raises the possibility that Israel is obtaining WhatsApp data, whether directly or from the US government. Another possibility is that Israel is accessing the data through the notorious ‘Pegasus’ hacking programme that has been shown to target WhatsApp users, hijacking their phones through WhatsApp even, in the later Pegasus versions, if they don’t open any suspicious links. Journalists, politicians, human rights activists and others are known to have been hacked by governments using the software, including its use by the Saudis against dissident Saudi journalist Jamal Khashoggi.

So serious was the issue that in 2021 tech firm Apple sued NSO, the maker of Pegasus, for targeting Apple users. NSO claimed that the software is used only against ‘terrorists’ – as which Israel, the UK, US and some others have designated Palestinian resistance groups – but there is clearly no guarantee that the definition of ‘terrorist’ is not extended in practice to anyone targeted by Israel. Biggar has accused WhatsApp’s owners of breaking international law and violating human rights.

Facebook, which belongs to the same Meta parent group as WhatsApp, has been accused of shutting down the circulation of pro-Palestinian and anti-Zionist posts and treating the term ‘Zionist’ as hate speech. In 2020, the company admitted changing its algorithms to filter out left-wing news and analysis from users’ feeds while allowing right-wing propaganda to flow unchecked.

However Israel is accessing the WhatsApp data it is said to be using to target Palestinians and their families, undoubtedly a war crime, the news that it is doing so is a warning for those who dissent from Establishment narratives and use ‘private’ messaging services to do so.

Meta continued its statement to Middle East Monitor:

Our principles are firm – we carefully review, validate and respond to law enforcement requests based on applicable law and consistent with internationally recognized standards, including human rights.

The US and UK governments, however, continue to insist that Israel is following international law and recognised human rights standards, even as it murders tens of thousands of civilians, mostly women and children.

If you wish to republish this post for non-commercial use, you are welcome to do so – see here for more.

The learned solution: Fix problems with violence

Published by Anonymous (not verified) on Mon, 29/04/2024 - 4:53am in

Are you well-armed, fired up, pitchfork to hand? The quarry is elusive, his background suspect but we know his name – DV. Are we getting closer? Every case is searingly awful but overall there have apparently been changes, with Crikey using Australian Institute of Health and Welfare data to claim domestic homicide rates have fallen: Continue reading »

UN rights chief demands international probe of mass graves near Gaza hospitals

Published by Anonymous (not verified) on Fri, 26/04/2024 - 4:50am in

“Hospitals are entitled to very special protection under international humanitarian law,” said Volker Türk, the United Nations high commissioner for human rights. The United Nations’ human rights chief on Tuesday called for an international investigation into mass graves discovered at two Gaza hospitals that Israeli forces recently assailed and destroyed, further imperilling the enclave’s barely Continue reading »

Pages