The role of social media in the ongoing Ukraine-Russia crisis is becoming more and more important. Social media platforms also continue to take new decisions regarding the crisis. A new step came from Twitter regarding the ongoing attacks in the region.
Social media giant Twitter announced that it has suspended advertisements in Russia and Ukraine due to Russia’s invasion of Ukraine. The social media company wrote that the decision was made to make public safety information stand out.
Twitter will not display ads in Russia and Ukraine
In the informational post shared by Twitter, “We are temporarily pausing ads in Ukraine and Russia to ensure that critical public safety information is upgraded and that ads do not adversely affect that information. ” was stated.
Twitter, in addition to the ad restriction, has Russia’s access to Ukraine. He announced a few more steps related to the war he was waging against. Alongside the changes, the social network also created a digital security resource page to help users keep their information private.
In the tweet series he shared on Twitter, it was stated that bot accounts that shared false information about the war would be investigated. The platform said that tweets will be proactively reviewed to detect manipulation, and that it will also sanction content that presents misinformation about the conflict in Ukraine.
Twitter announced these changes as the third day of the Russian occupation entered. The company also underlined that the decisions were implemented quickly.
All social media services, including Twitter, are used as an important source of information about the war. It is also preferred by both the Ukrainian and Russian governments to disseminate information to the world.
For example, Ukrainian President Volodymyr Zelensky and other state institutions of the country inform the public by sharing tweets in both Ukrainian and English. Russia uses government-run Twitter accounts to share information.
You can share your views on the advertising decision taken by Twitter in the comments section and on the SDN Forum.
22010
