Channel
@progersbooks
On this record: Topic · Observations · Also posting the same content · Growth · Engagement · What this channel posts · Reactions · Advertising · Posts · Cite this entry
8,295subscribers
-7 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
| Telegram ID | -1001474186642 |
|---|---|
| Type | Channel |
| Username | @progersbooks |
| Description | № 4931134716 Всё, что связано с айти и разработкой. По вопросам сотрудничества: @adv_and_pr |
| Created | Between 1 April 2019 and 31 August 2021— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 10 August 2026 |
| Measurements held | 3 |
| Confirmed unchanged | 1 time, most recently 10 August 2026 |
| On Telegram | t.me/progersbooks |
Technology — 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 11 August 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.
These are measurements, not verdicts. Each one below states something we counted, alongside the evidence it was counted from, so you can check it rather than take it. None of them is graded: every observation this register holds is recorded at severity 0, because the precision of the detectors behind them has not been measured yet, and a rating we cannot support is worse than none. Read each as a fact about the data, not as a judgement about the channel. How we measure.
Posts published here appear word for word on 1 other registered channel. The matching is on the text itself, not on Telegram’s forward marker, so it finds a copy whether or not it was labelled as one.
| Posted first | Then | Overlap | Gap |
|---|---|---|---|
| @progersbooks/2599 · this entry9 Jul 2026, 18:18 UTC | @itainik/14919 Jul 2026, 18:18 UTC | 1.00 | under a minute |
| @progersbooks/2603 · this entry16 Jul 2026, 08:24 UTC | @itainik/149516 Jul 2026, 08:24 UTC | 1.00 | under a minute |
| @progersbooks/2606 · this entry20 Jul 2026, 20:03 UTC | @itainik/149820 Jul 2026, 20:03 UTC | 1.00 | under a minute |
| @progersbooks/2607 · this entry22 Jul 2026, 19:22 UTC | @itainik/149922 Jul 2026, 19:22 UTC | 1.00 | under a minute |
| @progersbooks/2608 · this entry23 Jul 2026, 19:40 UTC | @itainik/150023 Jul 2026, 19:40 UTC | 1.00 | under a minute |
| @progersbooks/2615 · this entry3 Aug 2026, 20:59 UTC | @itainik/15073 Aug 2026, 20:59 UTC | 1.00 | under a minute |
| Channel | Matching posts | Text overlap | Typical gap | Published first |
|---|---|---|---|---|
| @itainik | 19 (8/8 hand-verifiable sample passed) | 1.00 | under a minute | this entry (19–0) |
Text overlap is the Jaccard coefficient over the set of distinct three-word phrases in the two bodies: 1.00 is identical wording, and the threshold for counting a pair at all is 0.70. Candidates are generated by simhash LSH (4 x 16-bit bands, exact Hamming <= 3) verified against the bodies with Jaccard over the SET of distinct 3-word shingles. Published first counts which side of each matching pair carries the earlier timestamp — in this corpus, which is the limitation directly below.
What this cannot establish
MEASURED, DOMINANT ERROR SOURCE: a post ingested before 2026-08-06 may have carried a forward header that was not recorded. A 45-pair hand-check against live t.me pages found 14 (31%) where the live page shows a forward header naming the other channel and the database has none, plus 4 more (9%) naming a third party. The text match itself was wrong 0 times out of 45. Read attribution_capture.items_in_trusted_window before treating the unattributed count as a claim.
Telegram lets a channel forward a post with a header naming the source, and we only began reliably recording that header on 2026-08-06. None of the 0 matches recorded here fall after that date, so for this entry we cannot say whether any of them carried a credit. The duplication is measured; the absence of attribution is not.
“Published first” means first in this corpus. We hold 20 comparable posts for this entry, running 8 July 2026 to 6 August 2026. A channel we have read one page deep will look younger than a neighbour we have read in full, and the order would flip with no change in the underlying facts.
The detector’s own notes on this observation, as it recorded them. Names in this_style are fields of the underlying evidence record, which the plain-English paragraphs above read out for this entry.
Across the whole group of 2, the earliest publisher we hold is @progersbooks — which is this entry. That is a statement about our reading window, not a claim of authorship.
Recorded under the key clone_source, last confirmed 7 August 2026. An observation that a later pass no longer finds is cleared, and a cleared observation is removed from this page rather than being shown struck through — we do not keep publishing a claim we have withdrawn. Dispute an observation.
This channel’s posts match, word for word or near enough, posts on 1 other registered channel, found by comparing text fingerprints across every channel on the register. That matching has been checked by hand against the live Telegram pages and found reliable — 0 wrong of 45 pairs re-read.
Which channel, if either, published first is deliberately not shown. The same hand-check found that reading wrong 18 of 45 times — 60%, no better than a coin flip — because it depends on how deep our own crawl happened to reach into each channel’s history, not on when the content was actually first posted. This list is ordered by subscriber count, the same as every other listing on this site, never by which channel we think came first. Word-for-word matching has several ordinary explanations besides copying — a channel mirroring itself, an unattributed repost, or two channels independently repeating the same wire story — and this measurement cannot tell those apart. How this is measured.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 10 Aug 2026, 09:20 | 8,295 | -5 |
| 7 Aug 2026, 12:28 | 8,300 | -2 |
| 7 Aug 2026, 01:45 | 8,302 | first reading |
23 posts held, back to 8 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 11 pagesof Telegram’s post history, 20 posts per page.
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 5 of 19 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 10 August 2026 |
|---|---|
| Posts held | 23 (8 July 2026 – 10 August 2026) |
| Views total | 11,689 |
| Reactions total | 4 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 12 Aug 2026, 16:35 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.
Lifetime counters from Telegram’s own channel header, read 12 August 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.
6 reactions across 5 posts, in 1 kind.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 6 | 100.0% |
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 7 of the 23 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 6reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 23 most recent posts we hold, published 8 July 2026 to 10 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.
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.
| erid | Posts | First seen | Last seen |
|---|---|---|---|
| 2W5zFGqBSt1 | 1 | 20 July 2026 | 20 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 23 most recent posts we hold, published 8 July 2026 to 10 August 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.
🗳 Java. Optional Не все программисты знаю, что такое Optional, а те кто знает или не умеет им пользоваться, или чётко понимает его роль в null-safety. Класс Optional кажется простым, по определению, но с его использованием есть много подводных камней, о которых рассказывает автор ролика. https://youtube.com/watch?v=rrQ4st2zgY8
🔓 Криптография Пишите вы ботов, сайты или делаете игры, вы обязаны понимать как работает шифрование, зачем нужен HTTPS, чем SHA256 лучше MD5 и как это всё использовать на практике. Автор рассказывает про проблемы криптографии, про работу хеш-функций, про TLS разных версий, атаки на них и методы ускорения протокола, про Blockchain, PKI и даже про Certificate Transparency. https://youtu.be/_jYb5TMxWQ8
🔥 Всё про корутины в Unity Сопрограмма или корутина — мощная и удобная функция, которую можно использовать для выполнения функции по истечении определенного периода времени. Автор ролика рассказывает что такое корутина, в каких ситуациях её стоит применять и какие проблемы могут возникнуть у новичков. Перейти к просмотру
⚡️ Как стать Backend разработчиком Backend занимается созданием невидимой части сайта. Он отвечает за самые важные процессы бизнеса: хранения данных, обработку входящих запросов. В этом видео вы узнаете какие задачи стоят перед Backend разработчиком и какие технологии надо учить чтобы стать программистом. Перейти к просмотру
Уроки C# Unity В ходе нескольких уроков вы ознакомитесь с написанием C# кода внутри движка Unity. Вы изучите различные функции и свойства, что присутствуют лишь в самом движке. К концу курса вам будет гораздо проще работать в движке, обладая навыками программирования на C#. 📂 Перейти к курсу
Программирование общее Микс из самых разных уроков на самые разные темы от самых разных авторов. Изучаем вопросы с максимальной конкретикой и повышаем свою эрудицию. Перейти к просмотру
🎩 7 ошибок джунов — [21:13] Джуниоры — это программисты, которые только недавно закончили изучать какой-либо язык. Из-за отсутствия опыта, они, очевидно, чаще всего допускают ошибки. Именно поэтому автор рассказал, каких ошибок можно избежать начинающим разработчикам. Он объяснил, почему много/мало вопросов — это плохо, как непонимание бизнес-логики рушит проекты, а также поделился ещё несколькими полезными советам…
🔗 Пишем приложение на блокчейн Web3 Если вы думаете, что писать приложения на блокчейне, с поддержкой смарт-контрактов, с хорошей защитой — сложно, то вы правы. Но если разобраться, что к чему, то станет намного проще. Автор рассказывает как написать децентрализованное приложение и как оно работает. https://youtube.com/watch?v=B4NiWJQgVJU
🐌 5 правил, чтобы стать программистом быстрее Если вы учитесь программировать самостоятельно, то вы должны понимать, что это может затянуться аж до понедельника (то есть навсегда). В этом видео автор собрал 5 полезных советов, благодаря которым ваше обучение пойдёт на порядок быстрее и не упрётся в невидимый потолок всего через несколько месяцев. А без этого никак. https://youtu.be/7l0vKLsS7AY
📚 70 книг по IT, которые надо прочесть — [1:06:02] Если читать по книге в месяц, то весь список прочитаете за 5.83333333 лет. Речь пойдёт про soft skill'ы, безопасность, хороший и «какого ***» код. Среди 70 лучших книг вы встретите произведения дядюшки Боба, паттерны, руководство по рефакторингу и руководства по языкам: Python, Rust, Go. https://youtube.com/watch?v=dx7F7VqnsVQ
💰 Решаем задачу про валюты на JavaScript — [10:09] Разбор популярной задачи с собеседования про валютные транзакции за день двумя возможными способами решения. В частности, вы узнаете, как на языке JavaScript из массива всех валютных операций за день создать объект с суммами всех операций по каждой из валют. Перейти к просмотру
❤2
📓 Учимся работать в PyCharm Sublime Text и другие подобные редакторы кода — это, конечно, хорошо, но подходят они в основном только для новичков. Если вы уже пытались с их помощью написать что-то сложнее, чем print("hello world"), то вы наверняка представляете, насколько это больно. Поэтому, из этого плейлиста вы узнаете, как работать с PyCharm — полноценной средой разработки для Python. Первое видео посвящено уста…
Showing the 12 most recent of 23 posts we hold for @progersbooks. 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.
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 10 August 2026 — this entry's latest reading, not the date you are reading this.
“Заметки программиста” (@progersbooks), 8,295 subscribers as measured 10 August 2026. Telegram Register, tgregister.com/channel/progersbooks.
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.