Telegram RegisterThe public register of Telegram
Telegram profile photo for Николай Хитров | Блог

Channel

Николай Хитров | Блог

@nkhitrov_blog

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

3,065subscribers

+891 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-1001829046073
TypeChannel
Username@nkhitrov_blog
CreatedBetween 1 October 2022 and 30 September 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded6 August 2026
Last confirmed live15 September 2026
Measurements held13
Confirmed unchanged1 time, most recently 15 September 2026
On Telegramt.me/nkhitrov_blog

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 14 September 2026 and assigned it the closest of 31 fixed categories, at 89% 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,1693,0652,6176 August 2026 — 2,174 subscribers6 August 2026 — 2,174 subscribers6 August 2026 — 2,171 subscribers10 August 2026 — 2,172 subscribers13 August 2026 — 2,169 subscribers16 August 2026 — 2,878 subscribers20 August 2026 — 2,948 subscribers23 August 2026 — 2,975 subscribers27 August 2026 — 3,017 subscribers30 August 2026 — 3,040 subscribers2 September 2026 — 3,056 subscribers11 September 2026 — 3,060 subscribers15 September 2026 — 3,065 subscribers6 August 202615 September 2026
13 measurements spanning 40 days, net +891. 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,035–3,199 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
15 Sept 2026, 10:413,065+5
11 Sept 2026, 10:193,060+4
2 Sept 2026, 11:023,056+16
30 Aug 2026, 06:353,040+23
27 Aug 2026, 01:163,017+42
23 Aug 2026, 16:352,975+27
20 Aug 2026, 00:432,948+70
16 Aug 2026, 17:432,878+709
13 Aug 2026, 10:052,169-3
10 Aug 2026, 09:202,172+1
6 Aug 2026, 23:402,171-3
6 Aug 2026, 06:062,174no change
6 Aug 2026, 03:022,174first reading

Engagement

20 posts held, back to 7 March 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 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 6 August 2026. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Video runtime
23s
Average length
23s

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

534 reactions across 19 posts, in 22 distinct kinds. The most used accounts for 28.1% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
🔥15028.1%
😁9818.4%
👍7914.8%
5710.7%
💯509.36%
🤣285.24%
🍓142.62%
🗿112.06%
🤔101.87%
👀81.50%
🌚50.936%
👻40.749%
😢40.749%
🥰30.562%
🥴30.562%
👎20.375%
😭20.375%
🤝20.375%
10.187%
👌10.187%
2 further kinds20.375%

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 561 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 7 March 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.

Telegram Stars

Stars received
10
across the posts below
Posts paid on
1
of 20 we hold a reading for · 5%
Most on one post
10
single highest reading

A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @nkhitrov_blog. 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 7 March 2026 to 6 August 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.

Recent posts

6 Aug 2026, 10:03 UTC681 views5 reactionsread 7 August 2026

HardFest от создателей CodeFest 17 октября в Екатеринбурге команда CodeFest делает HardFest. Как понятно из названия, ребята хотят сделать более узконаправленную тематику, без разброса по параллельным трекам на разные темы. И очень хотят собрать сильных инженеров в одном месте Сама конференция не такая большая как CodeFest, до 800 человек. В программе хотят видеть доклады про архитектуру, распределённые системы, эк

👀4🔥1

1 Aug 2026, 15:29 UTC≈1,440 views81 reactionsread 7 August 2026
Photo

Работа работой, но не забывайте иногда выходить на улицу и трогать траву руками

🔥6111👍7🥰2

20 Jul 2026, 18:33 UTC≈2,450 views48 reactionsread 7 August 2026

Иногда мне хочется плюнуть в лицо тому, кто придумал k8s. Катишь релиз, он половину подов выкатывает и затем делает rollback. Почему? Да потому что. Как это узнать? Ну иди там в events ковыряйся или логах каждого пода или еще как-нибудь, мне п***й. Сам найдешь. Очень. Удобный. Интерфейс. Все. Для. Людей.☕️

💯21🗿97😁4🥴3🤝2👍1💊1

9 Jul 2026, 17:12 UTC≈2,910 views4 reactionsread 7 August 2026

Мы начали, залетайте!

3👍1

8 Jul 2026, 14:05 UTC≈2,910 views21 reactionsread 7 August 2026

В комментариях нормально накидали разных вариантов, приходите завтра в 20:00 по мск, будем разбирать https://www.youtube.com/live/yDeIQ85wlKk?si=BDy8kW6aqZ_v5xZ7

👍156

1 Jul 2026, 17:00 UTC≈2,640 views15 reactionsread 7 August 2026

Pycon 2026 Чисто из названий я пока приметил для себя несколько докладов, с остальными разберемся на месте Первое, что зацепило, это доклад про новый фреймворк django modern rest (привет Никита). Я пока не видел production использования, надеюсь, спикеры расскажут про такой опыт. Все еще не люблю джангу, но люблю то, что делает Никита😁 Интересно посмотреть про мониторинг сборщика мусора. В прошлых годах были докла

9👍6

1 Jul 2026, 13:59 UTC≈1,950 views8 reactionsread 7 August 2026

Соцопрос: кто ваш любимый DI фреймворк в python? На днях обсуждали с Пашей @s3rius_san библиотеки и затронули тему DI. Он когда-то написал свою версию Depends из fastapi специально для своего фреймворка taskiq. Чтобы привычный уже многим интерфейс, но с "нормальной" реализацией Так мы перешли к спору за неудачные решения в других библиотеках. И нам стало интересно, кто чем пользовался и пользуется прямо сейчас? Со

👍7🔥1

8 Jun 2026, 20:11 UTC≈2,660 views34 reactionsread 7 August 2026
Photo

Может и правда есть смысл делать такие стримы про болтовню о всяком разном? Мне давно хотелось утащить каким-то образом в онлайн беседы с афтерпати и похоже, что стримы как формат вполне себе могут подойти для этого

💯28🌚42

2 Jun 2026, 21:49 UTC≈3,070 views35 reactionsread 7 August 2026
Forwarded from @komikakiPhoto

Photo, posted without a caption

🔥16😁144🌚1

29 May 2026, 12:28 UTC≈1,950 views6 reactionsread 7 August 2026

Долгое время не было постов и вот к чему это все привело...

😁6

29 May 2026, 12:28 UTC≈2,580 views17 reactionsread 7 August 2026
Forwarded from @opensource_findingsVideo

Анонс стрима: "работаем над lazy import'ами в CPython и плачем под аниме" (на превью - я на стриме) Мы с @nkhitrov_blog, @fastnewsdev и Денисом Аникиным (в 2026 и без тг канала!) решили замутить стрим по питону и ... новый канал на ютюбе под названием "Вялые Питоны". Подписаться уже можно вот тут: https://www.youtube.com/@SluggishPythons О чем будет канал? - Менее душный и более мемный чем мой основной - Все еще

🔥12😁41

13 Apr 2026, 15:38 UTC≈3,360 views44 reactionsread 7 August 2026
Photo

Сегодня больше не вайбкодим, рабочий день закончился☕️ https://downdetector.com/status/claude-ai/

🤣28👻4😢4👍2👎21👌1💯1

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

Диджитализируй!
@t0digital · 28,573
Telegram ranks this channel #3 of 88 here — alongside 87 others — read 9 September 2026
Timeweb Cloud Alerts
@timewebcloud_alerts · 27,753
Telegram ranks this channel #46 of 87 here — alongside 86 others — read 9 September 2026
FEDOR BORSHEV
@pmdaily · 23,757
Telegram ranks this channel #52 of 97 here — alongside 96 others — read 17 September 2026
BotNews
@BotNews · 131,414
Telegram ranks this channel #56 of 65 here — alongside 64 others — read 20 August 2026

This channel appears in 4 seed channels' Telegram-generated recommendation lists 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 15 September 2026 — this entry's latest reading, not the date you are reading this.

“Николай Хитров | Блог” (@nkhitrov_blog), 3,065 subscribers as measured 15 September 2026. Telegram Register, tgregister.com/channel/nkhitrov_blog.

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.