3 measurements taken within a single day, net -1. 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 418–419 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)
Subscribers
Change
6 Aug 2026, 23:18
418
-1
6 Aug 2026, 19:32
419
no change
6 Aug 2026, 00:48
419
first reading
Engagement
20 posts held, back to 16 October 2025 — the 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.
ERR · 30 days
65.8%
avg views ÷ 418 subscribers
Avg views / post
275
1 post measured
Reaction rate
8.73%
reactions ÷ views · ER floor
Posts in window
1
of 20 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.
What these figures were computed from
Window
Rolling 30 days · latest post in window 17 July 2026
Posts held
20 (16 October 2025 – 17 July 2026)
Views total
275
Reactions total
24
Forwards / comments
not exposed by the public surface — not measured, not estimated
Readings taken
6 Aug 2026, 19:32 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
458 reactions across 20 posts, in 8 distinct kinds. The most used accounts for 39.5% of them.
Every reaction kind recorded on the sample, most used first
Reaction
Count
Share
Share, drawn
👍
181
39.5%
🍾
81
17.7%
👨💻
71
15.5%
❤
50
10.9%
custom 5379555115013274080
46
10.0%
🤡
25
5.46%
👎
3
0.655%
custom 5379599460550607648
1
0.218%
Custom emoji. 2 of the rows above are Telegram custom emoji, which the public preview renders as an element carrying only a numeric id — no character, and no image we can reach. The id is printed as-is rather than substituted with a look-alike glyph, because a stand-in would be our invention showing where a measurement should be. The counts beside them areTelegram’s.
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 20 of the 20 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 458reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 20 most recent posts we hold, published 16 October 2025 to 17 July 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.
Telegram Stars
Stars received
77
across the posts below
Posts paid on
16
of 20 we hold a reading for · 80%
Most on one post
55
single highest reading
A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @iamtemporary. Telegram publishes the count on the public post preview alongside ordinary reactions, and this register reads it there. It is the only figure on this site that measures money moving rather than attention.
Stars are not reactions, and the two are never added. They are rendered in the same strip on Telegram and counted in the same shape, but one is a tap and the other is a purchase. The reaction totals and the engagement rate elsewhere on this page exclude every figure in this section, and no rate here is computed against a reaction count.
This is not revenue, and we publish no currency figure. What a Star costs a reader and what it pays a channel are different numbers, Telegram takes a share we cannot observe, and the terms have changed. Converting a Star count into money would be an estimate dressed as a measurement, so the count is where we stop.
Counted over the 20 most recent posts we hold for this entry, published 16 October 2025 to 17 July 2026. Star counts above 1,000 reach us in Telegram’s short form and carry the same three-significant-figure rounding as everything else on this page.
В последние месяцы качество результатов работы кодинг-агентов очень сильно выросло — это подчеркнул даже создатель ClickHouse в недавнем интервью.
Агентами я пользуюсь уже больше года, начиная с GitHub Copilot в мае прошлого года. Это, конечно, сильно всё поменяло, но долгое время требовало слишком большой вовлечённости от меня как от оператора. Сильно больше усилий я прикладывал к описанию контекста, допиныванию аг…
Зацените — недавно подумал, что можно отобразить рынки полимаркета в виде Heatmap (вы наверняка видели подобное для изменения цен акций по секторам) и вот накидал за пару дней: poly-heatmap.dkeysil.com
В таком отображении можно увидеть как меняются настроения в политике (США и Иран, например) или довольно интересно смотреть на спортивные исходы.
Сайт получился очень динамичным и активным, благодаря тому, что постоя…
Привет! Я тут в свободное время делал приложение с идеей связать инвестиции в стоки и блокчейны. Уже довольно много классной инфраструктуры есть связанной с традиционными рынками, при этом мое видение, что децентрализованные финансы сильно круче и эффективные древних централизованных решений.
Большие игроки признают, что именно децентрализованные финансы позволяют определять цену активов вне рабочих часов биржи (воо…
На выходных решил заобноардиться в новую тулу для вайбкодеров — superset.sh (conductor.build я использовать не могу, потому что не мак)
К сожалению, все эти модные программы вокруг клод кодов и кодексов очень сильно скофусированы на пользователей Mac OS, а у меня Omarchy. И это в целом проклятый сетап, тут не самый популярный дистрибутив (Arch), еще менее популярный оконный менеджер (Hyprland) — ну и вишенка на торт…
Поймал Claude Code цитировании очевидного AI-слопа как источник
Работал с Claude Code, скинул документацию, попросил разобраться. Модель прочитала — и пошла гуглить сама. Нашла форум. Я случайно открыл из любопытства.
Форум выглядит как настоящий: темы, обсуждения, реплаи. Но что-то зацепило. Пользователи: layer2_liza, security_sophia, blockchain_bryan, ethereum_emma. Паттерн [роль]-[имя]. У каждого поста ровно 4 р…
Я тут попытался применить инстурменты, которые генерируют видео — и все получилось ну очень плохо.
Поэтому хочу узнать, получалось ли у вас сгенерировать достаточное количество материала, чтобы склепать качественное видео? Или можете порекомендовать инфлюенсеров, которые занимаются производством ИИ видео контента.
Мой опыт:
- Природа генерируется добротно, широкие кадры, пролеты на дронах
- Как будто качество гене…
А еще сильная фича Clawdcode, которую много кто сейчас пытается решить через самописные скрипты — это луп, где клод код может сам по себе работать очень долго. И вот это фантастическая фича, которую я очень жду в официальной сборке.
Хочется, чтобы Claude Code добавил полноценную оркестрацию субагентов (чтобы он сам ими управлял) + сам регулярно пробуждался и пытался исполнить необходимые задачи (например раз в день …
Сейчас твиттер кипит про Clawdbot, но я не про него
Вообще я уже совершал несколько попыток использовать различные обертки и дополнения над сырым Claude Code и каждый раз они заканчивались одинаково — я от них отказывался, а в целом про них уже через пару недель забывали. Поэтому сейчас я следую идеи чистого Claude Code, ведь если какая-то фича действительно достойна внимания публики — команда ее быстренько навайбко…
Сегодня хочу рассказать про первую боль от разработки на Solana — аренда места под смарт контракты.
Аренда, кстати, это совсем неправильное слово для этой механики. В данном случае это депозит, ведь его можно вернуть в полном объеме и в любой момент при закрытии аккаунта.
Интересно сравнить эту механику с TON'ом, где тоже есть аренда. Но в ТОНе:
1. Реально аренда, ты платишь за место, которое занимает смарт контрак…
Совершенно случайно осознал, что примерно 70% моего ютуб фида продолжительное время были блогеры из города, где я родился и вырос — Санкт-Петербурга
Автоблогинг — Академег
Обозоры еды / готовка — Обломофф
Различный развлекательный контент — Хованские и его подсосы
Баттлрэп это тоже, естественно, про Питер
Даже майнкрафт я смотрел в основном у Лололошки
И еще множество разных блогеров — Темная Фаза, Star Factory, Ай…
👍15👨💻5🍾3👎1
Showing the 12 most recent of 20 posts we hold for @iamtemporary. 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.
Stars beside a post are paid reactions — Telegram Stars, bought with money and spent on that post. They are a different unit from reactions and are never added to them, here or anywhere else on this page.
Citation-graph rank
Citation-graph rank — 580,155 of 1,151,006entries 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.
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 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.
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.
Handles this channel named that no longer answer
Dead references
1
handles named in this channel’s posts, vacant today
Evidenced gone
0
we ourselves saw one of these resolve, at some point
Never seen alive
1
vacant every time we have ever looked
@iamtemporary named 1 handle that resolve to nothing today. That is a fact about the reference, not necessarily a fact about the handle’s history — see the two groups below.
Most of these may never have existed as a live channel at all.A handle a channel names can be a typo, an aspirational name nobody registered, or a channel that was already gone before this one ever mentioned it. Unless a row below is marked evidenced, all we know is that it references a handle that is not a live channel today — not that anything “died”. How this is measured.
Never seen alive
References a handle that is not a live channel — we have no record it ever was one.
@nlevshitstelegram named in 1 post, 8 August 2026 – 8 August 2026
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.
“Кисель” (@iamtemporary), 418 subscribers as measured 6 August 2026. Telegram Register, tgregister.com/channel/iamtemporary.
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.
