Telegram RegisterThe public register of Telegram
Telegram profile photo for .NET epeshk blog

Channel

.NET epeshk blog

@epeshkblog

On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Telegram's recommendations · Cite this entry

2,677subscribers

+5 since we began measuring on 6 August 2026

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

Register entry

Telegram ID-1001657876419
TypeChannel
Username@epeshkblog
CreatedBetween 1 December 2021 and 30 April 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded6 August 2026
Last confirmed live17 September 2026
Measurements held12
Confirmed unchanged1 time, most recently 17 September 2026
On Telegramt.me/epeshkblog

Topic

Technology — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-FP8, prompt version 1) read this channel’s own recent posts on 15 September 2026 and assigned it the closest of 31 fixed categories, at 97% confidence. This is a model’s judgement about what the channel is likely to be about, not a fact this register measured the way a subscriber count or a view count is measured — it can be revised on a later pass, and it carries no weight anywhere else on this page. How this classification works, and why it has no browse page of its own yet.

Growth

2,6722,6802,6766 August 2026 — 2,672 subscribers6 August 2026 — 2,672 subscribers6 August 2026 — 2,673 subscribers9 August 2026 — 2,675 subscribers12 August 2026 — 2,674 subscribers15 August 2026 — 2,676 subscribers18 August 2026 — 2,677 subscribers22 August 2026 — 2,679 subscribers29 August 2026 — 2,678 subscribers4 September 2026 — 2,680 subscribers10 September 2026 — 2,678 subscribers17 September 2026 — 2,677 subscribers2,6776 August 202617 September 2026
12 measurements spanning 42 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 2,671–2,681 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
17 Sept 2026, 07:192,677-1
10 Sept 2026, 05:402,678-2
4 Sept 2026, 22:382,680+2
29 Aug 2026, 00:272,678-1
22 Aug 2026, 14:082,679+2
18 Aug 2026, 21:552,677+1
15 Aug 2026, 19:272,676+2
12 Aug 2026, 02:072,674-1
9 Aug 2026, 04:112,675+2
6 Aug 2026, 08:402,673+1
6 Aug 2026, 05:192,672no change
6 Aug 2026, 04:332,672first reading

Engagement

20 posts held, back to 17 October 2025the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 2 pages of 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 20 posts for this entry, the most recent from 3 August 2026. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Video runtime
59s
Average length
59s

Measured directly from 1 video with a duration reading, out of the posts we hold for this channel — not this channel’s whole posting history, only the sample this register has actually read. An exact reading to the second, taken from the post itself rather than from Telegram’s own rounded chrome, so it carries no mark.

Reaction mix

1,148 reactions across 20 posts, in 13 distinct kinds. The most used accounts for 33.6% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
👍38633.6%
😁36732.0%
🔥14612.7%
🤡857.40%
👎403.48%
🤯373.22%
🤔332.87%
🤩161.39%
👾151.31%
🌚141.22%
🍓40.348%
🎃30.261%
😈20.174%

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 1,148 reactions 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 17 October 2025 to 3 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

3 Aug 2026, 12:24 UTC≈1,440 views46 reactionsread 7 August 2026

LLM оказались упорнее людей 2 недели назад LLM впервые справилась с математической задачей, которая казалась безнадёжной — опровергла гипотезу о якобиане, приведя явный контрпример. Задача не поддавалась людям 87 лет, и представляет собой классический пример гипотезы, доказательство которой (если она верна) займёт сотни страниц, а для опровержения достаточно лишь привести пример, когда условия не выполняются. Анало

👍26🔥13😁7

16 Jul 2026, 10:52 UTC≈2,700 views47 reactionsread 7 August 2026

Расскажите кто каким антикапча решением пользуется? Надоело прокликивать велосипеды, пешеходные переходы, собирать паззлы. Нужен плагин для браузера с ИИ, в который можно закинуть $10 и забыть о капчах как о страшном сне

😁39🔥4👎2😈2

14 Jul 2026, 07:01 UTC≈2,780 views73 reactionsread 7 August 2026

💬 Комментарии в коде Мне никогда не нравился откомментированный код. Комментирование каждой строки сразу выдаёт начинающего программиста. А те комментарии, которые при написании были уместными все равно устаревают — код изменяется, комментарии обновить забывают, человеческий фактор. Лучший вариант, для компилируемых языков, self-explanatory код Однажды не смог сделать оптимизацию в РеШарпере из-за комментария. И

👎38👍30🔥3🤔2

10 Jul 2026, 15:17 UTC≈3,400 views68 reactionsread 7 August 2026

Бежать со всех ног, чтобы только оставаться на месте Именно это придётся делать дотнету для выживания в мире Mythos-level моделей, которые могут всё переписать В этом посте разберём, что нейронки могут улучшить в .NET. Критерии отбора задач: - очевидна полезность - гарантированно существует решение - требует больших трудозатрат для реализации 1. Сделать кросскомпиляцию для NativeAOT. Сейчас фактически нужно ко

👍41🤡23🤔3🎃1

10 Jul 2026, 13:39 UTC≈6,330 views46 reactionsread 7 August 2026

Claude Fable 5 написал GC для .NET на C# Если точнее, модель довела до ума проект по написанию managed GC от Kevin Gosse. На некоторых бенчмарках, AI сгенерированный нейронкой GC не уступает в производительности оригинальному neuecc с помощью Fable 5 ускорил WriteInt в MessagePack. Вместо того, чтобы просить AI ускорить код и make no mistakes применили итеративный подход. В промпт загружались C# исходник и его disa

👍24🔥13🤔5🤩2😁2

22 Mar 2026, 15:33 UTC≈4,900 views81 reactionsread 7 August 2026
Photo

Главное, не списывать точь-в-точь, чтоб не спалили

😁65🔥8👍5🤩3

19 Mar 2026, 19:48 UTC≈4,820 views88 reactionsread 7 August 2026

goodbye, gc.cpp! Ушла эпоха. В .NET 11 Garbage Collector разделили по файлам. Больше нет легендарного gc.cpp с более 50к строк кода https://github.com/dotnet/runtime/pull/125703

😁54🔥20👍9🤯4🤔1

27 Jan 2026, 16:46 UTC≈6,330 views61 reactionsread 7 August 2026
Photo

Возвращаемся к теме многопоточности

😁43👾9🔥5🤡4

8 Jan 2026, 19:06 UTC≈6,950 views41 reactionsread 7 August 2026
Photo

Нарратив про AI bubble, который вот-вот взорвётся почти полностью исчез

🤡25🤔6🌚5👍4🤯1

7 Jan 2026, 10:19 UTC≈6,040 views36 reactionsread 7 August 2026
Photo

C# показал рекордный рост популярности (+2.39%) в индексе TIOBE а Go за год опустился с 7 позиции до 16 Реальность: - C# в индексе восстановился до уровня 2024 года в 7.4 после просадки до 4.2 в прошлом году - индекс TIOBE основан на статистике поисковых запросов, и показывает что шарписты до сих пор пользуются гуглом, а гошники сразу спрашивают чат гпт Методология TIOBE абсурдная изначально, т.к. показывает соц

👍23😁7🍓4🔥2

3 Jan 2026, 14:23 UTC≈4,210 views74 reactionsread 7 August 2026

Снова про Windows 11 Вчера наконец-то поставил Windows 10 вместо Windows 11. Недавно вышел пост про планы Microsoft переписать Windows на Rust с помощью AI-агентов в концепции 1 человек, 1 месяц, 1 миллион строк кода. Microsoft выпустили опровержение: переписывания на Rust не будет. Windows перепишут на TypeScript. Медленная прорисовка webview2-элементов и стала последней каплей. Когда нажимаешь на иконку вайфай,

👍34🤯22🌚9😁6👾3

Showing the 12 most recent of 20 posts we hold for @epeshkblog. 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.

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 2 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.

Appears in Telegram’s recommendations for other channels

The reverse of the list above, and a different kind of signal. This does not require this channel to have ever been asked about directly — each row below is a channel we DID ask Telegram about, whose Telegram-generated list happened to include this one. A channel can appear here with an empty list above it, because being named by someone else’s query is independent of having been queried itself.

The ExtremeCode Times
@extremecode · 35,635
Telegram ranks this channel #41 of 93 here — alongside 92 others — read 2 September 2026

This channel appears in 1 seed channel's Telegram-generated recommendation list in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.

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

“.NET epeshk blog” (@epeshkblog), 2,677 subscribers as measured 17 September 2026. Telegram Register, tgregister.com/channel/epeshkblog.

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.