Posted without readable text

Channel
IT База
@main_it_baza
On this record: Topic · Growth · Engagement · Reactions · Posts · Citations · Handles named that no longer answer · Cite this entry
7,089subscribers
+4 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
Register entry
| Telegram ID | -1002095174700 |
|---|---|
| Type | Channel |
| Username | @main_it_baza |
| Created | Between 1 November 2023 and 31 May 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 18 September 2026 |
| Measurements held | 14 |
| Confirmed unchanged | 1 time, most recently 18 September 2026 |
| On Telegram | t.me/main_it_baza |
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 12 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
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 18 Sept 2026, 16:20 | 7,089 | -10 |
| 14 Sept 2026, 08:15 | 7,099 | -12 |
| 10 Sept 2026, 17:16 | 7,111 | -17 |
| 5 Sept 2026, 19:38 | 7,128 | -17 |
| 1 Sept 2026, 14:44 | 7,145 | -3 |
| 29 Aug 2026, 23:54 | 7,148 | -11 |
| 26 Aug 2026, 21:04 | 7,159 | +52 |
| 23 Aug 2026, 21:39 | 7,107 | -18 |
| 20 Aug 2026, 13:42 | 7,125 | -20 |
| 17 Aug 2026, 19:18 | 7,145 | -14 |
| 14 Aug 2026, 22:07 | 7,159 | +25 |
| 11 Aug 2026, 08:08 | 7,134 | +49 |
| 7 Aug 2026, 17:46 | 7,085 | no change |
| 7 Aug 2026, 17:35 | 7,085 | first reading |
Engagement
61 posts held, back to 2 August 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 14 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 61 posts for this entry, the most recent from 20 August 2026. An engagement rate over an empty window would be a number about nothing.
Reaction mix
19 reactions across 17 posts, in 4 distinct kinds. The most used accounts for 73.7% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 14 | 73.7% | |
| 👍 | 2 | 10.5% | |
| 🔥 | 2 | 10.5% | |
| 💘 | 1 | 5.26% |
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 18 of the 61 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 19 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 61 most recent posts we hold, published 2 August 2026 to 20 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
📧 SMTP-сервер на Python для автоматизации заказов с бирж Знаешь, как это — тратить по 2-3 часа в день на ручной мониторинг фриланс-бирж, просто чтобы не пропустить важные сообщения от заказчиков? Проблема: сообщения от заказчиков приходят в email, но их нужно получать в реальном времени и пересылать в Telegram. Решение — собственный SMTP-сервер на чистом asyncio, который заменяет IMAP polling. В статье разбираются …
🔥 Мастхев подборка для каждого айтишника Держите подборку авторских IT-каналов по всем направлениям: курсы, гайды, статьи, практики, примеры кода, шпаргалки и прохождение собесов. ▪️ Python: @python ▪️ Frontend: @frontend ▪️ Java: @java 👨💻 Go: @golang ▪️ ИБ & Хакинг: @hacking ▪️ C/C++: @cplusplus ▪️ C# & GameDev: @gamedev ▪️ Data Science: @datascience ▪️ DevOps: @devops ▪️ Linux: @linux ▪️ IT Курсы: @courses ▪️ Ва…
🔬 Детектор радиации на ESP32 и MicroPython Хочешь собрать полезный гаджет своими руками и заодно изучить основы IoT-разработки? Этот проект объединяет электронику и программирование в одном устройстве. Полноценный детектор радиации с возможностью отправки данных на GMCMap и Home Assistant. Схема собирается на макетной плате без пайки: ESP32 за $8, OLED-дисплей за $3 и трубка Гейгера-Мюллера. В статье — подробная ин…
Posted without readable text
🐍 Побеждаем OOM в PyTorch на обычной видеокарте Обучаешь графные нейросети на миллионах узлов и постоянно сталкиваешься с ошибками памяти? Стандартный SparseAdam съедает всю видеопамять под историю градиентов, даже если сами параметры помещаются. Проблема: SparseAdam требует дополнительно 2× памяти под моменты оптимизации. Для 10M узлов с размерностью 128 это +10.24 ГБ поверх параметров. Решение — Disk Sparse Adam …
Posted without readable text
🕷️ Botasaurus — фреймворк для неуязвимых скраперов Сколько раз твои веб-скраперы ломались из-за антибот-систем? Botasaurus решает эту проблему раз и навсегда — он создаёт скраперы, которые проходят даже самые сложные проверки. Ключевые возможности: обход Cloudflare WAF, BrowserScan, Fingerprint, Datadome и Cloudflare Turnstile CAPTCHA. Фреймворк объединяет лучшие практики веб-скрейпинга — автоматическое управление …
🤖 Конформные предсказания: когда вероятность действительно 90% Устали ли вы от моделей, которые выдают красивые вероятности, но не дают реальной уверенности в своих предсказаниях? Softmax-проценты 0.9 совсем не означают, что в 90% случаев модель права. Конформные предсказания — метод, который строит предсказательные интервалы с гарантированным покрытием даже без предположений о распределении данных. В статье разбир…
Posted without readable text
🧠 Как случайно открыли функцию активации с багом Когда экспериментатор в области ML начинает "играть" с языковой моделью, спрашивая о функциях активации, оказывается, это может привести к неожиданному открытию. Автор столкнулся с ситуацией, которая вывела на новый "багофиктивный" подход к обучению нейросетей. Суть открытия: случайно обнаруженная "ошибка активации" на самом деле показала лучшие результаты, чем попул…
Posted without readable text
Showing the 12 most recent of 61 posts we hold for @main_it_baza. 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.
Mentions
Names
Channels on the register whose handles appear in this channel's posts.
@clucai · 221 postCOURSES
@courses · 8831 postکتاب برنامه نویسی سی پلاس پلاس - با C++ آشنا شویم
@cplusplus · 2081 postFrontend
@frontend · 3,3851 postGameDev Pulse
@GameDEV · 4,2311 postGo
@golang · 19,3201 postIT News
@itnews · 201 postJava逮捕
@java · 17,7351 postPython
@Python · 95,8801 postvibecoding
@vibecoding · 401 post
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.
Handles this channel named that no longer answer
- Dead references
- 1
- handles named in this channel’s posts, vacant today
- Evidenced gone
- 0
- we ourselves saw one of these resolve, at some point
- Never seen alive
- 1
- vacant every time we have ever looked
@main_it_baza named 1 handle that resolve to nothing today. That is a fact about the reference, not necessarily a fact about the handle’s history — see the two groups below.
Most of these may never have existed as a live channel at all. A handle a channel names can be a typo, an aspirational name nobody registered, or a channel that was already gone before this one ever mentioned it. Unless a row below is marked evidenced, all we know is that it references a handle that is not a live channel today — not that anything “died”. How this is measured.
Never seen alive
References a handle that is not a live channel — we have no record it ever was one.
named in 3 posts, 8 August 2026 – 11 August 2026
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 18 September 2026 — this entry's latest reading, not the date you are reading this.
“IT База” (@main_it_baza), 7,089 subscribers as measured 18 September 2026. Telegram Register, tgregister.com/channel/main_it_baza.
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.