3 measurements spanning 2 days, net +1. 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 110–111 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)
Subscribers
Change
9 Aug 2026, 07:02
111
no change
8 Aug 2026, 15:49
111
+1
7 Aug 2026, 16:47
110
first reading
Engagement
11 posts held, back to 8 December 2025 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 1 pageof Telegram’s post history, 20 posts per page.
ERR · 30 days
67.6%
avg views ÷ 111 subscribers
Avg views / post
75.0
1 post measured
Reaction rate
2.67%
reactions ÷ views · ER floor
Posts in window
1
of 11 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 19 July 2026
Posts held
11 (8 December 2025 – 19 July 2026)
Views total
75
Reactions total
2
Forwards / comments
not exposed by the public surface — not measured, not estimated
Readings taken
9 Aug 2026, 07:02 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
Links
4
Lifetime counters from Telegram’s own channel header, read 9 August 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.
Reaction mix
36 reactions across 9 posts, in 4 distinct kinds. The most used accounts for 75.0% of them.
Every reaction kind recorded on the sample, most used first
Reaction
Count
Share
Share, drawn
❤
27
75.0%
❤🔥
6
16.7%
👍
2
5.56%
🤣
1
2.78%
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 9 of the 11 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 36reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 11 most recent posts we hold, published 8 December 2025 to 19 July 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.
همین الان این ریلز رو ببین! 🚀
یه آسیبپذیری بحرانی جدید در وردپرس کشف شده که یه فرصت طلایی برای شکارچیهای باگ (Bug Hunters) ایجاد کرده. اگه دست بجنبونی و از متدولوژی و ابزارهایی که توی این ویدیو و دایرکت توضیح دادم استفاده کنی، شانس بالایی برای گرفتن بانتیهای سنگین داری.
بانتی ها این ریلز به دلیل اینکه ایمپکت کرتیکال هست از ۲-۳ هزاردلار به بالا هست پس زمان به شدت مهمه
تایملاین این آسیبپذیری به شدت حساسه؛ پس معطل…
این داستان مدیریت کانتکست اینقدری جدیه که حتا توی یکی از بلاگ پستایی که میخوندم دیدم یه ریسرچر ادعا کرده بود با ستاپ یه فریمورک درست حسابی (دادن اطلاعات کم ولی با کیفیت + ابزار های مناسب) تونستن با یه مدل 5.1B پارامتری باگایی که mythos زده بود رو بزنن.
But here is what we found when we tested: We took the specific vulnerabilities Anthropic showcases in their announcement, isolated the relevant code, and ran them thro…
یه چندتا تکنیک جالب هم هست برای کاهش مصرف Context.
---
یکی اینکه وقتی یه فایل رو بهش میدید و میخواید ادیتش کنه، بیاد به جای اینکه کل فایل رو از اول بنویسه، با ابزار بگه که خط مثلا 12 تا 15 رو پاک کن و فلان متن رو جاش بنویس. اینجوری توکن خروجیش خیلی کاهش پیدا میکنه مخصوصا توی فایلای حجیم.
---
یا مثلا یه skill براش بنویسید که هر دفعه که یک ریکوئست Http ارسال میکنه، به جای اینکه بیاد کل ریسپانس رو انالیز کنه، یه اسکریپ…
حالا طبق چیزی که من بعد سرچ بهش رسیدم تقریبا مهم ترین چیز برای استفاده از AI توی امنیت، محتوای Contextای هست که بهش داده میشه که شامل اینا میشه:
Skills
Target Info
User instructions
---
چندتا نکته هست که باید توی Context رعایت بشه
- زیاد و شلوغ نباشه که باعث توهم میشه
- کوتاه و دقیق باشه (هر ایجنت مخصوص یک کار) (مثل کاری که یاشار انجام میده، ریکوئست رو بگیر، اینم Skillهات، پاشو برو روشون تست کن) (یه عده هم مخالف…
یه خلاصه ساده راجب بیسیک LLMها بگم (قابل اسکیپ/زیاد مهم نیست/برای درک بهتر)
اقا AI اوایل صرفا تولید تکست بود (البته هنوزم هست).
- یک متن میدادی
- جواب رو به صورت text میگرفتی
اما یک موردی، اگه دوباره پیام بدی AI پیام قبلیت رو یادش نمیاد چی بوده، چون صرفا کارش گرفتن تکست و تولید متن خروجیه، به خودیه خود حافظه ای نداره.
اتفاقی که میوفته اینه: (پیام اول شما + جواب LLM + پیام جدید شما) برای LLM ارسال میشه، اینجوری م…
Showing the 11 most recent of 11 posts we hold for @khode_4li. 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 — 919,549 of 1,189,255entries 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
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 1 registered channel — 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 August 2026 — this
entry's latest reading, not the date you are reading this.
“4li” (@khode_4li), 111 subscribers as measured 9 August 2026. Telegram Register, tgregister.com/channel/khode_4li.
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.
