<?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: Anatoly</title>
    <description>The latest articles on Forem by Anatoly (@anatolyben).</description>
    <link>https://forem.com/anatolyben</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%2F3775871%2Fb0bfccf5-1d7c-4af6-bd0f-4d1157f9819c.jpeg</url>
      <title>Forem: Anatoly</title>
      <link>https://forem.com/anatolyben</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://forem.com/feed/anatolyben"/>
    <language>en</language>
    <item>
      <title>I manage 30+ Telegram groups. I tried every bot framework. Nothing worked. So I built my own.</title>
      <dc:creator>Anatoly</dc:creator>
      <pubDate>Tue, 31 Mar 2026 18:12:59 +0000</pubDate>
      <link>https://forem.com/anatolyben/i-manage-30-telegram-groups-i-tried-every-bot-framework-nothing-worked-so-i-built-my-own-khh</link>
      <guid>https://forem.com/anatolyben/i-manage-30-telegram-groups-i-tried-every-bot-framework-nothing-worked-so-i-built-my-own-khh</guid>
      <description>&lt;p&gt;I manage 30+ Telegram groups. I tried every bot framework. Nothing worked. So I built my own.&lt;/p&gt;

&lt;p&gt;As the community grew, so did the noise. Spam attempts, job scams, crypto solicitations, cross-chat abuse. Manual moderation doesn’t scale — it creates latency, inconsistency, and burnout.&lt;/p&gt;

&lt;p&gt;So I built a framework instead.&lt;/p&gt;

&lt;p&gt;The answer was a pipeline. Every incoming message flows through a sequence of stages you define, executed in order. One chat or thirty — every message gets the same predictable treatment. No handler fires out of turn. No rule gets skipped.&lt;/p&gt;

&lt;p&gt;Every stage has access to the full context — it knows exactly which chat it’s in, who sent the message. Stages can pass data to each other, dispatch actions like banning a user, terminate the pipeline early, or trigger hooks for logging and observability. The whole thing is observable, controllable, and composable.&lt;/p&gt;

&lt;p&gt;Built this running 30+ groups. If you’re building on top of Telegram at scale — moderation, automation, workflow — this is the foundation I wish I had.&lt;/p&gt;

&lt;p&gt;GitHub → &lt;a href="https://github.com/anatolyben/Telegram-Automation-Framework" rel="noopener noreferrer"&gt;https://github.com/anatolyben/Telegram-Automation-Framework&lt;/a&gt;&lt;/p&gt;

</description>
      <category>architecture</category>
      <category>automation</category>
      <category>showdev</category>
      <category>sideprojects</category>
    </item>
  </channel>
</rss>
