<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	
	>
<channel>
	<title>
	Comments on: Why Russia is turning against Telegram	</title>
	<atom:link href="https://theloop.ecpr.eu/why-russia-is-turning-against-telegram/feed/" rel="self" type="application/rss+xml" />
	<link>https://theloop.ecpr.eu/why-russia-is-turning-against-telegram/</link>
	<description>ECPR&#039;s Political Science Blog</description>
	<lastBuildDate>Fri, 20 Mar 2026 11:32:46 +0000</lastBuildDate>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	
	<item>
		<title>
		By: Michael		</title>
		<link>https://theloop.ecpr.eu/why-russia-is-turning-against-telegram/#comment-56011</link>

		<dc:creator><![CDATA[Michael]]></dc:creator>
		<pubDate>Fri, 20 Mar 2026 11:32:46 +0000</pubDate>
		<guid isPermaLink="false">https://theloop.ecpr.eu/?p=27186#comment-56011</guid>

					<description><![CDATA[This is a really compelling analysis, especially in showing how Telegram evolved from a useful wartime amplifier into something harder for the Kremlin to fully control.
That said, I wonder if framing the move primarily as an attempt to contain decentralized nationalism slightly underplays how deliberate this “messiness” was in the first place. For much of the war, Telegram didn’t just escape state control it actually seemed to serve it. The mix of official messaging, milbloggers, and “patriotic critics” arguably made pro-war narratives feel more dynamic and credible than top-down propaganda alone ever could.
What’s interesting is that this ecosystem allowed criticism but only of a certain kind. Attacks on military leadership or logistics were tolerated, even amplified, as long as they didn’t challenge Putin directly. In that sense, what looks like dissent often functioned as a pressure valve rather than a threat.
So the recent throttling of Telegram might not only be about fear of nationalist escalation. It could also reflect a shifting calculation: earlier in the war, decentralized voices helped with mobilisation and real-time adaptation. But in a longer, more politically sensitive phase especially with elections on the horizon that same openness starts to create coordination problems and unpredictability within the pro-regime camp.
From that perspective, this isn’t just containment it’s a move from a relatively flexible, networked model of control toward a more tightly managed and hierarchical one.]]></description>
			<content:encoded><![CDATA[<p>This is a really compelling analysis, especially in showing how Telegram evolved from a useful wartime amplifier into something harder for the Kremlin to fully control.<br />
That said, I wonder if framing the move primarily as an attempt to contain decentralized nationalism slightly underplays how deliberate this “messiness” was in the first place. For much of the war, Telegram didn’t just escape state control it actually seemed to serve it. The mix of official messaging, milbloggers, and “patriotic critics” arguably made pro-war narratives feel more dynamic and credible than top-down propaganda alone ever could.<br />
What’s interesting is that this ecosystem allowed criticism but only of a certain kind. Attacks on military leadership or logistics were tolerated, even amplified, as long as they didn’t challenge Putin directly. In that sense, what looks like dissent often functioned as a pressure valve rather than a threat.<br />
So the recent throttling of Telegram might not only be about fear of nationalist escalation. It could also reflect a shifting calculation: earlier in the war, decentralized voices helped with mobilisation and real-time adaptation. But in a longer, more politically sensitive phase especially with elections on the horizon that same openness starts to create coordination problems and unpredictability within the pro-regime camp.<br />
From that perspective, this isn’t just containment it’s a move from a relatively flexible, networked model of control toward a more tightly managed and hierarchical one.</p>
]]></content:encoded>
		
			</item>
	</channel>
</rss>
