<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>Forem: Pavel Glazkov</title>
    <description>The latest articles on Forem by Pavel Glazkov (@cyberextreme).</description>
    <link>https://forem.com/cyberextreme</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F3793650%2F8bdef13a-a191-4b24-a2ff-851b65ff8e12.jpg</url>
      <title>Forem: Pavel Glazkov</title>
      <link>https://forem.com/cyberextreme</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://forem.com/feed/cyberextreme"/>
    <language>en</language>
    <item>
      <title>I built a task manager inside Telegram — and censorship made me a better engineer</title>
      <dc:creator>Pavel Glazkov</dc:creator>
      <pubDate>Thu, 26 Feb 2026 06:16:28 +0000</pubDate>
      <link>https://forem.com/cyberextreme/i-built-a-task-manager-inside-telegram-and-censorship-made-me-a-better-engineer-2l19</link>
      <guid>https://forem.com/cyberextreme/i-built-a-task-manager-inside-telegram-and-censorship-made-me-a-better-engineer-2l19</guid>
      <description>&lt;p&gt;I got tired of switching between Telegram and our project management tool dozens &lt;br&gt;
of times a day. The team was already in Telegram — why wasn't the work?&lt;/p&gt;

&lt;p&gt;So I built iTasks: a full task tracker that runs as a Telegram Mini App. &lt;br&gt;
No install, no sign-up — just open the bot and start working. Kanban board, &lt;br&gt;
time tracking, file attachments, workflow automation, voice rooms for the team.&lt;br&gt;
Built on Node + React.&lt;/p&gt;

&lt;h2&gt;
  
  
  Why Telegram specifically?
&lt;/h2&gt;

&lt;p&gt;Telegram is the closest thing we have to a truly independent platform. No &lt;br&gt;
predatory commissions, no arbitrary rule changes overnight, no app store &lt;br&gt;
gatekeeping. It's always in your pocket, and I genuinely believe it's becoming &lt;br&gt;
the global WeChat — a super-app that people live inside of.&lt;/p&gt;

&lt;p&gt;Building on Telegram felt like building on solid ground.&lt;/p&gt;

&lt;h2&gt;
  
  
  Then reality hit
&lt;/h2&gt;

&lt;p&gt;I assumed the hard parts would be product decisions. I was wrong.&lt;/p&gt;

&lt;p&gt;The real challenge turned out to be &lt;strong&gt;digital geography&lt;/strong&gt;.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Problem #1: CDN blocked.&lt;/strong&gt;&lt;br&gt;
I was using DigitalOcean Spaces for file attachments. Turns out DigitalOcean &lt;br&gt;
is blocked in certain countries. Users couldn't load their own attachments.&lt;/p&gt;

&lt;p&gt;The fix: I built a proxy layer — all media now routes through the app server &lt;br&gt;
itself when direct CDN access fails. Automatic, transparent to the user.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Problem #2: Telegram voice calls blocked.&lt;/strong&gt;&lt;br&gt;
Russia blocks Telegram's native voice infrastructure. A "built-in voice rooms" &lt;br&gt;
feature that silently doesn't work is worse than no feature at all.&lt;/p&gt;

&lt;p&gt;The fix: I deployed my own &lt;a href="https://livekit.io" rel="noopener noreferrer"&gt;LiveKit&lt;/a&gt; servers. LiveKit is &lt;br&gt;
an open-source WebRTC infrastructure — self-hosted, fully under my control. &lt;br&gt;
Now voice rooms work independently of Telegram's own voice infrastructure. &lt;br&gt;
Russian users can actually talk to their teammates.&lt;/p&gt;

&lt;p&gt;What started as a product feature became a small piece of &lt;br&gt;
censorship-circumvention infrastructure.&lt;/p&gt;

&lt;h2&gt;
  
  
  Where it is now
&lt;/h2&gt;

&lt;p&gt;iTasks launched recently and is in active user testing. A few teams have been &lt;br&gt;
using it daily for three months — including our own team, which has been the &lt;br&gt;
most honest QA process imaginable.&lt;/p&gt;

&lt;p&gt;Free forever for teams up to 3 people. For larger teams — PRO at 499 Telegram &lt;br&gt;
Stars/month.&lt;/p&gt;

&lt;p&gt;If you're building on Telegram or dealing with the same geo-blocking headaches, &lt;br&gt;
I'd love to compare notes. And if you want to try it — @iTasksBot on Telegram.&lt;/p&gt;

&lt;p&gt;→ Landing: &lt;a href="https://itasksbot.com" rel="noopener noreferrer"&gt;itasksbot.com&lt;/a&gt;&lt;br&gt;&lt;br&gt;
→ Bot: &lt;a href="https://t.me/iTasksBot" rel="noopener noreferrer"&gt;t.me/iTasksBot&lt;/a&gt;&lt;/p&gt;

</description>
      <category>telegram</category>
      <category>webdev</category>
      <category>productivity</category>
      <category>startup</category>
    </item>
  </channel>
</rss>
