in ,

LOVELOVE YES!YES!

Leftist Journalist Who Called For Conservatives To Be Censored Is Now Crying That He Got Censored

Share this:

A poor little lefty has learned the hard way that actions have consequences, and if you call for broad censorship then don’t cry when it comes for you.

The left-wing journalist is now expressing regret about calling for Silicon Valley to censor content after it happened to him.

Progressive reporter Jordan Chariton had the change of heart after YouTube took down one of his videos.

Chariton’s original advocacy for censorship occurred when he called for Big Tech giants to target anyone who questioned the legitimacy of the 2020 presidential election.

“EVERY media outlet that pushed this INSANE election fraud conspiracy for clicks should be taken off the air. They’ve incited a Civil War,” Chariton tweeted on January 6, the date of the Capitol breach.

However, after YouTube pulled video from his own channel featuring footage of the January 6 riot for violating the platform’s policies against “spam and deceptive practices,” the Chariton reversed his position.

“With time to reflect, & seeing Silicon Valley’s censorship onslaught, I regret this tweet made in [the] heat of moment,” the progressive journalist wrote. “Whether certain cable/YouTube outlets mislead audiences w/ dishonest claims lacking real evidence, they shouldn’t be targeted.”

Chariton noted that with the precedent having been set for blanket censorship, progressive content was also now being unfairly targeted, while pointing out that big left-wing networks with friendly YouTube ties like the Young Turks were not calling it out.

In a subsequent interview, the journalist noted that the purge of right-wing content was merely an excuse for YouTube to “get rid of” all content that questioned the consensus on subjects such as healthcare or U.S. foreign policy.

Chariton pointed out that big networks like CNN that carried the exact same footage from January 6 were not targeted at all by YouTube.

Subscribe
Notify of
guest

0 Comments
Inline Feedbacks
View all comments