Microsoft выпустила антивирус Microsoft Defender… для Linux. Серьёзно. https://techcommunity.microsoft.com/blog/microsoftdefenderatpblog/secure-linux-desktops-with-microsoft-defender/4560822 @linuxos_tg
custom 5249138669293413940189🤣156😁24🔥7🤔6🥰6❤5🤝1

Channel
@linuxos_tg
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Advertising · Posts · Posts edited after publishing · Citations · Handles named that no longer answer · Cite this entry
56,944subscribers
-221 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 31,623–100,000.
| Telegram ID | -1002488029349 |
|---|---|
| Type | Channel |
| Username | @linuxos_tg |
| Description | Всё самое интересное из мира Linux и опенсорса Сотрудничество, реклама: @devmangx РКН: https://clck.ru/3PKrKN Работаем с @Spiral_Yuri |
| Created | Between 1 September 2024 and 31 March 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 6 August 2026 |
| Last confirmed live | 16 October 2026 |
| Measurements held | 40 |
| Confirmed unchanged | 1 time, most recently 16 October 2026 |
| On Telegram | t.me/linuxos_tg |
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 20 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.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 16 Oct 2026, 23:06 | 56,944 | +77 |
| 15 Oct 2026, 22:08 | 56,867 | +164 |
| 14 Oct 2026, 22:38 | 56,703 | +89 |
| 13 Oct 2026, 15:56 | 56,614 | +63 |
| 9 Oct 2026, 19:18 | 56,551 | -27 |
| 5 Oct 2026, 09:58 | 56,578 | -15 |
| 29 Sept 2026, 07:20 | 56,593 | -138 |
| 17 Sept 2026, 21:20 | 56,731 | -4 |
| 15 Sept 2026, 16:42 | 56,735 | +9 |
| 13 Sept 2026, 23:42 | 56,726 | -26 |
| 12 Sept 2026, 03:19 | 56,752 | -37 |
| 9 Sept 2026, 19:38 | 56,789 | +1 |
| 6 Sept 2026, 09:21 | 56,788 | +51 |
| 3 Sept 2026, 23:21 | 56,737 | -2 |
| 2 Sept 2026, 15:24 | 56,739 | -18 |
| 1 Sept 2026, 13:04 | 56,757 | -3 |
| 31 Aug 2026, 15:46 | 56,760 | -4 |
| 30 Aug 2026, 18:03 | 56,764 | +4 |
| 29 Aug 2026, 21:33 | 56,760 | -11 |
| 28 Aug 2026, 20:08 | 56,771 | first reading |
58 posts held, back to 29 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 155 pages of 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.
| Window | Rolling 30 days · latest post in window 16 October 2026 |
|---|---|
| Posts held | 58 (29 July 2026 – 16 October 2026) |
| Views total | 337,860 |
| Reactions total | 4,873 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 16 Oct 2026, 23:56 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 16 October 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.
Measured directly from 3 videos 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.
15,326 reactions across 58 posts, in 29 distinct kinds. The most used accounts for 25.5% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 5249138669293413940 | 3,902 | 25.5% | |
| ❤ | 2,738 | 17.9% | |
| 😁 | 1,820 | 11.9% | |
| 👍 | 1,653 | 10.8% | |
| 🎉 | 1,266 | 8.26% | |
| 🤣 | 1,068 | 6.97% | |
| 🔥 | 967 | 6.31% | |
| custom 5467713446227234408 | 601 | 3.92% | |
| 😢 | 391 | 2.55% | |
| 🤔 | 335 | 2.19% | |
| 💯 | 89 | 0.581% | |
| 🙈 | 62 | 0.405% | |
| 🥰 | 52 | 0.339% | |
| 🫡 | 52 | 0.339% | |
| 😱 | 51 | 0.333% | |
| 🌚 | 49 | 0.32% | |
| 🤷♂ | 46 | 0.3% | |
| 🌭 | 36 | 0.235% | |
| 🤯 | 29 | 0.189% | |
| 👻 | 23 | 0.15% | |
| 9 further kinds | 96 | 0.626% |
Custom emoji. 2 of the rows above are Telegram custom emoji, which the public preview renders as an element carrying only a numeric id — no character, and no image we can reach. The id is printed as-is rather than substituted with a look-alike glyph, because a stand-in would be our invention showing where a measurement should be. The counts beside them are Telegram’s.
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 58 of the 58 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 15,326 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 58 most recent posts we hold, published 29 July 2026 to 16 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.
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 |
|---|---|---|---|
| 2W5zFGNvsmB | 1 | 14 August 2026 | 14 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 58 most recent posts we hold, published 29 July 2026 to 16 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.
Microsoft выпустила антивирус Microsoft Defender… для Linux. Серьёзно. https://techcommunity.microsoft.com/blog/microsoftdefenderatpblog/secure-linux-desktops-with-microsoft-defender/4560822 @linuxos_tg
custom 5249138669293413940189🤣156😁24🔥7🤔6🥰6❤5🤝1
Epic Games наконец-то переносит Fortnite на Linux после нескольких лет отказа от поддержки из-за проблем с античитом Переработанный лаунчер Epic Games уже доступен в предварительной версии и впервые официально поддерживает Linux. Следующий шаг – Fortnite. Epic перерабатывает Easy Anti-Cheat для Linux и сотрудничает с мейнтейнерами дистрибутивов, чтобы обеспечить необходимые для запуска игры требования безопасности.…
🔥104custom 524913866929341394029❤15😁7👍4🤔3🙏3
💬👨💻🐍💩🤖🤖🐧👩💻🧑💻👋🦀 Дождались! Ребята сделали крутейший канал про IT новой эпохи Нейросети, ИИ-агенты, вайбкодинг, вайбхакинг и новые инструменты уже меняют привычный мир технологий. Там разбирают эти изменения и другие интересные IT-темы на простых картинках и понятном языке, а еще делятся полезными ресурсами и свежими новостями Подписывайтесь: @IT_Portal
🤣23custom 524913866929341394016❤6🔥4🙈3👍1
Линус Торвальдс назвал правила, запрещающие использование ИИ, «ПОЛНЕЙШЕЙ ГЛУПОСТЬЮ» и «идиотизмом». Говоря о разработке ядра Linux, Торвальдс заявил: «Мы не собираемся вводить глупые правила вроде "нельзя использовать инструменты для определённых задач"». https://lkml.iu.edu/2610.1/13255.html @linuxos_tg
❤161custom 5249138669293413940105👍44🔥5🤔5🥰5🙈4😁2
Линус Торвальдс, похоже, всерьёз взялся за вайбкодинг ядра Linux. Он работает над новой веткой, направленной на ускорение чтения из страничного кеша. Торвальдс: «Код, тестовые программы, ревью изменений из списка выше и первый черновик этого текста были подготовлены с помощью ИИ-ассистента для написания кода (Claude Code) под моим руководством». https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/com…
custom 5249138669293413940185👍93🤔18🫡8❤6😢4🙈4🤷♂3
У кого ниже задержка… у Wayland или X11 (Xorg / XLibre)? Разработчики и сторонники Wayland уже много лет утверждают, что Wayland быстрее, имеет меньшую задержку и эффективнее X11. Nvidia провела исследование этого вопроса… и выяснила, что… Wayland НЕ обеспечивает меньшую задержку по сравнению с существующими X11-серверами. Это показывает, что Wayland не смог достичь одной из своих ключевых целей - устранить архит…
custom 5249138669293413940219🔥48👍23❤15😁10🤣7👨💻4💯3
DevOps-инструмент недели: Radar При диагностике Kubernetes приходится переключаться между kubectl, Helm, Argo CD и сетевыми дашбордами, чтобы понять, что происходит в кластере. Radar собирает всё в одном интерфейсе. Это открытый Kubernetes UI, который можно запустить локально одним бинарным файлом и подключить напрямую к кластеру. Что умеет: • Показывает связи между ресурсами Kubernetes. • Отображает события и изм…
❤35👍6🌚3custom 52491386692934139403
Прошлая неделя стала второй за всю историю по количеству отправленных в ядро Linux изменений, сгенерированных ИИ, лишь немного не дотянув до рекорда неделей ранее — 1 553 отправки кода, сгенерированного LLM. Таким образом, с начала сентября в ядро уже отправили 5 470 изменений, сгенерированных ИИ. Это 17,6% от всех пулл реквестов с кодом. @linuxos_tg
custom 5249138669293413940124custom 546771344622723440822❤10😢9✍6👍5
@linuxos_tg
🤣285😁47custom 524913866929341394014🔥6❤3🥰2custom 54677134462272344082
Сложный, но критически важный процесс: усиление защищенности инфраструктуры. Для него нужно понимать специфику угроз и особенности IT-систем. Хорошо, что Сидни поделилась ссылкой на библиотеку экспертных материалов по этой теме от BI.ZONE. На странице вы найдете подборку статей с практическими рекомендациями, как: 🔵Устранить небезопасные настройки. 🔵Сократить поверхность атаки. 🔵Закрыть уязвимые места и проверить …
😁45custom 524913866929341394020❤4🌚4🌭4🤣4👍1
Кто-то попытался протащить в OpenBSD клоны GNU CoreUtils, переписанные на Rust Тео де Раадт, руководитель OpenBSD, идею не оценил. А его ответы были... занятными. "Пахнет продвижением повестки." "А, потому что это написано на Rust. Ваша повестка уже слишком заметна." "В этом нет никакого смысла. Никому не нужны бинарники, которые ведут себя чуть иначе, как часть привычного воркфлоу... В этой вселенной нет людей,…
👍207custom 524913866929341394057🔥21😁7❤5😢3custom 54677134462272344083
Проекту GNU сегодня исполняется 43 года 1983 год: Ричард Столлман объявил планы разработать «Unix-совместимую систему под названием GNU (GNU’s Not Unix) и распространять её бесплатно» С днём рождения! 🥳 @linuxos_tg
🎉299❤94🔥39👍9custom 52491386692934139405🤩3custom 54677134462272344083
Showing the 12 most recent of 58 posts we hold for @linuxos_tg. 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.
@linuxos_tg edited 1 post 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.
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
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.
Named by 12 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.
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.
@linuxos_tg named 2 handles 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.
References a handle that is not a live channel — we have no record it ever was one.
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 16 October 2026 — this entry's latest reading, not the date you are reading this.
“Мир Linux” (@linuxos_tg), 56,944 subscribers as measured 16 October 2026. Telegram Register, tgregister.com/channel/linuxos_tg.
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.