Telegram RegisterThe public register of Telegram
Telegram profile photo for Книжный куб

Channel

Книжный куб

@book_cube

On this record: Topic · Growth · Engagement · Reactions · Stars · Posts · Posts edited after publishing · Citations · Telegram's recommendations · Cite this entry

15,749subscribers

+1,077 since we began measuring on 6 August 2026

Risers and fallers across the register · movement among entries of 10,000–31,623.

Register entry

Telegram ID-1001758034592
TypeChannel
Username@book_cube
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 live26 September 2026
Measurements held33
Confirmed unchanged1 time, most recently 26 September 2026
On Telegramt.me/book_cube

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 10 September 2026 and assigned it the closest of 31 fixed categories, at 99% 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

14,67215,78115,226.56 August 2026 — 14,672 subscribers6 August 2026 — 14,677 subscribers7 August 2026 — 14,692 subscribers8 August 2026 — 14,689 subscribers9 August 2026 — 14,693 subscribers10 August 2026 — 14,698 subscribers11 August 2026 — 14,693 subscribers12 August 2026 — 14,686 subscribers13 August 2026 — 14,685 subscribers17 August 2026 — 14,696 subscribers18 August 2026 — 14,704 subscribers19 August 2026 — 14,717 subscribers20 August 2026 — 14,725 subscribers22 August 2026 — 14,730 subscribers23 August 2026 — 14,735 subscribers25 August 2026 — 14,845 subscribers26 August 2026 — 15,118 subscribers27 August 2026 — 15,330 subscribers28 August 2026 — 15,468 subscribers29 August 2026 — 15,515 subscribers30 August 2026 — 15,565 subscribers31 August 2026 — 15,630 subscribers1 September 2026 — 15,715 subscribers2 September 2026 — 15,753 subscribers3 September 2026 — 15,781 subscribers5 September 2026 — 15,762 subscribers8 September 2026 — 15,740 subscribers11 September 2026 — 15,729 subscribers13 September 2026 — 15,724 subscribers15 September 2026 — 15,744 subscribers17 September 2026 — 15,750 subscribers19 September 2026 — 15,751 subscribers26 September 2026 — 15,749 subscribers15,7496 August 202626 September 2026
33 measurements spanning 51 days, net +1,077. 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 14,506–15,947 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 33
Measured (UTC)SubscribersChange
26 Sept 2026, 00:1815,749-2
19 Sept 2026, 09:4015,751+1
17 Sept 2026, 01:5915,750+6
15 Sept 2026, 01:4115,744+20
13 Sept 2026, 09:1515,724-5
11 Sept 2026, 13:1915,729-11
8 Sept 2026, 23:5815,740-22
5 Sept 2026, 14:1715,762-19
3 Sept 2026, 13:2015,781+28
2 Sept 2026, 09:2215,753+38
1 Sept 2026, 10:5515,715+85
31 Aug 2026, 12:3515,630+65
30 Aug 2026, 09:1315,565+50
29 Aug 2026, 08:0515,515+47
28 Aug 2026, 09:2715,468+138
27 Aug 2026, 06:4715,330+212
26 Aug 2026, 04:1615,118+273
25 Aug 2026, 01:5914,845+110
23 Aug 2026, 15:5414,735+5
22 Aug 2026, 01:3914,730first reading

Engagement

117 posts held, back to 31 July 2026 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 52 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
13.4%
avg views ÷ 15,749 subscribers
Avg views / post
2,100
21 posts measured
Reaction rate
0.631%
reactions ÷ views · ER floor
Posts in window
21
of 117 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
WindowRolling 30 days · latest post in window 3 September 2026
Posts held117 (31 July 2026 – 3 September 2026)
Views total44,189
Reactions total279
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken3 Sept 2026, 10:17 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

1,720 reactions across 110 posts, in 32 distinct kinds. The most used accounts for 33.1% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
❤57033.1%
🔥54931.9%
👍41924.4%
😱382.21%
👎191.10%
🤔160.93%
💔140.814%
😢130.756%
😁120.698%
🫡120.698%
🕊70.407%
🌚60.349%
👾50.291%
💅50.291%
🤝50.291%
❤‍🔥40.233%
🗿40.233%
😭40.233%
✍20.116%
👌20.116%
12 further kinds140.814%

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

Measured over the 117 most recent posts we hold, published 31 July 2026 to 3 September 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
17
across the posts below
Posts paid on
14
of 117 we hold a reading for · 12%
Most on one post
3
single highest reading

A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @book_cube. 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 117 most recent posts we hold for this entry, published 31 July 2026 to 3 September 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

3 Sept 2026, 05:08 UTC989 views3 reactions3 Starsread 3 September 2026

Stanford MS&E435: Али Годси говорит, что AGI уже здесь, а компания — ещё нет (Рубрика #AI) Редкий случай, когда одна 39-минутная запись собирает в одну картину темы, о которых я писал по отдельности: корпоративную память, AI-native организацию, судьбу SaaS и перенос ценности вверх по стеку. Это встреча Stanford MS&E435: преподаватель Apoorv Agrawal разговаривает с Али Годси, сооснователем и CEO Databricks. Годси на…

🔥2❤1

Signed Alexander Polomodov

2 Sept 2026, 17:22 UTC≈1,400 views14 reactions1 Starread 3 September 2026

Code of Leadership S2E18: Продуктовый инженер — как изменится роль программистов в ближайшие 3 года Код писать становится заметно быстрее. Но если всё большую часть реализации можно делегировать AI-инструментам, что тогда остаётся ядром работы программиста: знание синтаксиса, инженерное суждение или ответственность за продукт целиком? В новом выпуске Code of Leadership во вторник, 8 сентября, в 19:00 попробуем разо…

👎5🔥5❤2👍2

Signed Alexander Polomodov

2 Sept 2026, 15:18 UTC≈1,430 views9 reactions1 Starread 3 September 2026

Материалы Code of Leadership S2E15: последние 90 дней в компании (Рубрика #Management) Готовы материалы сольного выпуска Code of Leadership S2E15, который вышел 31 августа. В общей нумерации подкаста это выпуск №73. Он получился личным: после почти десяти лет в одной компании я разбираю обратную сторону первых 90 дней — как осознанно завершить прежний этап. Заявление здесь не начало процесса, а трудно обратимая точ…

🔥4👍3❤2

Signed Alexander Polomodov

2 Sept 2026, 13:16 UTC≈1,450 views10 reactions1 Starread 3 September 2026
Photo

NVLink Fusion: свой XPU, стойка NVIDIA и причем здесь Mediatek (Рубрика #AI) Когда я рассказывал про эволюцию Google TPU, логика была понятной: крупный облачный провайдер создаёт собственный ускоритель, чтобы точнее подогнать железо под свои модели и меньше зависеть от универсальных GPU. Ответ NVIDIA на этот тренд выглядит довольно красиво: хорошо, делайте свой XPU — а стойку вокруг него мы поможем собрать на нашей…

👍5❤3🔥2

Signed Alexander Polomodov

2 Sept 2026, 10:01 UTC≈1,690 views12 reactions1 Starread 3 September 2026

Приходите послушать про джунов на эфир и задавайте свои вопросы.

👍6❤5🔥1

Signed Alexander Polomodov

2 Sept 2026, 08:11 UTC≈1,820 views8 reactionsread 3 September 2026

3 AImigo S1E4: AI нанимает AI. Как пересобрать IT-собеседования? (Рубрика #AI) AI соискателя встречается с AI нанимающего — мегазорд против супер-рейнджера. Запрет AI не делает интервью AI-free, резюме всё хуже подтверждает способность работать, а старые онлайн-этапы дают всё более шумный сигнал. Вопрос у компании прежний: сможет ли человек успешно работать в этой роли? В пятницу в 12:00 по Мск в прямом эфире подка…

❤5🔥2👍1

Signed Alexander Polomodov

2 Sept 2026, 05:08 UTC≈1,680 views4 reactionsread 3 September 2026

Stanford MS&E435: дефицитный мегаватт AI-фабрики (Рубрика #AI) После этой лекции «облачный AI» выглядит удивительно тяжёлой промышленностью: электричество, подстанции, охлаждение, бетон и люди, которые всё это собирают. Третья встреча Stanford MS&E435 полезна именно этим — опускает разговор о моделях, токенах и GPU на физический слой ниже. Гость — Чейз Локмиллер, сооснователь и CEO Crusoe, которая строит и продаёт в…

❤2👍1🔥1

Signed Alexander Polomodov

1 Sept 2026, 14:38 UTC≈1,950 views20 reactionsread 3 September 2026

Code of Leadership S2E16: Джун после кода - как растить инженеров, когда исполнение уезжает агентам (Рубрика #Education) Сегодня 1 сентября, хотел анонсировать завтрашний эфир в 13:00 про джунов и не только. AI-агенты уже умеют за минуты собирать прототипы, писать тесты, находить ошибки и предлагать готовые изменения. Артефакты становятся качественнее, а разница между работой джуна и опытного инженера на демо — всё …

❤12🔥5👍3

Signed Alexander Polomodov

1 Sept 2026, 13:16 UTC≈1,880 views7 reactions1 Starread 3 September 2026

SGLang: как структура программы ускорила LLM-инференс (Рубрика #AI) Продолжая тему vLLM и PagedAttention (что я разбирал раньше), решил продолжить статье «SGLang: Efficient Execution of Structured Language Model Programs». У vLLM вопрос был: как эффективнее размещать KV cache в памяти. SGLang делает следующий ход: как не вычислять заново точные префиксы, уже обработанные в предыдущих обращениях к модели. Команда St…

🔥4❤2👍1

Signed Alexander Polomodov

1 Sept 2026, 05:08 UTC≈1,990 views7 reactionsread 3 September 2026

Stanford MS&E435: inference как производственная система (Рубрика #AI) После истории Google TPU и разговора с Dylan Patel про hardware-software co-design вторая лекция Stanford MS&E435 складывается в следующий кусок пазла. Она называется «The GPU Economy», но интереснее здесь не вопрос «какой чип победит?». Интереснее момент, в котором software становится производством: каждый новый запрос снова включает фабрику. В…

❤3🔥3👍1

Signed Alexander Polomodov

31 Aug 2026, 13:59 UTC≈2,270 views33 reactionsread 3 September 2026

Заходите на прямой эфир про последние дни в компании, которые начинаются задолго до заявления. P.S. Кстати, сегодня я забрал свою трудовую книжку:)

🔥22💔6👍3❤‍🔥2

Signed Alexander Polomodov

31 Aug 2026, 08:11 UTC≈2,350 views8 reactionsread 3 September 2026
Photo

JetBrains Developer Ecosystem 2026: что 15 509 разработчиков говорят об AI-агентах (Рубрика #AI4SDLC) JetBrains опубликовала срез десятого ежегодного Developer Ecosystem Survey. Опрос проходил с мая по июль 2026 года, в анализ вошли 15 509 профессиональных разработчиков. Было восемь языков, региональные квоты и статистические веса по региону, занятости, языкам программирования и знакомству с продуктами JetBrains. Ч…

❤4👍3🔥1

Signed Alexander Polomodov

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

Posts edited after publishing

@book_cube edited 2 posts after it first published — the same permalink now carries different wording than the one this register originally read, caught because our own crawl held a copy of the earlier text.

An edit is not deception. Typo fixes, price updates and corrections look exactly like this too — this register can tell you the wording changed and when, not why. How this is measured.

First edit seen
11 August 2026
Most recent edit
15 August 2026

Forward network

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

Код Желтый
@kod_zheltyi · 33,101
Telegram ranks this channel #6 of 96 here — alongside 95 others — read 4 September 2026
Инжиниринг Данных
@rockyourdata · 23,732
Telegram ranks this channel #11 of 93 here — alongside 92 others — read 17 September 2026
Teamlead Good Reads – ежедневные советы про менеджмент людей и команд
@leadgr · 28,120
Telegram ranks this channel #16 of 96 here — alongside 95 others — read 10 September 2026
AvitoTech
@avitotech · 25,625
Telegram ranks this channel #24 of 96 here — alongside 95 others — read 14 September 2026
Максим Дорофеев: Прокрастинация и джедайские техники
@mnogosdelal · 26,254
Telegram ranks this channel #30 of 97 here — alongside 96 others — read 14 September 2026
Диджитализируй!
@t0digital · 28,573
Telegram ranks this channel #34 of 88 here — alongside 87 others — read 9 September 2026
T-Crew
@t_crew · 43,385
Telegram ranks this channel #49 of 95 here — alongside 94 others — read 29 August 2026
Нестыдная фасилитация
@no_shame_facilitation · 22,824
Telegram ranks this channel #60 of 99 here — alongside 98 others — read 19 September 2026
ИТ-Пикник
@IT_picnic · 23,126
Telegram ranks this channel #62 of 94 here — alongside 93 others — read 18 September 2026
FEDOR BORSHEV
@pmdaily · 23,698
Telegram ranks this channel #69 of 97 here — alongside 96 others — read 17 September 2026
Системный анализ | Ольга Пономарева
@system_analyse · 31,554
Telegram ranks this channel #69 of 97 here — alongside 96 others — read 6 September 2026
Yandex for Developers
@Yandex4Developers · 28,545
Telegram ranks this channel #71 of 94 here — alongside 93 others — read 9 September 2026
Yandex Cloud
@yandexcloudnews · 21,888
Telegram ranks this channel #72 of 97 here — alongside 96 others — read 22 September 2026
Профсоюз работников IT
@ruitunion · 35,942
Telegram ranks this channel #74 of 94 here — alongside 93 others — read 2 September 2026
GetAnalyst - Навыки • Системный анализ • Бизнес-анализ
@getanalysts · 22,509
Telegram ranks this channel #75 of 96 here — alongside 95 others — read 20 September 2026
запуск завтра
@ctodaily · 33,699
Telegram ranks this channel #81 of 96 here — alongside 95 others — read 4 September 2026
Лидерская позиция | Андрей Шапенко
@leadership_position · 27,168
Telegram ranks this channel #86 of 98 here — alongside 97 others — read 11 September 2026
Ozon Tech
@ozon_tech · 29,768
Telegram ranks this channel #89 of 98 here — alongside 97 others — read 8 September 2026
Яндекс нанимает | Вакансии для разработчиков
@ya_jobs · 32,803
Telegram ranks this channel #91 of 96 here — alongside 95 others — read 5 September 2026

This channel appears in 19 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 26 September 2026 — this entry's latest reading, not the date you are reading this.

“Книжный куб” (@book_cube), 15,749 subscribers as measured 26 September 2026. Telegram Register, tgregister.com/channel/book_cube.

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.