РКН: № 6877073972
У нас публикуются лучшее и эксклюзивные материалы, курсы по программированию, информационная безопасность "хакингу" и IT в целом, которые вы не найдёте в интернете.
CEO: @O_K_TOP
Мы на бирже:
telega.in/c/it_mega_g
Created
Between 1 October 2022 and 30 September 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
Education — 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 11 September 2026 and assigned it the closest of 31 fixed categories, at 88% 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 the other topics.
Observations
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.
Content that also appears on other registered channels
Posts published here appear in near-verbatim form 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.
Matching posts — open both and compare (5 of the pairs behind the counts below)
Channels this entry shares post bodies with, where at least one matching post pair has no forward credit between the two channels, or to a common source, recorded in our data
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 66 comparable posts for this entry, running 6 July 2026 to 10 November 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.
Verbatim republication has three causes and the text separates only two: a clone/mirror, unattributed copy-paste, or BOTH channels copying a common third source that neither attributes. The spread filter (content held by at most 8 channels) reduces the third and does not remove it.
'Earliest' means earliest IN THIS CORPUS. A channel ingested one page deep will look younger than a neighbour ingested in full; corpus_coverage above is there to be checked before the direction is believed.
shared_verified_est extrapolates the sampled pass rate over the full narrow match count; sampled/passed are the numbers actually measured.
Absence of a forward header is not proof of intent: Telegram lets a channel disable forward attribution, and a credit written in the body is not parsed as attribution here (mention_edge_either_way above is the closest available signal).
Recorded under the key clone_source, last confirmed 11 November 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.
Growth
54 measurements spanning 95 days, net +49. 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 11,127–11,192 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 54
Measured (UTC)
Subscribers
Change
9 Nov 2026, 23:47
11,184
+1
7 Nov 2026, 03:21
11,183
+1
6 Nov 2026, 00:56
11,182
+1
4 Nov 2026, 02:20
11,181
+6
3 Nov 2026, 00:39
11,175
+1
2 Nov 2026, 00:05
11,174
-2
1 Nov 2026, 01:00
11,176
+3
31 Oct 2026, 03:58
11,173
-4
30 Oct 2026, 01:17
11,177
-2
28 Oct 2026, 22:15
11,179
-4
27 Oct 2026, 17:38
11,183
+5
26 Oct 2026, 16:59
11,178
+5
25 Oct 2026, 16:20
11,173
-1
24 Oct 2026, 17:29
11,174
+1
23 Oct 2026, 18:47
11,173
+4
22 Oct 2026, 16:08
11,169
+2
21 Oct 2026, 07:47
11,167
-2
20 Oct 2026, 07:59
11,169
+4
19 Oct 2026, 08:07
11,165
-2
18 Oct 2026, 07:06
11,167
first reading
Engagement
67 posts held, back to 6 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 64 pages of Telegram’s post history, 20 posts per page.
ERR · 30 days
16.4%
avg views ÷ 11,184 subscribers
Avg views / post
1,840
22 posts measured
Reaction rate
—
this channel exposes no reaction counts
Posts in window
22
of 67 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
Window
Rolling 30 days · latest post in window 10 November 2026
Posts held
67 (6 July 2026 – 10 November 2026)
Views total
40,413
Reactions total
—
Forwards / comments
not exposed by the public surface — not measured, not estimated
Readings taken
11 Nov 2026, 09:26 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
≈1,050
Videos
≈13
Links
≈1,130
Lifetime counters from Telegram’s own channel header, read 11 November 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.
Advertising
Ad load
2.99%
2 of 67 posts carry an ad marker
Regulatory tokens
2
posts carrying an erid · 2 distinct tokens
Median views · ads
825
over 2 measured posts
Median views · rest
2,480
over 65 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
erid
Posts
First seen
Last seen
2SDnjdTjNe8
1
5 November 2026
5 November 2026
2SDnjeLgYB6
1
9 November 2026
9 November 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 67 most recent posts we hold, published 6 July 2026 to 10 November 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
Telegram’s own ‘edited’ marker: 6 of 22 posts held from the last 30 days (27.3%) carried it when this register last read them. The marker says a post was changed after publishing, not what it said before — this register holds the earlier wording only where an edit fell between two of its own reads (see the edit ledger and how it is measured).
🔴В 2025 году Россияне заработали 5,3 млрд рублей на арбитраже криптовалют
По данным Минфин 32% граждан покинули своё место работы поскольку в среднем уже в первый месяц смогли заработать 250 000 рублей, а через 2-3 месяца с легкостью вышли на семизначные числа.
Самое смешное, что лишь 8% россиян что-то слышали об этой профессии хотя все инструкции бесплатно лежат на канале Арбитраж Криптовалют
Там объясняют, как и…
Связные списки: задачи с алгосекций. (2026)
Чему вы научитесь:
📍Интенсив по решению задач на связные списки
📍Освойте структурированный подход без хаотичного заучивания множества задач на LeetCode.
📍Начнем с основ, без лишних деталей — только самое важное для решения задач
📍Затем рассмотрим 8 типовых задач уровня easy/medium, характерных для алгоритмических секций — полное объяснение идеи и кода
📍К каждой задаче буде…
Advertisementerid 2SDnjeLgYB6Forwarded from @secmediaPhoto
🔒 В Москве состоится митап УЦСБ и «Газинформсервиса»
Тема — безопасная 1С при импортозамещении
Для компаний с развитым ландшафтом 1С его безопасность — вопрос устойчивости бизнес-процессов. Как учесть требования к защите ERP на разных этапах, контролировать доработки и настройки после запуска?
🗓 18 ноября в Москве «Газинформсервис» и УЦСБ проведут митап «Безопасная 1С: как защитить ERP без потери производительности…
ИИ для разработчиков 2.0. (2026)
Чему вы научитесь:
📍Научитесь эффективно работать с контекстом, настраивать харнес (тулы, mcp, память) и проектировать циклы верификации.
📍Реализуете проект через Spec Driven Development и интегрируйте AI в SDLC (Github Workflow)
📍ИИ-агенты становятся стандартом современной разработки:
• Компании массово внедряют workflow-системы, чтобы экономить время, снижать издержки и быстрее ма…
Фабрики программного обеспечения для настоящих инженеров. (2026)
Чему вы научитесь:
📍Курс показывает, как использовать фундаментальные принципы программной инженерии для создания масштабируемой системы разработки, в которой AI способен работать автономно, производить качественный код и постепенно улучшать проект.
📍Строить собственную AI-ориентированную фабрику разработки.
📍Делегировать большие объёмы работы AI-агент…
Advertisementerid 2SDnjdTjNe8Forwarded from @secmediaPhoto
Конференция «Сетевая безопасность 2026» — для тех, кто строит сети и кто их защищает
⏺ 24 ноября, Москва | Регистрация
Сетевикам нужна быстрая и управляемая сеть, безопасникам — сеть под контролем. Конференция «Сетевая безопасность» в равной мере ориентирована на обе команды. В прошлом году её посетили более 1000 специалистов по кибербезопасности, сетевых инженеров и архитекторов, разработчиков ИБ-решений. В програ…
Практики разделения на модули и микросервисы. (2023)
Чему вы научитесь:
📍Познакомитесь с идеями разделения кода на модули или микросервисы.
📍Мы разобрали всё это на своём примере большого магазина, но от вас поступили предложения сделать это и на ваших примерах для ваших предметных областей.
📍Также часто спрашивают о том, как раздробить на модули или микросервисы не новый, а уже имеющийся монолитный проект.
📍Также р…
Первая игра в Roblox за 7 дней. (2026)
Чему вы научитесь:
📍Буквально за неделю вы достигнете впечатляющих результатов.
📍Создадите полноценную игру для Roblox с помощью новейших ИИ-инструментов, разместите её и получите первые деньги, которые сможете вывести на карту в Россию, несмотря на блокировки.
📍Почему стоит выбрать Roblox?
• Это платформа с миллионами пользователей, которая выплатила разработчикам за прошлый …
Дизайнеры с AI. За 1 месяц. (2025)
Чему вы научитесь:
📍У нас вы найдете всё необходимое для вдохновения и обучения: от базовых уроков до продвинутых техник применения нейросетей в творчестве.
📍Создан для того, чтобы помочь вам освоить генеративные нейросети, предоставляя все необходимые материалы для изучения и вдохновения в одном месте.
📍Здесь собраны самые ценные для нас материалы, которые мы используем в своих пр…
Как заработать на AI и AI-агентах? (2026)
Чему вы научитесь:
📍Этот курс создан для тех, кто желает не просто «понять нейросети», а начать зарабатывать на них. Независимо от вашего опыта и профессии, вы сможете интегрировать AI в свою жизнь и превратить его в инструмент дохода.
📍Основная цель курса — продемонстрировать вам практические методы заработка с помощью нейросетей, научить работать с ChatGPT, Midjourney, Ele…
Глубокое погружение: Rust. (2026)
Чему вы научитесь:
📍Этот курс не подойдёт для новичков. Он ориентирован на тех, кто уже знаком с синтаксисом Rust и хочет перейти к разработке серьёзных backend и системных приложений. 📍Основные преимущества курса: детальное изучение работы с памятью, многопоточностью, асинхронным программированием и практиками для продакшена.
📍Основное внимание уделяется системе типов, управлению п…
Программист C
Чему вы научитесь:
📍Поможет разработчикам, администраторам и IoT-специалистам освоить практические навыки программирования на языке C и решать задачи уровня Middle+.
📍Обучение подойдёт тем, кто уже знаком с промышленной разработкой и хочет глубже понять, как программы взаимодействуют с операционной системой и аппаратными ресурсами.
📍Вы не только глубоко погрузитесь в возможности языка С, но и изучите н…
Showing the 12 most recent of 67 posts we hold for @it_mega_g. 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_mega_g 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
1 September 2026
Most recent edit
9 November 2026
Posts recorded as deleted after publishing
We recorded 6 posts on @it_mega_g as deleted — posts this register held that were missing from the channel’s public page on two separate reads, taken from different network addresses at least an hour apart.
A deletion is not wrongdoing. This register can see that a post it held is no longer on the channel’s public page, and when — not why. Expired ad placements, reposts, rotating links and corrections all look the same. This is a count of recorded detections, not an exact total: it misses deletions we could not see, because only a post we held and later re-read inside the page can be seen to go, and it may include a small number of wrong records. How this is measured.
First seen missing
10 August 2026
Most recent seen missing
3 November 2026
Median time before seen missing
3 days
Seen missing in the last 30 days
1
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 6 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.
Named by
Channels on the register whose posts name this channel's handle.
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.
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 9 November 2026 — this
entry's latest reading, not the date you are reading this.
“IT MEGA” (@it_mega_g), 11,184 subscribers as measured 9 November 2026. Telegram Register, tgregister.com/channel/it_mega_g.
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.