Telegram RegisterThe public register of Telegram
Telegram profile photo for Программирование | книги

Channel

Программирование | книги

@it_boooks

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

47,448subscribers

+26 since we began measuring on 6 August 2026

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

Register entry

Telegram ID-1001305140758
TypeChannel
Username@it_boooks
DescriptionДля программистов разных областей науки. Навигация по тегам всегда в закрепе. Чат канала: https://t.me/+GBl0ISybbi00NGYy По всем вопросам: @altmainf Регистрация в перечне РКН https://goo.su/PqEImo3
CreatedBetween 1 March 2018 and 31 July 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded6 August 2026
Last confirmed live7 September 2026
Measurements held27
Confirmed unchanged1 time, most recently 7 September 2026
On Telegramt.me/it_boooks

Topic

Education — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-UD-Q6_K_XL, prompt version 1) read this channel’s own recent posts on 21 August 2026 and assigned it the closest of 31 fixed categories, at 84% 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

47,41047,45547,432.56 August 2026 — 47,422 subscribers6 August 2026 — 47,422 subscribers7 August 2026 — 47,420 subscribers8 August 2026 — 47,424 subscribers9 August 2026 — 47,437 subscribers10 August 2026 — 47,447 subscribers11 August 2026 — 47,446 subscribers12 August 2026 — 47,442 subscribers14 August 2026 — 47,434 subscribers15 August 2026 — 47,410 subscribers16 August 2026 — 47,414 subscribers17 August 2026 — 47,424 subscribers18 August 2026 — 47,430 subscribers19 August 2026 — 47,439 subscribers20 August 2026 — 47,446 subscribers23 August 2026 — 47,438 subscribers25 August 2026 — 47,441 subscribers26 August 2026 — 47,446 subscribers27 August 2026 — 47,443 subscribers28 August 2026 — 47,441 subscribers29 August 2026 — 47,455 subscribers30 August 2026 — 47,437 subscribers31 August 2026 — 47,431 subscribers31 August 2026 — 47,441 subscribers2 September 2026 — 47,446 subscribers5 September 2026 — 47,421 subscribers7 September 2026 — 47,448 subscribers47,4486 August 20267 September 2026
27 measurements spanning 32 days, net +26. 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 47,403–47,462 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 27
Measured (UTC)SubscribersChange
7 Sept 2026, 21:5747,448+27
5 Sept 2026, 00:0247,421-25
2 Sept 2026, 01:3247,446+5
31 Aug 2026, 23:3447,441+10
31 Aug 2026, 01:3647,431-6
30 Aug 2026, 02:5647,437-18
29 Aug 2026, 03:2347,455+14
28 Aug 2026, 01:2347,441-2
27 Aug 2026, 03:3547,443-3
26 Aug 2026, 00:4647,446+5
25 Aug 2026, 03:0747,441+3
23 Aug 2026, 21:5447,438-8
20 Aug 2026, 19:2847,446+7
19 Aug 2026, 20:4747,439+9
18 Aug 2026, 20:3647,430+6
17 Aug 2026, 20:2847,424+10
16 Aug 2026, 21:2847,414+4
15 Aug 2026, 16:3447,410-24
14 Aug 2026, 02:1847,434-8
12 Aug 2026, 19:4347,442first reading

Engagement

37 posts held, back to 1 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 74 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
15.2%
avg views ÷ 47,448 subscribers
Avg views / post
7,200
16 posts measured
Reaction rate
this channel exposes no reaction counts
Posts in window
16
of 37 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 9 September 2026
Posts held37 (1 July 20269 September 2026)
Views total115,220
Reactions total
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken10 Sept 2026, 11:05 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.

What this channel posts

Photos
2,600
Links
23

Lifetime counters from Telegram’s own channel header, read 10 September 2026 — not the date at the top of this page, which is when the subscriber count was last read. A count marked was rounded by Telegram before we ever saw it — t.me prints these counters in full below 1,000 and to three significant figures above, so ≈142,000 means somewhere between 141,500 and 142,499.

Telegram Stars

Stars received
2
across the posts below
Posts paid on
1
of 37 we hold a reading for · 3%
Most on one post
2
single highest reading

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

Advertising

Ad load
2.70%
1 of 37 posts carry an ad marker
Regulatory tokens
1
posts carrying an erid · 1 distinct token
Median views · ads
8,880
over 1 measured post
Median views · rest
9,520
over 36 measured posts

An ad marker, not a judgement about a post. A post is counted here because it carries one of two explicit markings: an erid token, which Russian law has required on paid placements since 2022 and which is issued against a specific advertising contract, or a #реклама / #ad hashtag in the body, which is the channel declaring it itself. The first is documentary; the second is a self-declaration and is weaker. No classifier reads the text and decides — nothing on this site guesses that a post is an advertisement.

This is a floor, and it can only ever be a floor. A channel that runs paid placements without marking them produces no marker for us to count, and an unmarked ad is indistinguishable from an ordinary post on the public surface. The ad load above therefore means “the share of posts that declared themselves”, never “the share of posts that were paid for”. A low figure is not evidence of a channel that runs few ads.

Both figures are medians, and no ratio between them is published. Each is a view reading that actually occurred on a post, picked by percentile_disc rather than averaged, so one viral post cannot move it and no interpolated value is invented between two readings. The sample on one side is under five posts, which is too thin to compare. The two figures are shown side by side with the count behind each, and deliberately not divided into a headline like “ads get x% fewer views” — an arithmetic that is easy to print and, at this sample size, means nothing.

Advertising tokens recorded on this entry
eridPostsFirst seenLast seen
2VtzqvmTpdo18 July 20268 July 2026

A token repeated across several posts is one advertising contract placed more than once, which is what the identifier is for. The strings are reproduced exactly as they appeared in the post or in its click-through URL and are not validated against any registry — we record the marker a channel published, and whether it resolves to a real contract is a question for the register that issued it.

Measured over the 37 most recent posts we hold, published 1 July 2026 to 9 September 2026. Views are the latest single reading held for each post, and any reading at or above 1,000 is rounded by Telegram to three significant figures.

Recent posts

9 Sept 2026, 14:59 UTC≈3,020 viewsread 10 September 2026
Photo

#ИБ #Облака 2025 Защита данных в облаке с OAuth: Масштабируемая архитектура с нулевым доверием Авторы: Арчер Г., Карер Дж., Трояновски М. OAuth – мощный фреймворк для обеспечения безопасности API – предлагает инструменты, помогающие защитить конфиденциальность бизнес данных и реализовать динамический контроль доступа. Он позволяет выйти за рамки простых запретов и определить политики безопасности, соответствующи

7 Sept 2026, 14:59 UTC≈4,640 viewsread 10 September 2026
Photo

#ИИ 2026 Протокол MCP для систем искусственного интеллекта Автор: Айдоуби Протокол контекста модели (Model Context Protocol, MCP) служит связующим звеном между ИИ-приложениями и внешними расширениями. MCP стремительно меняет экосистему ИИ и стал общепринятым отраслевым стандартом. Основная цель этой книги – помочь читателю получить всестороннее и системное представление о MCP, включая историю его появления, принц

4 Sept 2026, 14:59 UTC≈6,080 viewsread 10 September 2026
Photo

#D3JS 2025 D3.js в действии Авторы: Микс Э., Дюфур Э.-М. Книга рассказывает о библиотеке D3.js, которая позволяет создавать сложную инфографику, диаграммы и визуализации данных с применением стандартных инструментов разработки веб интерфейсов, включая JavaScript, HTML и CSS. Вы научитесь воспроизводить анимационные эффекты и настраивать адаптивные отображения на мобильных устройствах. Каждая глава содержит законч

4 Sept 2026, 11:54 UTC≈5,950 viewsread 10 September 2026
Photo

Первый шаг к работе в Росатоме можно сделать прямо из своего города. 🚀Кейслаб по веб-разработке — это бесплатное обучение, реальные отраслевые задачи и наставники, которые помогут пройти программу и разобраться с рабочим форматом. По итогам лучшие участники смогут попасть на очный финал молодежного фестиваля «ИТ КоР 5.0. Новый код атомной отрасли». На финале в Нижнем Новгороде участники защитят свои решения, познак

3 Sept 2026, 14:59 UTC≈6,100 viewsread 10 September 2026
Photo

#OpenClaw #ИИ 2026 OpenClaw. Как разработать собственного ИИ-агента за час Автор: Лю Цзян В отличие от традиционных ИИ-систем, агенты не просто отвечают на ваши вопросы, а по-настоящему выполняют за вас работу. В книге подробно описана экосистема OpenClaw – популярного ИИ-агента с открытым исходным кодом, предназначенного для широкого использования людьми, не имеющими специальной подготовки. Понятные пояснения и

3 Sept 2026, 11:54 UTC≈5,450 viewsread 10 September 2026
Photo

7,2 млн рублей призового фонда и реальные задачи космической отрасли 🚀 В сентябре пройдет серия КосмоХакатонов для студентов, молодых ученых и специалистов. Участникам предстоит за два дня разработать собственное решение, поработать с экспертами и представить проект жюри. Участников ждут: 🛰 реальные задачи космической отрасли 👥 команды от 3 до 5 человек 💻 очный и онлайн-форматы 🧑‍💻 работа с экспертами и трекерами 🏆

2 Sept 2026, 14:59 UTC≈5,720 viewsread 10 September 2026
Photo

#Haskell 2025 Изучаем Haskell на примерах Автор: Хагенлохер Ф. Haskell – это мощный и красивый, но непростой функциональный язык программирования. Вы научитесь создавать Haskell-приложения на примерах разработки полезных и увлекательных проектов. Вас ждут язык для сочинения музыки, библиотека обработки изображений и многое другое! Особое внимание уделено таким вопросам, как проектирование функций, композиция и не

31 Aug 2026, 14:59 UTC≈6,920 viewsread 10 September 2026
Photo

#ИИ 2026 Создание приложений с ИИ-агентами. Проектирование и внедрение мультиагентных систем Автор: Майкл Альбада Генеративный ИИ произвел революцию в том, как организации решают проблемы, ускорив переход от концепции к прототипу и готовому решению. По мере роста возможностей моделей наблюдается появление нового паттерна проектирования — ИИ-агентов. Сочетание инструментов, знаний, памяти и механизмов обучения с п

28 Aug 2026, 15:02 UTC≈7,720 viewsread 10 September 2026
Photo

#СистемнаяИнженерия #Trinity 2026 Системная инженерия: современные методы проектирования для создания сложных информационных систем. 2-е изд Автор: Холт Д. Системная инженерия — ключевой инструмент для разработки сложных систем на всех этапах их жизненного цикла. В обновленном издании эксперт в области системной инженерии подробно рассказывает, что следует учитывать при проектировании надежных и эффективных сист

26 Aug 2026, 15:00 UTC≈8,050 viewsread 10 September 2026
Photo

#DevOps 2026 Метрики программной архитектуры. Кейсы, повышающие качество ПО Автор: Форд Н. В современном мире разработки ПО архитектура приложения играет ключевую роль. Но как убедиться, что выбранная архитектура действительно отвечает всем требованиям проекта? Именно здесь на сцену выходят метрики — комплексный процесс проверки соответствия архитектурных решений заданным требованиям и критериям качества. Чем поз

24 Aug 2026, 14:59 UTC≈8,570 viewsread 10 September 2026
Photo

#MachineLearning 2025 Машинное обучение для приложений высокого риска. Подходы к ответственному искусственному интеллекту Авторы: Патрик Холл, Джеймс Кертис Книга представляет собой комплексное руководство по применению искусственного интеллекта и машинного обучения (ИИ/ML) с целью снижения рисков для современного бизнеса, связанного с использованием этих технологий. Рассмотрены основы управления рисками и компью

21 Aug 2026, 15:02 UTC≈8,910 viewsread 10 September 2026
Photo

#KaliLinux 2026 The Ultimate Kali Linux Book: Использование Nmap, Metasploit, Aircrack-ng и Empire для пентестинга. 3-е межд. изд Автор: Сингх Г. Вы освоите набор инструментов Kali Linux для оценки уязвимостей, где ключевая роль отводится сбору информации, научитесь находить целевые системы, обнаруживать проблемы в безопасности устройств, эксплуатировать уязвимости сети и тестировать веб-приложения. Дойдя до конц

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

Posts edited after publishing

@it_boooks edited 1 post 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
13 August 2026
Most recent edit
13 August 2026

Mentions

Named by 3 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.

Porscode | CMD
@porscode_tg · 28,501
Telegram ranks this channel #9 of 77 here — alongside 76 others — read 9 September 2026
Physics.Math.Code
@physics_lib · 146,469
Telegram ranks this channel #12 of 72 here — alongside 71 others — read 13 August 2026
Базы данных | Access, SQL, Big Data
@databases_secrets · 30,018
Telegram ranks this channel #21 of 82 here — alongside 81 others — read 7 September 2026
Библиотека программиста
@proglibrary · 78,398
Telegram ranks this channel #33 of 82 here — alongside 81 others — read 19 August 2026
Java библиотека
@javalib · 30,717
Telegram ranks this channel #46 of 84 here — alongside 83 others — read 7 September 2026
Терабит: айти технологии
@tbite · 28,262
Telegram ranks this channel #55 of 85 here — alongside 84 others — read 9 September 2026
Python Learning
@Python_per_month · 28,368
Telegram ranks this channel #74 of 86 here — alongside 85 others — read 9 September 2026

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

“Программирование | книги” (@it_boooks), 47,448 subscribers as measured 7 September 2026. Telegram Register, tgregister.com/channel/it_boooks.

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.