Saturday, April 20, 2024

Iran Protests at Blocking of IRIB’s Social Network Accounts

The world service of the Islamic Republic of Iran Broadcasting (IRIB) has strongly denounced the blocking of its social network accounts on YouTube, Twitter, Google Plus, and Facebook, saying such moves are a sign of the impact of IRIB channels on the global media.

In a statement on Saturday, the IRIB World Service regretted that over the past few days, accounts of some of the World Service channels have been blocked on Facebook, Twitter, YouTube and Google+.

The administrators of these social networks claim these accounts have been blocked for misleading audiences by publishing false information, the statement said.

The IRIB World Service condemned the act, stating that it is a clear example of censorship and blocking the publication of facts and viewpoints on social networks.
“Independent media such as Press TV, Hispan TV, Al-Alam, Sahar, Al-Kawthar, etc.,

apart from releasing facts that the US government and its allies are reluctant to publish, have not committed any crime to be deserved to be blocked.”

The IRIB World Service once again rejected the claims raised by the Western media giants, pledging that these channels will continue to reflect the “voice of the voiceless”.

The IRIB World Service broadcasts programs in a variety of languages for audiences outside Iran. It runs a number of radio and television networks as well as numerous social media accounts and other online platforms.

In 2012, Britain’s media regulator Ofcom took Press TV off the air for what it called breaking of the UK’s broadcasting code.

The body revoked Press TV’s license after the English-language network broadcast confessions of a man named Maziar Bahari who was accused of spying for Western countries. Iranian officials responded to the decision at that time and called Ofcom “the media arm of the Royal family.”

› Subscribe

LEAVE A REPLY

Please enter your comment!
Please enter your name here

The reCAPTCHA verification period has expired. Please reload the page.

More Articles