Telegram RegisterThe public register of Telegram

Channel

Котатограм: блог разработки

@kotatogram_dev_ru

On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry

282subscribers

+0 since we began measuring on 6 August 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1002138793580
TypeChannel
Username@kotatogram_dev_ru
DescriptionБлоги разработки Kotatogram. Основной канал: @kotatogram_ru
Created1 January 2024measured — dated from the channel’s first post
First recorded6 August 2026
Last confirmed live7 August 2026
Measurements held2
On Telegramt.me/kotatogram_dev_ru

Growth

2826 Aug 2026, 21:31 — 282 subscribers6 Aug 2026, 23:18 — 282 subscribers6 Aug 2026, 21:316 Aug 2026, 23:18
2 measurements taken within a single day. Dots are measurements; the straight line between them is drawn to join them, not to claim we know the path taken in between — snapshots are recorded only when a count changes, so gaps mean “no change observed”, never “interpolated”. The vertical axis spans 281–283 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
6 Aug 2026, 23:18282no change
6 Aug 2026, 21:31282first reading

Engagement

16 posts held, back to 1 January 2024the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 1 pageof Telegram’s post history, 20 posts per page.

Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 16 posts for this entry, the most recent from 13 March 2024. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Photos
4
Links
8

Lifetime counters from Telegram’s own channel header, read 6 August 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.

Reaction mix

139 reactions across 12 posts, in 14 distinct kinds. The most used accounts for 36.0% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
👍5036.0%
2518.0%
❤‍🔥1812.9%
🔥1410.1%
🤡107.19%
🎉53.60%
🤯53.60%
👏32.16%
👻21.44%
🖕21.44%
🤔21.44%
👎10.719%
💘10.719%
😨10.719%

No sentiment is inferred, and none should be read in. This table is ordered by count and by nothing else. Emoji do not carry stable meaning across languages or communities — 🙏 is thanks in one channel and mourning in another — so we publish which ones were pressed and how often, and pass no judgement on what an audience meant by them.

Precision. Telegram publishes reaction counts per emoji and short-forms each one — 4.34K, 1.2M — so any single kind at or above 1,000 reaches us at three significant figures, and only counts below 1,000 are exact. The shares above are ratios of those figures and carry the same error. This is also why the total here can differ slightly from a reaction total printed elsewhere on the page: both are sums of the same rounded parts, taken over samples with different edges.

Coverage. Reactions were read on 12 of the 16 sampled posts in this sample. Summed by Telegram’s own count on each post — not by adding up the per-emoji breakdown above — those same posts carry 139reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 16 most recent posts we hold, published 1 January 2024 to 13 March 2024, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.

Recent posts

13 Mar 2024, 21:33 UTC≈5,400 views57 reactionsread 6 August 2026

Новый билд на основе беты 4.15.3, в которой главное изменение — Instant View. https://t.me/KotatogramTestVersions/17

👍34🤡74🔥4👏3👻2🖕2😨1

12 Mar 2024, 03:05 UTC≈4,920 views13 reactionsread 6 August 2026

Новый тестовый билд и новая ветка. Из фиксов только количество аккаунтов (так как это 32-битный билд, их должно быть 10). Сам фикс, правда, не проверял. https://t.me/KotatogramTestVersions/16

❤‍🔥10🤡3

11 Mar 2024, 22:32 UTC≈3,330 views12 reactionsread 6 August 2026
Photo

Обновил исходники до 4.15.1, выложу после тестового билда. Так как версия уже выходит за пределы 4.14, а создавать на каждую версию ветку не хочется, чтобы не раздувать репозиторий, эта ветка будет называться patches-track-wip. Также, чтобы сократить вес репозитория, я планирую реорганизовать ветки patches-track*. Как это выглядит сейчас: — patches-track: TD 4.1.1 — patches-track-old: TD 3.5.2 — patches-track-4.8

❤‍🔥81👍1💘1🔥1

2 Feb 2024, 04:30 UTC≈2,550 views15 reactionsread 6 August 2026

Новый тестовый билд с теми фиксами, что я писал выше. Чинить ещё много, но надеюсь, без вылетов. https://t.me/KotatogramTestVersions/15

9🤯5👎1

2 Feb 2024, 04:15 UTC≈2,180 views4 reactionsread 6 August 2026

Починил скрытие и показ закреплённых сообщений в меню, однако всё не так гладко, как хотелось бы. В текущем тестовом билде нажатие на "Скрыть закреплённое сообщение" в меню "три точки" приведёт к вылету. В следующем тестовом билде это будет исправлено, и работать как надо. Однако кнопку "Скрыть" в окне, которое появляется по нажатию крестика на панели закреплённых сообщений, починить мне пока не удалось. Но по крайн

4

1 Feb 2024, 22:31 UTC≈1,610 views9 reactionsread 6 August 2026

Ветка patches-track-4.14 теперь обновлена до 4.14.12. Без багфиксов пока что, к сожалению, но зато с тегами в сохранённых. https://t.me/KotatogramTestVersions/14

🔥9

2 Jan 2024, 12:10 UTC≈1,730 views6 reactionsread 6 August 2026

Ну и раз уж настройка скругления есть (пусть и не доделанная), расскажу, как она работает. Сейчас пока что скругление контролируется в JSON-файле (Настройки > три точки > Показать файл настроек). В релизе это будет дополнено слайдером в настройках. Новые опции: — userpic_corner_radius, целое число от 0 до 50: процент скругления для всех чатов (0 — квадрат, 50 — круг). По умолчанию 50. — userpic_corner_radius_forum,

6

2 Jan 2024, 11:52 UTC≈1,490 viewsread 6 August 2026

Другие баги, которые присутствуют сейчас, и о которых я точно знаю: — «Показать/скрыть закреплённое сообщение»: вылет по нажатию — Кнопка «Недавние действия» в профиле: не реагирует — Правый клик по неактивному аккаунту в главном меню: вылет — Папки: баг с премиум-лимитами Визуальные недочёты: — Иконки, выбивающиеся из общей стилистики: отложенные сообщения, уведомления (в шапке профиля), настройки Kotatogram — Сме

2 Jan 2024, 11:35 UTC≈1,340 views3 reactionsread 6 August 2026

Также напомню про баг автозагрузки, который до сих пор присутствует. Однако я нашёл способ это временно обойти для конкретного чата: достаточно открыть один раз общие медиа. Конечно же, к релизу такой ужас будет исправлен, либо где-нибудь в самой автозагрузке, либо сборкой с LTO (которая, судя по всему, опять будет часов на 5).

👍3

2 Jan 2024, 11:16 UTC≈1,240 views1 reactionsread 6 August 2026
Photo

Считаю должным лишний раз напомнить, что лучше ставить этот билд отдельно от основного с отдельным профилем. Telegram Desktop не поддерживает понижение версии профиля: если вы попробуете запустить профиль с нового Telegram Desktop на старом, он просто сбросится и вам придётся перелогиниваться заново. Версия Telegram Desktop, на которой основан Kotatogram, указана в самом низу главного меню.

👍1

2 Jan 2024, 10:39 UTC≈1,300 viewsread 6 August 2026

Новая ветка готова вместе с собранным с неё тестовым бидом. https://t.me/KotatogramTestVersions/13

2 Jan 2024, 06:43 UTC≈1,320 views6 reactionsread 6 August 2026
Photo

У меня есть две новости, хорошая и плохая. Хорошая: есть первый успешный билд на версии TD 4.14. Плохая: актуальная версия — 4.14.1... Но надеюсь, что там не настолько сложно будет обновлять.

👍4🤔2

Showing the 12 most recent of 16 posts we hold for @kotatogram_dev_ru. View and reaction counts are the latest single reading for each post, not a live figure, and a recent post is still accumulating both. A view count marked was rounded by Telegram before we ever saw it — t.me prints views in full below 1,000 and to three significant figures above, so ≈1,200,000 means somewhere between 1,150,000 and 1,249,999. Unmarked counts are exact. Text is reproduced from the public post preview and truncated for length.

Citation-graph rank

Citation-graph rank — 723,566 of 1,183,361entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.

Mentions

Named by 1 registered channel — every channel on the register whose own posts have named this one, by its current username or any other username it currently holds, merged from two separately captured readings of the same fact so a namer caught by only one of them is not missed and a namer both caught is not counted twice. A username this channel has since dropped is not matched — that handle may belong to someone else now, and crediting today’s namer to yesterday’s owner would misattribute it.

Named by

Channels on the register whose posts name this channel's handle.

Names

Channels on the register whose handles appear in this channel's posts.

A mention is a weaker signal than a forward and is counted separately for that reason — naming a channel is not republishing it, and a handle in a post body is easy to place deliberately. The post counts beside each row below are distinct posts in which the handle appeared, from posts we have read on both sides — the “Named by N registered channels” figure above is a different count, of distinct NAMING CHANNELS rather than posts, and is not the sum of the rows under it.

Cite this entry

A live page changes as we take new readings, so a citation should name the measurement it is based on, not just the URL. The line below cites the subscriber count as measured 6 August 2026 — this entry's latest reading, not the date you are reading this.

“Котатограм: блог разработки” (@kotatogram_dev_ru), 282 subscribers as measured 6 August 2026. Telegram Register, tgregister.com/channel/kotatogram_dev_ru.

Full measurement history, CC BY 4.0. Every reading this register holds for this entry, not just the latest one, as a dated, downloadable record: CSV · JSON. Free to use with attribution to tgregister.com. Each file carries its own generation timestamp, which is the figure to cite for exactly when the data was retrieved.