← Telegram bot dev
Telegram bot dev — заказы за 2026-08-29
9 заказов за этот день
- 19:53 (and the worst thing is that you can't use the general class for every block, you got to use all the different classes for different blocks. viva aiogram's vibecoding and pydantic ig.)
- 19:38 I'm trying to find a way to use the blocks without defining classes, because that's the current implementation of aiogram, with makes their use the slowest
- 19:38 aiogram. etc always overabstract things to much imo, thats why i use my own library which just uses TypedDicts for input objects
- 19:38 aiogram = your server not telegram server as original question. — and 1ms delay of your connection to telegram probably is slower than the trying to optimize this parse.
- 13:02 so then sharing aiogram is forbidden too or what?
- 13:02 Aiogram and other libs shared here are referenced by Telegram
- 11:55 Hi all! I’ve open-sourced the FlowCastle SDK for Telegram bots. It plugs into an existing grammY, Telegraf, aiogram or python-telegram-bot project and adds things like CRM, a shared support inbox, broadcasts and funnel analytics. It works as middleware: the bot token stays in your process, message text is filtered locally, and handlers don’t wait on FlowCastle network calls. There are runnable exa
- 11:40 Hi all! Writing bot code is fun. But code alone doesn't bring users, give support a shared inbox, or show which conversations convert. So I open-sourced an SDK that adds that layer — CRM, live chat, broadcasts, funnel analytics — to a Telegram bot you already have on grammY, Telegraf, aiogram or python-telegram-bot. Just middleware: your token never leaves your process, message text is filtered lo
- 08:55 Anyway, I may never have said this, but I will say that Telegram has given me more than I can even imagine, from the Telegram bot ecosystem to everything else. I say thanks to Telegram for everything.
📨 Получать такие лиды live →