Telegram RegisterThe public register of Telegram

Channel

C# Short Posts 🔞

@dimasshortposts

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

306subscribers

+5 since we began measuring on 7 August 2026

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

Register entry

Telegram ID-1001746342550
TypeChannel
Username@dimasshortposts
CreatedBetween 1 December 2021 and 30 April 2023— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded8 August 2026
Last confirmed live14 August 2026
Measurements held3
Confirmed unchanged1 time, most recently 14 August 2026
On Telegramt.me/dimasshortposts

Growth

301306303.57 August 2026 — 301 subscribers8 August 2026 — 301 subscribers14 August 2026 — 306 subscribers7 August 202614 August 2026
3 measurements spanning 7 days, net +5. 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 300–307 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
14 Aug 2026, 20:08306+5
8 Aug 2026, 08:01301no change
7 Aug 2026, 16:36301first reading

Engagement

10 posts held, back to 22 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 1 pageof Telegram’s post history, 20 posts per page.

ERR · 30 days
77.2%
avg views ÷ 306 subscribers
Avg views / post
236
10 posts measured
Reaction rate
3.24%
reactions ÷ views · ER floor
Posts in window
10
of 10 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 9 of 10 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 6 August 2026
Posts held10 (22 July 20266 August 2026)
Views total2,362
Reactions total72
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken8 Aug 2026, 08:01 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

72 reactions across 9 posts, in 12 distinct kinds. The most used accounts for 40.3% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
custom 52219906577567726112940.3%
912.5%
🔥811.1%
❤‍🔥68.33%
👏56.94%
🐳34.17%
💅34.17%
🤝34.17%
👍22.78%
💯22.78%
💘11.39%
🤔11.39%

Custom emoji. One row above is a 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 count beside it isTelegram’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 9 of the 10 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 72reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

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

6 Aug 2026, 15:25 UTC142 views8 reactionsread 8 August 2026
Photo

Модный dev'ан @dimasshortposts #http #модныйdevан

💅3custom 522199065775677261131🔥1

6 Aug 2026, 15:20 UTC134 views7 reactionsread 8 August 2026
Photo

🔎 У HTTP появился новый метод QUERY Двадцать лет индустрия пытается ответить на главный вопрос жизни, вселенной и всего такого. А именно: как посылать сложные запросы? Потому что если посылать GET, то у него есть ограничения по длине. К примеру Nginx по умолчанию рубит строку запроса на 8 КБ. Плюс тело у GET семантически не определено: ты можешь его положить, но его по дороге могут не передать. Двадцать лет индуст

custom 52219906577567726113👍2💘1🔥1

5 Aug 2026, 10:34 UTC142 viewsread 8 August 2026
Poll

Сколько потоков создаётся в консольном приложении Hello world?

  1. 126%
  2. 316%
  3. 103%
  4. Зависит58%

The shares total 103%, above 100: this poll accepts more than one answer per voter. No per-option vote count is published, so the number of voters who chose each option is not derivable and is not shown.

5 Aug 2026, 10:33 UTC158 views5 reactionsread 8 August 2026
Photo

Почти всё лето мы с тобой изучали внутрянку БД на примере #postgresql: от индексов мы спустились по Б+-деревьям до work mem и узнали насколько глубока восьмиикилобайтовая страница 📄 Теперь поплывём дальше 🛳 На нашей steam state machine мы пойдём по бурным рабочим потокам (worker thread), воочию увидим их освобождение на асинхронном водопаде, который приведёт нас к бескрайнему озеру памяти 🫡 Там мы увидим, как разли

custom 522199065775677261132

31 Jul 2026, 15:27 UTC307 views8 reactionsread 8 August 2026
Photo

🗞 Что почитать за июль — мой топ-3 для ASP.NET-щика Возвращаюсь к нерегулярной рубрике (в мае был такой же топ за апрель). Как и всегда июль вышел с перекосом в AI-инструменты для дотнетчика, но и обычного бэкендерского добра завезли. 1️⃣ Много хайпа вокруг .NET 11 Preview 6. Там много чего завезли, но лично мне нравятся вот эти штуки: 🟢 CSRF-защита теперь работает по умолчанию. Приложение теперь само отбивает неб

custom 522199065775677261132🔥2🐳1

29 Jul 2026, 11:35 UTC311 views6 reactionsread 8 August 2026
Photo

🩺 Диагностика — как понять, на что ушла оперативка (часть 2, work_mem наносит ответный удар) 👈 Часть инструментов рассмотрели в прошлом посте, а в этом рассмотрим ещё парочку: 🧰 Что лежит в кэше прямо сейчас Расширение pg_buffercache (мы его уже видели в посте про shared_buffers) показывает поимённо, какие страницы заняли кэш Postgres в данный момент. Удобно, когда надо понять, чем именно забиты те самые 128 MB, вы

custom 522199065775677261132🤝1

27 Jul 2026, 16:20 UTC272 views12 reactionsread 8 August 2026

🍁 Уже этой осенью я буду выступать на DotNEXT 2026! Мне нравится .NET, AI и рассказывать доклады. И что может быть лучше чем рассказать доклад про AI в .NET? Агенты — это относительно новая штука, и мы привыкли пользоваться ими в разработке. Но вот как писать своих агентов и главное зачем? Об этом особо никто не говорит. Так что в этом году буду рассказывать с большого экрана про Microsoft Agent Framework и про то

❤‍🔥6custom 52219906577567726113🔥2🐳1

24 Jul 2026, 15:36 UTC330 views9 reactionsread 8 August 2026
Photo

🤩 Пятничное. Начал тут читать “Войну и Мир” Был значительно ошарашен (в ахуе) от того, сколкьо персонажей можно ввести за раз. В первой главе аж 9 основных. Ну и там еще около 10 второстепенных перечисляется. Сначала чутка фрустировал. Потом пытался вести конспект. А потом вдург вспомнил, что сейчас же есть клодчанский! Попросил его накидать по-быстрому доску-расследование, как в Alan Wake 2. Типа я читаю главу

👏5custom 52219906577567726113🔥1

22 Jul 2026, 15:02 UTC286 views9 reactionsread 8 August 2026

⚡️ Еще быстрый факт про серверный MCP сервер Сегодня поймали еще одну проблемку-дилемку, которую можно было бы добавить в TOP-11 вопросов которые возникли при проектировании MCP: ⚠️ Не очень удобно через серверный MCP отправлять файлы. Дело в том, что по сути есть два пути как передать файл. 1️⃣ Inline base64 прям в Body запроса. 2️⃣ Передать ссылку на точку где лежит ресурс и загрузить самому на сервере. Путь

custom 52219906577567726114💯2🤝2🤔1

22 Jul 2026, 11:32 UTC280 views8 reactionsread 8 August 2026
Photo

🩺 Диагностика — как понять, на что ушла оперативка (часть 1) Мы с тобой разобрались с shared_buffers, кэш ОС и work_mem. Теперь можем понять, если на сервере память забита под завязку (как на дикпике из графаны), проблема это или норма, и куда смотреть в первую очередь 👀 📊 Доля попаданий в кэш (дикпик 1) Первый вопрос — насколько хорошо данные ложатся в память. По каждой базе Postgres в pg_stat_database (системное

custom 522199065775677261142🐳1🔥1

Showing the 10 most recent of 10 posts we hold for @dimasshortposts. 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.

Polls

The poll we hold for this entry, as Telegram rendered it when we read the post. A poll’s figures keep moving after that, so each one is dated.

5 Aug 2026, 10:34 UTCAnonymous Poll31 voters

Сколько потоков создаётся в консольном приложении Hello world?

  1. 126%
  2. 316%
  3. 103%
  4. Зависит58%

The shares total 103%, above 100: this poll accepts more than one answer per voter. No per-option vote count is published, so the number of voters who chose each option is not derivable and is not shown.

Percentages only — there are no per-option vote counts here, because Telegram publishes none.The public post preview gives each option’s share and a single voter total, and nothing else. Multiplying one by the other would produce a per-option tally that looks measured and is not: the shares are rounded to whole numbers before we ever see them. We print what was published and leave the column that does not exist empty.

The shares need not add up to 100.Rounding alone puts many polls at 99 or 101. A poll that allows more than one answer per voter runs well past 100 by design, and several here do. The bars are drawn against a fixed 100% track at each option’s own percentage rather than normalised to the total, so a poll that exceeds it shows that it does instead of being quietly rescaled.

Read from the 10 most recent posts we hold, published 22 July 2026 to 6 August 2026. Telegram labels each poll by kind — an anonymous poll, a quiz, a closed set of final results — and that label is reproduced rather than paraphrased.

Citation-graph rank

Citation-graph rank — 386,658 of 1,350,102entries 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.

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

“C# Short Posts 🔞” (@dimasshortposts), 306 subscribers as measured 14 August 2026. Telegram Register, tgregister.com/channel/dimasshortposts.

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.