Telegram RegisterThe public register of Telegram
Telegram profile photo for Системный администратор

Channel

Системный администратор

@i_linux

On this record: Topic · Observations · Also posting the same content · Growth · Engagement · Reactions · Posts · Citations · Handles named that no longer answer · Cite this entry

1,963subscribers

-26 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of 1,000–3,162.

Register entry

Telegram ID-1001723464174
TypeChannel
Username@i_linux
CreatedBetween 1 December 2021 and 30 April 2023— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live17 August 2026
Measurements held5
Confirmed unchanged1 time, most recently 17 August 2026
On Telegramt.me/i_linux

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 11 August 2026 and assigned it the closest of 31 fixed categories, at 100% 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
@i_linux/1147 · this entry3 Jul 2026, 05:44 UTC@linuxchmod/108215 Jul 2026, 07:36 UTC0.9912 days
@i_linux/1150 · this entry13 Jul 2026, 07:48 UTC@linuxchmod/108420 Jul 2026, 07:53 UTC0.997 days
@i_linux/1154 · this entry27 Jul 2026, 07:17 UTC@linuxchmod/109229 Jul 2026, 10:11 UTC0.992 days
@i_linux/1145 · this entry18 Jun 2026, 08:55 UTC@linuxchmod/108114 Jul 2026, 08:24 UTC0.9926 days
@i_linux/1151 · this entry15 Jul 2026, 07:36 UTC@linuxchmod/108523 Jul 2026, 14:18 UTC0.998 days
@i_linux/1148 · this entry7 Jul 2026, 06:28 UTC@linuxchmod/108317 Jul 2026, 07:42 UTC0.9710 days
Every channel this entry shares post bodies with
ChannelMatching postsText overlapTypical gapPublished first
@linuxchmod6 (6/6 hand-verifiable sample passed)0.998 daysthis entry (60)

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 12 comparable posts for this entry, running 18 June 2026 to 3 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 @i_linux — 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

1,9631,9891,9767 August 2026 — 1,989 subscribers7 August 2026 — 1,989 subscribers10 August 2026 — 1,986 subscribers13 August 2026 — 1,972 subscribers17 August 2026 — 1,963 subscribers7 August 202617 August 2026
5 measurements spanning 10 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 1,959–1,993 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
17 Aug 2026, 12:351,963-9
13 Aug 2026, 23:471,972-14
10 Aug 2026, 17:081,986-3
7 Aug 2026, 11:561,989no change
7 Aug 2026, 00:461,989first reading

Engagement

13 posts held, back to 15 June 2026the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 2 pagesof Telegram’s post history, 20 posts per page.

ERR · 30 days
15.2%
avg views ÷ 1,963 subscribers
Avg views / post
298
5 posts measured
Reaction rate
1.07%
reactions ÷ views · ER floor
Posts in window
5
of 13 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 3 August 2026
Posts held13 (15 June 20263 August 2026)
Views total1,491
Reactions total16
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken7 Aug 2026, 17:09 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.

Reaction mix

41 reactions across 13 posts, in 5 distinct kinds. The most used accounts for 41.5% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
👍1741.5%
1331.7%
🔥819.5%
👎24.88%
👏12.44%

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

Measured over the 13 most recent posts we hold, published 15 June 2026 to 3 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

3 Aug 2026, 06:32 UTC188 views1 reactionsread 7 August 2026
Photo

Топ-10 артефактов Linux для расследования инцидентов Несмотря на то что Windows остается самой распространенной ОС, о чем знают в том числе атакующие, нельзя оставлять без внимания другие системы, а уж тем более Linux (ладно-ладно, GNU/Linux). Сегодня российские компании все чаще пользуются Linux из соображений импортозамещения, но эта ОС по-прежнему более распространена именно как серверное решение. А теперь предс

👍1

30 Jul 2026, 21:02 UTC327 views9 reactionsread 7 August 2026

🎉 С Днём системного администратора! Сегодня можно официально ничего не чинить. Потому что существует закон сисадмина: 🟢 Пока админ рядом — всё работает. 🔴 Как только он ушёл в отпуск — ломается всё сразу. Желаем, чтобы серверы не знали слова panic, диски не пищали SMART'ом, а пользователи звонили только с фразой: «Спасибо, всё отлично работает!»

9

29 Jul 2026, 10:13 UTC338 views2 reactionsread 7 August 2026
Photo

GTFOBins Это список двоичных файлов Unix, которые могут быть использованы для обхода локальных ограничений безопасности в неправильно сконфигурированных системах. В проекте собраны легитимные функции двоичных программ Unix, которые могут быть использованы для выхода из ограниченных оболочек, повышения или сохранения повышенных привилегий, передачи файлов, порождения bind и reverse оболочек, а также для решения друг

1👍1

27 Jul 2026, 07:17 UTC356 views1 reactionsread 7 August 2026

Назначения подсетей IPv4 и использование некоторых маршрутизируемых адресов в качестве локальных Как-то, очередной раз настраивая роутер с LTE модемом, обратил внимание, что IP адрес оператором мне был выдан из сети 11.0.0.0/8. Уже не помню точно, что за оператор это был, да и не имеет это значения, но задумался: а как так-то? Ведь вряд ли сотовый оператор будет бесплатно раздавать динамические публичные IP адреса,

👍1

25 Jul 2026, 11:10 UTC282 views3 reactionsread 7 August 2026

🚀 Подборка полезных IT каналов в Max Системное администрирование, DevOps 📌 https://max.ru/i_odmin Все для системного администратора https://max.ru/bash_srv Bash Советы https://max.ru/sysadminof Книги для админов, полезные материалы https://max.ru/i_odmin_book Библиотека Системного Администратора https://max.ru/i_devops DevOps: Пишем о Docker, Kubernetes и др. https://max.ru/tipsysdmin Типичный Сисадмин https://max

👎2👍1

15 Jul 2026, 07:36 UTC425 views1 reactionsread 7 August 2026
Photo

Cron — лучшие практики Планировщик задач cron(8) существует с 7 версии Unix, а его синтаксис crontab(5) знаком даже тем, кто нечасто сталкивается с системным администрированием Unix. Это стандартизированный, довольно гибкий, простой в настройке и надёжно работающий планировщик, которому пользователи и системные пакеты доверяют управление важными задачами. У простоты cron(8), как и многих старых Unix-инструментов, е

👍1

13 Jul 2026, 07:48 UTC402 views3 reactionsread 7 August 2026

Команда findmnt Это простая утилита командной строки, используемая для отображения списка подключенных файловых систем или поиска файловой системы в /etc/fstab, /etc/mtab или /proc/self/ mountinfo. Для отображения списка подключенных файловых систем, выполните в командной строке следующую команду. По умолчанию команда findmnt отображает файловые системы в древовидном формате. # findmnt Чтобы отобразить информацию

👍3

8 Jul 2026, 06:21 UTC409 views2 reactionsread 7 August 2026
Photo

Подборка скриптов PowerShell для работы с Azure, Active Directory, SCCM, SCSM, Exchange ... Пример скрипта function Get-LocalUser { <# .SYNOPSIS This script can be list all of local user account. .DESCRIPTION This script can be list all of local user account. The function is using WMI to connect to the remote machine .PARAMETER ComputerName Specifies the computers

👍1🔥1

7 Jul 2026, 06:28 UTC394 views1 reactionsread 7 August 2026
Photo

Конвертация PFX в CRT и KEY Для ECDSA: openssl pkcs12 -in certificate_ECDSA.pfx -out certificate_ECDSA.key -nodes -nocerts openssl pkcs12 -in certificate_ECDSA.pfx -out certificate_ECDSA.crt -nokeys Если pfx запаролен, будет запрошен Import Password. Для RSA: openssl pkcs12 -in certificate_RSA.pfx -clcerts -nokeys -out certificate_RSA.crt openssl pkcs12 -in certificate_RSA.pfx -nocerts -out certificate_RSA-encryp

👍1

3 Jul 2026, 05:44 UTC455 views4 reactionsread 7 August 2026

Простое копирование ssh ключей между серверами c использованием утилиты ssh-copy-id Традиционно администраторы решают задачу копирования ssh ключей между серверами путем копирования содержимого файла /root/.ssh/id_rsa.pub с сервера server1 на server2 в файл /root/.ssh/authorized_keys. Копируют обычно из одного терминала в другой, но есть более изящное решение — это использование утилиты ssh-copy-id, которая позволяе

👍21🔥1

23 Jun 2026, 07:18 UTC505 views3 reactionsread 7 August 2026

Шпаргалка по часто используемым командам systemctl 1. Посмотреть статус службы. Покажет статус службы на примере сети network systemctl status network 2. Запустить сервис. Запустит сервис баз данных на примере mysql systemctl start mysql 3. Остановить службу. Остановит сервис времени ntpd systemctl stop ntpd 4. Перезапустить службу. Перезапустит веб-сервер nginx systemctl restart nginx 5. Включить автозапуск слу

🔥2👍1

18 Jun 2026, 08:55 UTC516 views4 reactionsread 7 August 2026

Команды Linux: Пользователи и группы groupadd group_name — создать новую группу с именем group_name groupdel group_name — удалить группу group_name groupmod -n new_group_name old_group_name — переименовать группу old_group_name в new_group_name useradd -c "Nome Cognome" -g admin -d /home/user1 -s /bin/bash user1 — создать пользователя user1, назначить ему в качестве домашнего каталога /home/user1, в качестве shell'а

👍31

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

Citation-graph rank

Citation-graph rank — 1,052,756 of 1,550,164entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.

Mentions

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

Names

Channels on the register whose handles appear in this channel's posts.

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 17 August 2026 — this entry's latest reading, not the date you are reading this.

“Системный администратор” (@i_linux), 1,963 subscribers as measured 17 August 2026. Telegram Register, tgregister.com/channel/i_linux.

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.