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.
5 measurements spanning 6 days, net +30. 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 6,766–6,805 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)
Subscribers
Change
12 Aug 2026, 22:43
6,800
+7
9 Aug 2026, 23:43
6,793
+20
7 Aug 2026, 04:40
6,773
+3
6 Aug 2026, 11:00
6,770
no change
6 Aug 2026, 10:59
6,770
first reading
Engagement
38 posts held, back to 27 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 10 pagesof Telegram’s post history, 20 posts per page.
ERR · 30 days
13.7%
avg views ÷ 6,800 subscribers
Avg views / post
933
37 posts measured
Reaction rate
0.663%
reactions ÷ views · ER floor
Posts in window
38
of 38 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. It is computed over the 27 of 37 measured posts that carry a reaction reading, and over those same posts' views.
What these figures were computed from
Window
Rolling 30 days · latest post in window 11 August 2026
Posts held
38 (27 July 2026 – 11 August 2026)
Views total
34,523
Reactions total
164
Forwards / comments
not exposed by the public surface — not measured, not estimated
Readings taken
12 Aug 2026, 02:46 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
164 reactions across 24 posts, in 6 distinct kinds. The most used accounts for 46.3% of them.
Every reaction kind recorded on the sample, most used first
Reaction
Count
Share
Share, drawn
❤
76
46.3%
😁
45
27.4%
👍
36
22.0%
🔥
4
2.44%
🥰
2
1.22%
👏
1
0.61%
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 27 of the 38 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 164reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 38 most recent posts we hold, published 27 July 2026 to 11 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.
🔰فعلا این سه اصطلاح را یکبار برای همیشه یادت باشه:
🔹Mesa
یک مجموعهی نرمافزاری منبعباز است که پیادهسازیهای آزاد از APIهای گرافیکی مانند OpenGL، Vulkan و OpenCL را برای سیستم عاملهای لینوکسی فراهم میکند و به عنوان لایهی میانی بین سختافزار گرافیکی و برنامههای کاربردی عمل مینماید.
🔹Vulkan
یک API کمسطح و چندسکویی برای رندرینگ سهبعدی و محاسبات موازی در کارتهای گرافیکی است که توسط کنسرسیوم Kronos توسعه یافته…
جالب بود بچهها:
🔰 یک رابط کاربری متنی داخل ترمینال یا (TUI) برای مدیریت کل استک وب محلی
🔹ابزارReeve یک مدیر محیط localhost برای توسعه است که ابزارهای رایج توسعه را در یک رابط ترمینال جمعآوری میکند.
🔹قابلیتها:
تغییر نسخههای PHP؛مدیریت Caddy، Apache و nginx؛
کار با پایگاههای داده؛
تنظیم SSL و DNS محلی؛مدیریت سایتهای پارک شده؛
مشاهده ترافیک لحظهای؛
داشتن فول استک محلی در دسترس بدون نیاز به دهها دستور جداگا…
#نترس_و_ببین
🔰همه میدونیم سرعت هارد دیسک از رم و پردازنده کندتره. گاهی سرعت سیستم کاهش پیدا میکنه و کند میشه و نمیدونیم چرا؟
🔹پس برای اینکه بفهمیم چرا: ترمینال باز کن. دستور بزن:
sudo iotop -o
این دستور فقط پردازههایی که دارن از دیسک استفاده میکنن رو نشون میده.
اگر نصب نبود. بسته iotopنصب کن
#نترس_و_ببین
🔰این دستور رو توی ترمینال بزن و ۵ دقیقه بهش زل بزن.😁
🔹 ببین هر ثانیه چه ارتباطات شبکهای (TCP/UDP) برقرار میشه، چه پروسسهایی دارن ارتباط برقرار میکنن، و پورتهای باز رو بشناس.
watch -n 1 'ss -tupna | grep -v "^State" '
یه تمرین عالیه برای Network Forensics
#نترس_و_ببین
🔰 چطور بدون استخراج، محتوای فایل فشرده .gz را ببینیم؟
ترمینال باز کن و دستور زیر و اسم فایل رو بنویس
zcat filename.gz
این دستور محتوای فایل را مستقیماً در ترمینال نمایش میدهد، بدون اینکه یک نسخهٔ استخراجشده روی دیسک ایجاد کند.
منبع: کتاب ۱۰۰۱ دستورالعمل عملی عیبیابی لینوکس
🔹 اخبار و آموزش بیشتر در:
https://learninghive.ir
🔰 یک درایور ۲۷ ساله از هسته لینوکس حذف شد؛ AI هم در این تصمیم نقش داشت
🔹درایور Moxa Intellio / mxser که پشتیبانی از کارتهای سریال چندپورتی قدیمی Moxa را فراهم میکرد، پس از حدود ۲۷ سال از هسته لینوکس کنار گذاشته شد. این درایور از سال ۱۹۹۹ در Kernel حضور داشت و در نهایت با توجه به قدیمیشدن سختافزار و نبود نیاز عملی به ادامه نگهداری آن حذف شد.
🔹نکته جالب اینجاست که Moxa مدتهاست این سختافزار را متوقف کرده و حتی د…
🔰سرمایهگذاری ۵ میلیارد دلاری IBM و Red Hat برای امنیت Open Source 🛡
🔹در مه ۲۰۲۶، IBM و Red Hat تعهدی ۵ میلیارد دلاری برای تقویت امنیت نرمافزارهای متنباز اعلام کردند. این برنامه در ادامه با توسعه پروژه Lightwell دنبال شده و بیش از ۲۰ هزار مهندس در این اکوسیستم برای شناسایی و رفع آسیبپذیریها مشارکت خواهند داشت.
تمرکز این برنامه فقط روی Patch کردن آسیبپذیریها نیست؛ بلکه استفاده از AI برای شناسایی، تحلیل و اصلاح …
🔰سازمان Linux Foundation اقتصاد AI را هم وارد قلمرو Open Source کرد.
🔸در ۴ اوت ۲۰۲۶، Linux Foundation از راهاندازی Tokenomics Foundation خبر داد؛ بنیادی جدید با مشارکت اولیه حدود ۳۰ شرکت و سازمان که هدف آن ایجاد استانداردهای باز و Vendor-neutral برای اندازهگیری هزینه، ارزش و بازگشت سرمایهگذاری در AI است.
مسئله اصلی این است که شرکتها امروز روشهای متفاوتی برای محاسبه هزینه و ROI سیستمهای AI دارند؛ از هزینه GPU …
🔰 حمایت غولهای فناوری از بهروزرسانی Firmware در لینوکس
بنیاد لینوکس اعلام کرده است که شرکتهای Dell، HP، Lenovo و NVIDIA به عنوان اعضای اصلی به پروژه Linux Vendor Firmware Service (LVFS) پیوستهاند.
🔹 این حمایت مالی، آینده این پروژه متنباز را برای سالهای آینده پایدارتر میکند و توسعه زیرساخت بهروزرسانی امن Firmware در لینوکس را تقویت خواهد کرد.
📌 مهمترین تغییرات و دستاوردها:
🔹 تضمین حمایت مالی و توسعه بلندمدت پ…
🔰کرنل Linux 7.2؛ وقتی هوش مصنوعی وارد فرآیند بررسی کد هسته لینوکس شد
هسته Linux 7.2 به مراحل پایانی توسعه نزدیک شده و یکی از جالبترین اتفاقات این چرخه، نقش پررنگ ابزارهای هوش مصنوعی در پیدا کردن باگهای پنهان در کد Kernel است.
🔹نسخه Linux 7.2-rc7 در آستانه انتشار قرار دارد و در روزهای اخیر مجموعهای از اصلاحات مهم برای آن آماده شده است. یکی از مهمترین بخشها، زیرسیستم HWMON (Hardware Monitoring) است؛ بخشی از Ker…
#نترس_و_ببین
🔰 مانیتور لحظهای تغییرات فایل در لینوکس
بخواهی بفهمی یک فایل چه زمانی تغییر میکند.رویدادهای یک فایل رو مانیتور کن.
ترمینال باز کن.دستور زیر بزن.
دستور:
inotifywait -m /etc
رویدادهایی مثل:
ایجاد فایل CREATE
حذف فایل DELETE
تغییر محتوا MODIFY
تغییر نام MOVED_FROM / MOVED_TO
دسترسی به فایل ACCESS
را نمایش میدهد.
❤3👍1
Signed hosein seilany https://seilany.ir/
Showing the 12 most recent of 38 posts we hold for @linuxtnt. 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 — 151,885 of 1,151,006entries 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.
Forward network
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
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.
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.
تکنولوژی،خبری،هوش مصنوعی، @ITSecurityComputer · 164,944 Telegram ranks this channel #67 of 71 here — alongside 70 others — read 12 August 2026
Computer & IT Engineering @Computer_IT_Engineering · 188,254 Telegram ranks this channel #67 of 76 here — alongside 75 others — read 11 August 2026
This channel appears in 2 seed channels' Telegram-generated recommendation lists in total. 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 12 August 2026 — this
entry's latest reading, not the date you are reading this.
“linuxtnt(linux tips and tricks)” (@linuxtnt), 6,800 subscribers as measured 12 August 2026. Telegram Register, tgregister.com/channel/linuxtnt.
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.