Telegram RegisterThe public register of Telegram
Telegram profile photo for Kali Linux

Channel

Kali Linux

@linuxkalii

On this record: Topic · Observations · Also posting the same content · Growth · Engagement · What this channel posts · Reactions · Stars · Advertising · Posts · Citations · Handles named that no longer answer · Telegram's recommendations · Cite this entry

55,481subscribers

+596 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-1001175723706
TypeChannel
Username@linuxkalii
Description@linux_kal наш чат По всем вопросам- @workakkk @ai_machinelearning_big_data - машинное обучение @itchannels_telegram - 🔥 главные ресурсы для хакера @programming_books_it - бесплатные it книги @pythonl -🐍 РКН: clck.ru/3Fmszy #VRHSZ
Created29 September 2020 — measured — cross-checked against a third-party dataset (ext.tg_channel)
First recorded6 August 2026
Last confirmed live4 October 2026
Measurements held36
Confirmed unchanged1 time, most recently 4 October 2026
On Telegramt.me/linuxkalii

Topic

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

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

Matching posts — open both and compare (6 of the pairs behind the counts below)
Posted firstThenOverlapGap
@linuxkalii/2129 · this entry28 Jul 2026, 11:02 UTC@linux_education/261028 Jul 2026, 15:49 UTC1.004.8 hours
@linuxkalii/2128 · this entry27 Jul 2026, 14:31 UTC@linux_education/260827 Jul 2026, 15:55 UTC0.9983 minutes
@linuxkalii/2130 · this entry29 Jul 2026, 12:13 UTC@linux_education/261229 Jul 2026, 15:45 UTC0.993.5 hours
@linuxkalii/2125 · this entry26 Jul 2026, 13:05 UTC@linux_education/260526 Jul 2026, 15:59 UTC0.992.9 hours
@linuxkalii/2137 · this entry1 Aug 2026, 12:33 UTC@linux_education/26241 Aug 2026, 15:32 UTC0.993.0 hours
@linuxkalii/2131 · this entry30 Jul 2026, 12:00 UTC@linux_education/261430 Jul 2026, 15:40 UTC0.993.7 hours
Every channel this entry shares post bodies with
ChannelMatching postsText overlapTypical gapPublished first
@linux_education12 (8/8 hand-verifiable sample passed)0.993.0 hoursthis entry (12–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 19 comparable posts for this entry, running 24 July 2026 to 7 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.

  • 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).

Across the whole group of 2, the earliest publisher we hold is @linuxkalii — 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.

Also posting the same content

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.

Growth

54,88555,48155,1836 August 2026 — 54,885 subscribers6 August 2026 — 54,898 subscribers7 August 2026 — 54,902 subscribers8 August 2026 — 54,897 subscribers9 August 2026 — 54,898 subscribers10 August 2026 — 54,914 subscribers11 August 2026 — 54,933 subscribers12 August 2026 — 54,956 subscribers13 August 2026 — 54,975 subscribers14 August 2026 — 54,976 subscribers16 August 2026 — 54,988 subscribers17 August 2026 — 54,999 subscribers18 August 2026 — 55,008 subscribers19 August 2026 — 55,048 subscribers20 August 2026 — 55,029 subscribers21 August 2026 — 55,042 subscribers22 August 2026 — 55,091 subscribers24 August 2026 — 55,138 subscribers25 August 2026 — 55,128 subscribers26 August 2026 — 55,124 subscribers27 August 2026 — 55,145 subscribers28 August 2026 — 55,146 subscribers29 August 2026 — 55,153 subscribers30 August 2026 — 55,151 subscribers31 August 2026 — 55,173 subscribers1 September 2026 — 55,201 subscribers2 September 2026 — 55,233 subscribers3 September 2026 — 55,231 subscribers5 September 2026 — 55,240 subscribers9 September 2026 — 55,243 subscribers11 September 2026 — 55,267 subscribers13 September 2026 — 55,286 subscribers15 September 2026 — 55,312 subscribers17 September 2026 — 55,349 subscribers25 September 2026 — 55,412 subscribers4 October 2026 — 55,481 subscribers6 August 20264 October 2026
36 measurements spanning 59 days, net +596. 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 54,796–55,570 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 36
Measured (UTC)SubscribersChange
4 Oct 2026, 10:3855,481+69
25 Sept 2026, 23:3655,412+63
17 Sept 2026, 10:0055,349+37
15 Sept 2026, 07:1855,312+26
13 Sept 2026, 12:5655,286+19
11 Sept 2026, 19:3655,267+24
9 Sept 2026, 07:5455,243+3
5 Sept 2026, 20:5655,240+9
3 Sept 2026, 21:2255,231-2
2 Sept 2026, 13:1455,233+32
1 Sept 2026, 10:5755,201+28
31 Aug 2026, 10:3455,173+22
30 Aug 2026, 07:5455,151-2
29 Aug 2026, 09:1755,153+7
28 Aug 2026, 09:1155,146+1
27 Aug 2026, 08:4855,145+21
26 Aug 2026, 11:5255,124-4
25 Aug 2026, 14:5355,128-10
24 Aug 2026, 13:2555,138+47
22 Aug 2026, 19:1455,091first reading

Engagement

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

ERR · 30 days
12.3%
avg views ÷ 55,481 subscribers
Avg views / post
6,800
38 posts measured
Reaction rate
0.662%
reactions ÷ views · ER floor
Posts in window
38
of 99 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 6 October 2026
Posts held99 (24 July 2026 – 6 October 2026)
Views total258,320
Reactions total1,709
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken6 Oct 2026, 20:12 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,340
Videos
≈102
Links
≈1,290

Lifetime counters from Telegram’s own channel header, read 6 October 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.

Video runtime
2m 34s
Average length
2m 34s

Measured directly from 1 video with a duration reading, out of the posts we hold for this channel — not this channel’s whole posting history, only the sample this register has actually read. An exact reading to the second, taken from the post itself rather than from Telegram’s own rounded chrome, so it carries no ≈ mark.

Reaction mix

4,311 reactions across 97 posts, in 13 distinct kinds. The most used accounts for 30.7% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
👍1,32530.7%
❤1,10925.7%
🔥83719.4%
😁43410.1%
😱1242.88%
🥰1032.39%
👎912.11%
🤔902.09%
👏811.88%
🎉611.41%
🤬420.974%
🤯80.186%
😢60.139%

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

Measured over the 99 most recent posts we hold, published 24 July 2026 to 6 October 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
2
across the posts below
Posts paid on
2
of 99 we hold a reading for · 2%
Most on one post
1
single highest reading

A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @linuxkalii. 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 99 most recent posts we hold for this entry, published 24 July 2026 to 6 October 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
7.07%
7 of 99 posts carry an ad marker
Regulatory tokens
7
posts carrying an erid · 7 distinct tokens
Median views · ads
5,910
over 7 measured posts
Median views · rest
7,160
over 92 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. They are printed side by side with the count behind each rather than as a ratio: an ad and an ordinary post are not otherwise matched — for topic, for length, for hour of day — so the gap between them is a description of two groups and not the effect of one being an ad.

Advertising tokens recorded on this entry
eridPostsFirst seenLast seen
2VSb5xcpXbp14 September 20264 September 2026
2Vtzqw2Brow15 October 20265 October 2026
2VtzqwS4qQe127 July 202627 July 2026
2VtzqwtMVDn12 October 20262 October 2026
2W5zFGUvsxm114 September 202614 September 2026
2W5zFHDrAFj121 September 202621 September 2026
2W5zFJ9AfYV120 August 202620 August 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 99 most recent posts we hold, published 24 July 2026 to 6 October 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

6 Oct 2026, 10:21 UTC≈2,500 views21 reactionsread 6 October 2026
Photo

🕵️ Удалили cookies? Сайт всё ещё может узнать ваш браузер Александр Ханфф собрал большой технический разбор способов отслеживания в Chrome: цифровые отпечатки устройства, идентификаторы в хранилищах и утечки через заголовки запросов. Внутри разбираются: • Canvas и WebGL: особенности отрисовки помогают отличать устройства. • Шрифты, звук и параметры экрана: отдельные сигналы складываются в цифровой отпечаток. • Хра…

🔥10❤5👍4🥰2

5 Oct 2026, 13:05 UTC≈4,070 views99 reactionsread 6 October 2026
Photo

🤯 Один программист создал FFmpeg, QEMU, QuickJS и запуск Linux прямо в браузере. И его имя знают далеко не все. Это Фабрис Беллар, французский инженер и один из самых продуктивных системных программистов последних десятилетий. В 2000 году он запустил FFmpeg и несколько лет руководил проектом. Сегодня FFmpeg стал фундаментальным инструментом для обработки, кодирования и стриминга аудио и видео. Затем Беллар создал …

🔥68❤18👏11👍2

5 Oct 2026, 11:21 UTC≈3,780 views21 reactionsread 6 October 2026
Advertisementerid 2Vtzqw2BrowPhoto

От теории к реальным задачам: как учат веб-пентесту в Codeby 🚗 Можно знать OWASP Top 10, понимать, как работают SQLi и SSRF, и уметь пользоваться Burp Suite. Но в реальном проекте важно самостоятельно исследовать приложение, находить цепочки уязвимостей и доводить их до эксплуатации. Именно поэтому курс WAPT от Codeby построен вокруг практики: ⏺️поиск и эксплуатация уязвимостей из OWASP Top 10 ⏺️анализ защищённости…

👍8❤7👎4🔥2

5 Oct 2026, 10:31 UTC≈4,050 views41 reactionsread 6 October 2026
Photo

🐍 Доверилась Claude как дневнику, а переписка дошла до полиции Жительница Флориды рассказывала боту о своей жизни. По данным следствия, в одном из сообщений она пригрозила устроить стрельбу в офисе шерифа, а позже написала, что приобрела оружие. Система безопасности пометила сообщения и передала их на проверку сотрудникам Anthropic. Уже люди уведомили правоохранителей. Женщину задержали и предъявили обвинение в пи…

❤13👍8😱6🤔5🔥4👏2😁2👎1

4 Oct 2026, 13:02 UTC≈4,760 views33 reactionsread 6 October 2026
Photo

🐧 Linux Cheat Sheet - шпаргалка по командам Linux Самая удобная шпаргалка по Linux и Bash на русском: теория простым языком (как устроены файлы, процессы, права, память, загрузка и сеть), команды терминала, права доступа, процессы, сеть, SSH, systemd, grep/sed/awk, Vim и готовые однострочники - с примерами. А для тех, кто идёт дальше, - продвинутый уровень: Bash для профи, LVM и RAID, трассировка и производительнос…

👍22🔥8❤3

3 Oct 2026, 12:02 UTC≈4,990 views28 reactionsread 6 October 2026
Photo

🕵️ Flowsint - open-source платформа для OSINT-расследований в виде графа Flowsint помогает собирать данные из разных источников и сразу видеть связи между сущностями: доменами, IP, email, телефонами, организациями, соцсетями и криптокошельками. Что умеет: - искать поддомены, DNS, WHOIS и ASN - проверять email и телефоны по утечкам - искать username по соцсетям через Maigret - анализировать сайты и трекеры - смотре…

🔥14👍8❤6

2 Oct 2026, 11:04 UTC≈5,190 views20 reactionsread 6 October 2026
Photo

🛠️ Awesome SRE - большая подборка ресурсов для Site Reliability Engineering Репозиторий awesome-sre собирает полезные материалы по SRE и Production Engineering в одном месте. Внутри есть подборки по: - Monitoring и Observability - Incident Response и Post-Mortem - On-Call - Chaos Engineering - Automation и Toil Reduction - Capacity Planning - SLO / SLI - Performance - книгам, докладам, статьям и гайдам Также собр…

❤8🔥7👍5

2 Oct 2026, 09:02 UTC≈4,760 views12 reactionsread 6 October 2026
Advertisementerid 2VtzqwtMVDnPhoto

22 октября Kubernetes-сообщество встречается офлайн в Москве! Кому будет интересна конференция: – DevOps- и SRE-инженерам; – специалистам по Kubernetes и облачной инфраструктуре; – платформенным инженерам; – архитекторам и техническим руководителям; – всем, кто занимается эксплуатацией и развитием инфраструктуры. Что будет в течение дня? 🎤 Доклады Программа продолжает дополняться, но уже сейчас в ней много интерес…

❤6👍6

1 Oct 2026, 09:57 UTC≈5,510 views24 reactionsread 6 October 2026
Photo

OpenAI впервые публично обвинила китайскую лабораторию в дистилляции OpenAI связала скоординированную атаку на скрытые рассуждения своих моделей с людьми из Moonshot AI, разработчика Kimi. Шифрование никто не взламывал. Атакующие копировали зашифрованные рассуждения из одного диалога и просили модель расшифровать их в другом. Кампания шла с 1 июля, на пике 24–25 июля было 16 000 запросов от 4 000+ пользователей, а…

❤10🔥5👍3👎2🥰2😁2

30 Sept 2026, 12:04 UTC≈6,090 views36 reactionsread 6 October 2026

Почему `kill -9` не может убить главный процесс Linux Обычно SIGKILL завершает любой процесс мгновенно. Его нельзя перехватить, заблокировать или проигнорировать. Но у процесса с PID 1 особый статус. Ядро разрешает отправлять ему только те сигналы, для которых он сам установил обработчик. У SIGKILL обработчика быть не может, поэтому даже команда: sudo kill -9 1 не завершит системный init. Причина проста: если PI…

👍20🔥9❤5🥰2

30 Sept 2026, 08:32 UTC≈5,660 views20 reactionsread 6 October 2026
Forwarded from @ai_machinelearning_big_dataPhoto

📌 Anthropic оценила кибервозможности GLM-5.3 Anthropic впервые оценила открытую китайскую модель и опубликовала исследование о том, насколько GLM-5.3 от Z.ai продвинулась в поиске и эксплуатации уязвимостей. Z.ai выпустила модель в августе, веса выложила через две недели. Двумя неделями ранее её проверял CAISI, центр стандартов и инноваций ИИ при американском институте NIST, и назвал сильной в киберзадачах среди о…

🔥10❤8👍2

28 Sept 2026, 12:10 UTC≈6,660 views45 reactionsread 6 October 2026
Photo

Linux приближается к 2000 уязвимостей за один релиз Ещё несколько лет назад речь шла примерно о 500 уязвимостях на релиз. Потом число перевалило за 1000, затем за 1500, а теперь ядро Linux приближается к отметке в 2000. Об этом рассказал Грег Кроа-Хартман, один из самых известных и опытных мейнтейнеров Linux kernel, перед выступлением на Kernel Recipes 2026. Интересно, что сам код не вырос пропорционально. Ядро вс…

👍33❤9🔥3

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

Forward network

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 51 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. The 24 listed below are the most frequent namers; the rest are counted above but not each listed.

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.

Channels Telegram recommends alongside this one

Telegram’s own answer, not this register’s. When this register asks Telegram’s API what is similar to this channel, this is the list it returns, in the exact order Telegram returns it — never re-sorted by subscribers or by anything else this register measures. The relationship, and the order, are Telegram’s; we record them and date them, and make no claim of our own about which of these channels actually resemble this one.

Linux Academy
@linuxacademiya · 28,459
#1
Social Engineering
@Social_engineering · 124,999
#2
infosec
@it_secur · 62,254
#3
DevOps
@DevOPSitsec · 23,671
#4
Admin Guides | Сисадмин
@admguides · 11,960
#5
Архив Безопасника
@secure_archive · 10,977
#6
Machinelearning
@ai_machinelearning_big_data · 278,381
#7
Python/ django
@pythonl · 58,674
#8
Open Source
@open_source_friend · 52,333
#9
Life-Hack - Хакер
@haccking · 63,140
#10
PyLinux - Всё о Linux, Python и IT
@pylinux0 · 11,043
#11
Чёрный Треугольник
@black_triangle_tg · 63,815
#12
Белый хакер
@bezopasno_soft · 29,634
#13
no system is safe // cybersec
@nsis_cybersec · 21,516
#14
ZeroDay | Кибербезопасность
@cybersec_academy · 42,827
#15
Bash Days | Linux | DevOps
@bashdays · 23,640
#16
Codeby
@codeby_sec · 37,047
#17
Не хакинг, а ИБ
@searchack · 18,204
#18
Golang Books
@golang_books · 16,937
#19
CyberINS // Лаборатория ИБешника
@cyberins · 11,609
#20
Записки Безопасника
@infosec_globe · 18,057
#21
Похек
@poxek · 16,928
#22
BashMaster
@bash_help · 8,853
#23
Linux Books
@linux_read · 16,099
#24
Серверная Админа | Компьютерные сети
@school_network · 26,560
#25
InfoSec Portal
@cybersecinform · 19,286
#26
S.E.Book
@S_E_Book · 23,139
#27
C++ Academy
@cpluspluc · 15,487
#28
Inf0 | ИБ, OSINT
@info_cybersecurity · 10,450
#29
Network Admin
@networkadm · 12,361
#30
Секреты сисадмина | DevOps, Linux, SRE
@sysadmin_library · 25,522
#31
Rust
@rust_code · 8,925
#32
IT Portal
@IT_Portal · 99,777
#33
Linux
@linux_sup · 7,429
#34
ServerAdmin.ru
@srv_admin · 32,593
#35
Kali Linux (ru)
@kali_linux_ru · 9,042
#36
Linux / Линукс
@linux_gram · 13,704
#37
White Hat
@kind_hack · 12,028
#38
Python RU
@pro_python_code · 12,343
#39
Библиотека хакера | Hacking, Infosec, ИБ, информационная безопасность
@hackproglib · 12,693
#40
Linux для чайника
@os_linux_ru · 19,602
#41
Архив Программиста
@storage_it · 8,723
#42
Машинное обучение RU
@machinelearning_ru · 18,200
#43
DevOps School | Linux, InfoSec, ИБ
@devops_sc · 14,824
#44
IT Syndicate
@ITSyndicate_23 · 8,558
#45
IT-KB 🤖
@ITKB_channel · 7,997
#46
RECURA | Программирование & IT
@recura_tech · 14,575 (as read 23 August 2026)
#47
Linux Education
@linux_education · 11,106
#48
Хакер | Red Team
@Red_Team_hacker · 6,706
#49
INSPECTOR | OSINT
@it_fullstak · 10,926
#50
Cybred
@cybred · 11,287
#51
Этичный Хакер
@hack_less · 240,669
#52
Golang
@Golang_google · 40,420
#53
Mr. Robot
@elliot_cybersec · 38,849
#54
Анализ данных (Data analysis)
@data_analysis_ml · 50,680
#55
Data Science. SQL hub
@sqlhub · 35,948
#56
infosecurity
@tg_infosec · 26,761
#57
SecurityLab.ru
@SecLabNews · 84,790
#58
S.E.Reborn
@S_E_Reborn · 22,399
#59
[PYTHON:TODAY]
@python2day · 63,715
#60
Go tests
@golangtests · 7,818
#61
Хакер — Xakep.RU
@xakep_ru · 39,722
#62
Бункер Хакера
@book_academ · 21,410
#63
Golang вопросы собеседований
@golang_interview · 15,038
#64
STEIN: ИБ, OSINT
@secur_researcher · 14,247
#65
GitHub Community
@github · 155,595
#66
Хабр
@habr_com · 132,847
#67
NetStalkers
@netstalkerscom · 7,836
#68
Бэкдор
@whackdoor · 1,586,239
#69
Библиотека С# С++
@cpluscsharp · 10,085
#70
Russian OSINT
@Russian_OSINT · 47,997
#71
Сетевик Джонни // Network Admin
@iscode · 5,787
#72
Математика Дата саентиста
@data_math · 14,263
#73
Python вопросы с собеседований
@python_job_interview · 24,860
#74
SecAtor
@true_secator · 41,782
#75
IT MEGA облако
@it_mega_disk · 11,367
#76
Арсенал Безопасника
@arsenal_security · 15,191
#77
Интернет-Розыск
@irozysk · 45,930
#78
Big Data AI
@bigdatai · 18,202
#79
C# (C Sharp) programming
@csharp_ci · 18,060
#80
PHP Academy
@phpshka · 9,216
#81
Пост Лукацкого
@alukatsky · 37,955
#82
CyberYozh
@cyberyozh_official · 62,542
#83
Эксплойт
@exploitex · 2,048,192
#84
Golang Jobs
@GolangJobsit · 14,232
#85
Python tests
@python_testit · 6,888
#86
Вакансии в ИБ | infosec
@infosec_work · 15,847
#87
Physics.Math.Code
@physics_lib · 146,792
#88
Утечки информации
@dataleak · 118,872
#89

Read from Telegram’s recommendation API, most recently 23 August 2026. Telegram holds a list like this for a small and growing share of the register — how this is measured, and why most channel pages show nothing here.

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.

Linux Academy
@linuxacademiya · 28,459
Telegram ranks this channel #1 of 84 here — alongside 83 others — read 9 September 2026
DevOps
@DevOPSitsec · 23,671
Telegram ranks this channel #3 of 90 here — alongside 89 others — read 18 September 2026
Termux, please
@termuxplz0x41 · 32,678
Telegram ranks this channel #11 of 54 here — alongside 53 others — read 4 September 2026
Python/ django
@pythonl · 58,674
Telegram ranks this channel #11 of 84 here — alongside 83 others — read 22 August 2026
Open Source
@open_source_friend · 52,333
Telegram ranks this channel #12 of 87 here — alongside 86 others — read 24 August 2026
Linux для чайника
@os_linux_ru · 19,602
Telegram ranks this channel #13 of 87 here — alongside 86 others — read 1 October 2026
InfoSec Portal
@cybersecinform · 19,286
Telegram ranks this channel #14 of 75 here — alongside 74 others — read 2 October 2026
ZeroDay | Кибербезопасность
@cybersec_academy · 42,827
Telegram ranks this channel #15 of 70 here — alongside 69 others — read 29 August 2026
Белый хакер
@bezopasno_soft · 29,634
Telegram ranks this channel #17 of 78 here — alongside 77 others — read 8 September 2026
Серверная Админа | Компьютерные сети
@school_network · 26,560
Telegram ranks this channel #19 of 85 here — alongside 84 others — read 12 September 2026
infosec
@it_secur · 62,254
Telegram ranks this channel #20 of 81 here — alongside 80 others — read 22 August 2026
no system is safe // cybersec
@nsis_cybersec · 21,516
Telegram ranks this channel #21 of 71 here — alongside 70 others — read 23 September 2026
Social Engineering
@Social_engineering · 124,999
Telegram ranks this channel #21 of 82 here — alongside 81 others — read 13 August 2026
Секреты сисадмина | DevOps, Linux, SRE
@sysadmin_library · 25,522
Telegram ranks this channel #22 of 85 here — alongside 84 others — read 13 September 2026
Life-Hack - Хакер
@haccking · 63,140
Telegram ranks this channel #23 of 85 here — alongside 84 others — read 21 August 2026
Bash Days | Linux | DevOps
@bashdays · 23,640
Telegram ranks this channel #24 of 94 here — alongside 93 others — read 18 September 2026
S.E.Book
@S_E_Book · 23,139
Telegram ranks this channel #31 of 64 here — alongside 63 others — read 19 September 2026
Чёрный Треугольник
@black_triangle_tg · 63,815
Telegram ranks this channel #32 of 87 here — alongside 86 others — read 21 August 2026
Mr. Robot
@elliot_cybersec · 38,849
Telegram ranks this channel #34 of 70 here — alongside 69 others — read 31 August 2026
Системный администратор
@i_odmin · 26,681
Telegram ranks this channel #43 of 89 here — alongside 88 others — read 12 September 2026
CYBER HUNTER - Кибербезопасность
@cyberbezopasno · 57,544
Telegram ranks this channel #43 of 50 here — alongside 49 others — read 26 August 2026
Анализ данных (Data analysis)
@data_analysis_ml · 50,680
Telegram ranks this channel #46 of 93 here — alongside 92 others — read 25 August 2026
Бункер Хакера
@book_academ · 21,410
Telegram ranks this channel #47 of 72 here — alongside 71 others — read 23 September 2026
ServerAdmin.ru
@srv_admin · 32,593
Telegram ranks this channel #47 of 96 here — alongside 95 others — read 5 September 2026

This channel appears in 54 seed channels' Telegram-generated recommendation lists in total, of which the 24 where it ranks highest are shown above. 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 4 October 2026 — this entry's latest reading, not the date you are reading this.

“Kali Linux” (@linuxkalii), 55,481 subscribers as measured 4 October 2026. Telegram Register, tgregister.com/channel/linuxkalii.

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.