Telegram RegisterThe public register of Telegram
Telegram profile photo for ··• Серёжа печатает

Channel

··• Серёжа печатает

@seryozha_typing

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

2,378subscribers

+4 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of 1,000–3,162.

Register entry

Telegram ID-1001457657332
TypeChannel
Username@seryozha_typing
CreatedBetween 1 April 2019 and 30 September 2021— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live14 August 2026
Measurements held4
Confirmed unchanged1 time, most recently 14 August 2026
On Telegramt.me/seryozha_typing

Growth

2,3742,3782,3767 August 2026 — 2,374 subscribers7 August 2026 — 2,376 subscribers10 August 2026 — 2,377 subscribers14 August 2026 — 2,378 subscribers7 August 202614 August 2026
4 measurements spanning 7 days, net +4. 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 2,373–2,379 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
14 Aug 2026, 02:152,378+1
10 Aug 2026, 09:562,377+1
7 Aug 2026, 11:352,376+2
7 Aug 2026, 01:022,374first reading

Engagement

22 posts held, back to 27 July 2026the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 2 pagesof Telegram’s post history, 20 posts per page.

ERR · 30 days
28.0%
avg views ÷ 2,378 subscribers
Avg views / post
665
22 posts measured
Reaction rate
1.68%
reactions ÷ views · ER floor
Posts in window
22
of 22 held

ERR is average views per post over the last 30 days divided by subscribers, the definition TGStat uses, so this figure is comparable with the one you will see elsewhere. It falls structurally as a channel grows: a high ERR on a small channel and a low one on a large channel describe reach mathematics, not quality. We publish the figure and the sample it came from and pass no verdict on it.

ER is defined industry-wide as (forwards + reactions + comments) ÷ views— note the denominator is views, not subscribers. Telegram’s public web preview carries views and reactions but not forward or comment counts, so the reaction rate above is the reactions term only and is therefore a floor: the true ER for this channel is higher by an amount we have not measured and will not estimate. It is computed over the 21 of 22 measured posts that carry a reaction reading, and over those same posts' views.

What these figures were computed from
WindowRolling 30 days · latest post in window 7 August 2026
Posts held22 (27 July 20267 August 2026)
Views total14,634
Reactions total234
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken7 Aug 2026, 16:37 UTC

Views are a single reading per post, taken at the time above. A post published in the last day or two is still accumulating views, which pulls the 30-day average down slightly. That is a property of the standard definition rather than a fault in it, so we keep the definition rather than “correcting” the number into something nobody can reproduce.

Precision. Telegram publishes view counts on its public widget in short form — 8.12K, 3.7M — so any reading at or above 1,000 reaches us rounded to three significant figures, and only counts below 1,000 are exact. Averages and rates derived from them are shown to the same precision rather than to the unit: a figure like 3,701,250 would assert digits nobody measured.

Reaction counts are published per emoji and rounded the same way, so a total below 1,000 is exact and a larger one is a sum that may carry a rounded component from each emoji above 1,000. Because it is a sum, it does not look rounded — read a large reaction total as three significant figures per contributing emoji rather than as the figure it prints.

Reaction mix

234 reactions across 21 posts, in 11 distinct kinds. The most used accounts for 52.1% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
😁12252.1%
5021.4%
🔥2510.7%
💩93.85%
😱93.85%
👍83.42%
❤‍🔥31.28%
🥰31.28%
👀20.855%
👏20.855%
🤩10.427%

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 21 of the 22 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 234reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 22 most recent posts we hold, published 27 July 2026 to 7 August 2026, 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

7 Aug 2026, 12:31 UTC231 views11 reactionsread 7 August 2026
Photo

Photo, posted without a caption

😁11

Signed Серёжа

7 Aug 2026, 05:08 UTC298 views13 reactionsread 7 August 2026
Photo

Закончили первый AI-интенсив и собрали обратную связь. Мы взяли 22 человека! До конца дошли 10, проект сделали 6 человек. За месяц. Ребята воткнули нам 8 из 10, что неплохо. Что делали? Один участник развивал промышленное ПО для управления автоматом расстановки компонентов на печатные платы: камеры, OpenCV, микросервисная архитектура, калибровки, планировщик движений и веб-интерфейс оператора. Другой сделал мод-

🔥85

Signed Серёжа

6 Aug 2026, 13:03 UTC348 views2 reactionsread 7 August 2026

https://t.me/ivan_plastun_channel/24 Хорошая мысль, кстати. Причём это частая ошибка руководителя и команды в целом. Психологически нам легко, когда уютно. Мы можем не обращать внимание на то, что мы застоялись, в тот момент, когда нам кажется, что вокруг всё круто. Именно поэтому надо стараться выходить из зоны комфорта и стараться трезво оценивать ситуацию и результаты. А также челенджить самих себя и команду. Н

👍2

Signed Серёжа

6 Aug 2026, 08:10 UTC418 views12 reactionsread 7 August 2026
Photo

Сделал вам мем

😁10💩2

Signed Серёжа

6 Aug 2026, 05:20 UTC431 views6 reactionsread 7 August 2026
Photo

Недавно проходил Yandex AI Studio Series — это серия образовательных лекций по ИИ. Там было много про инфру AI Studio, очевидно, но было и очень много теоретической информации, кторая максимально универсальна. Я смотрел и делал конспекты. А сейчас собрал всё в одно место с расшифровками, скринами презентаций. Вышло довольно комапактно, но полезно. Пользуйтесь https://popovs.tech/blog/yandex-ai-studio-series

6

Signed Серёжа

4 Aug 2026, 08:07 UTC489 views2 reactionsread 7 August 2026

Борис ночью пофиксил образ на brew, теперь его можно ставить и обновлять одной командой. И я добавил поддержку OpenCode, по просьбе чата. Теперь он считает и его тоже. https://github.com/tsergeytovarov/ai-stats

👍1🔥1

Signed Серёжа

3 Aug 2026, 14:22 UTC553 views16 reactionsread 7 August 2026

Наблюдение. ChatGPT неплохо раскладывает таро и нотальную карту.

😁16

Signed Серёжа

3 Aug 2026, 09:18 UTC568 views2 reactionsread 7 August 2026

Короче, вот это реально тема. Я прям вчера тестировал много, и оно работает. Сильно быстрее и экономнее, чем до этого. Тут сошлось пару факторов. 1. Переход исключительно на риск-тест. То есть он покрывает тестами не все 100% строк кода, а только там, где есть риски. 2. В конце той недели OpenAI сами пофиксили страсть к оверинженирингу и прожорливость. Как итог — за 2 дня почти неприрывной работы по 3 проектам 30

👀2

Signed Серёжа

2 Aug 2026, 14:38 UTC580 views5 reactionsread 7 August 2026

А ещё сеттинги я тоже обновил и починил. Это которые про базове настройки. Зачем? Агенты совсем стали умными, и все прошлые штуки загоняют их в бесконечные циклы, слишком много тестов и ревью. Я вычистил это и на уровне глобальных настроек и на уровне того, как оно работает с superpowers. у меня стало прям заметно шустрее https://github.com/tsergeytovarov/ai-settings

🔥31💩1

Signed Серёжа

2 Aug 2026, 13:35 UTC531 views3 reactionsread 7 August 2026
Photo

у меня кстати день обновлений) в Burn приехало обновление, которое теперь все лимиты показывает в риалтайме ну и там много мелких улучшений, по скорости, производительности и вот это всё.

👍3

Signed Серёжа

2 Aug 2026, 08:45 UTC531 views17 reactionsread 7 August 2026

Короче я вчера ездил проводить два воркшопа по ИИ для ребят. Вывода 3. 1. Как всегда сложнее всего нащупать стартовый средний уровень, что у всех начало быстро получаться что-то делать. 2. Смотреть как у ребят начинает что-то получаться за полтора часа — бесценно. 3. Я слишком стар для того, чтобы вести два воркшопа в один день. Вывод три самый важный я думаю)

😁14❤‍🔥3

Signed Серёжа

31 Jul 2026, 14:09 UTC583 views8 reactionsread 7 August 2026
Photo

Так, чтиво на выходные. Я обещал написать материал про фронтенд, но пока писал, понял что оно все выглядит так сложно, что никто не будет это делать. Но на самом деле — не всё сложно. Более того, достаточно сделать один раз в проекте и дальше наслаждаться. Так получился материал. Я выложил его на VC. И я выложил его в свой блог. https://vc.ru/ai/3054786-kak-sdelat-sovremennyj-frontend-bez-neiroslopa https://popovs

8

Signed Серёжа

Showing the 12 most recent of 22 posts we hold for @seryozha_typing. 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 — 318,319 of 1,481,217entries 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.

Forward network

Republished by

Channels on the register that have forwarded this channel's posts into their own feed.

Republishes

Channels on the register whose posts this channel has forwarded.

Built only from forwarded posts we have actually read, on both sides. Coverage is early and deliberately incomplete: a missing link means we have not read the post that would prove it, never that the relationship does not exist. Counts are distinct forwarded posts observed, so they only ever go up as we read more.

Mentions

Named by 3 registered channels — 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.

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 14 August 2026 — this entry's latest reading, not the date you are reading this.

“··• Серёжа печатает” (@seryozha_typing), 2,378 subscribers as measured 14 August 2026. Telegram Register, tgregister.com/channel/seryozha_typing.

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.