4 measurements spanning 10 days, net +10. 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 4,877–4,890 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)
Subscribers
Change
16 Aug 2026, 22:26
4,888
+7
10 Aug 2026, 11:02
4,881
+2
7 Aug 2026, 07:25
4,879
+1
7 Aug 2026, 02:01
4,878
first reading
Engagement
22 posts held, back to 22 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 8 pagesof Telegram’s post history, 20 posts per page.
ERR · 30 days
12.0%
avg views ÷ 4,888 subscribers
Avg views / post
588
22 posts measured
Reaction rate
0.83%
reactions ÷ views · ER floor
Posts in window
22
of 22 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 17 of 22 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
22 (22 July 2026 – 11 August 2026)
Views total
12,935
Reactions total
83
Forwards / comments
not exposed by the public surface — not measured, not estimated
Readings taken
12 Aug 2026, 05:10 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
83 reactions across 17 posts, in 6 distinct kinds. The most used accounts for 74.7% of them.
Every reaction kind recorded on the sample, most used first
Reaction
Count
Share
Share, drawn
❤
62
74.7%
👍
12
14.5%
👏
6
7.23%
❤🔥
1
1.20%
🍓
1
1.20%
🔥
1
1.20%
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 17 of the 22 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 83reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 22 most recent posts we hold, published 22 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.
لما بقعد اتناقش مع CHATGPT or Claude في ال architecture الخاص باي مشروع بشتغل عليه آخرها كان product lens يبقي open source يقدر اي مشروع يستخدمه
اتكلمنا في تفاصيل كتير جدا ومناقشات علي مستوي ال architecture وال layers وخلافه وهل محتاجين نعمل كل حاجه from scratch ولا نستخدم حاجات موجودة تناسب ال requirements اللي عندنا
وهو اقترح شويه github links لمشاريع اقدر استفيد منها في ال RAG Pipeline وبصيت علي كل مشروع وعرفت ف…
بعد ما وصلنا بفضل الله لـ 117 🌟 علي الـ repo فده شجعني ان اكمل في مشروع الـ arch-wiki
من فترة كنت اشتغلت على arch-wiki وكانت الفكرة إننا نعمل Architecture Documentation للمشاريع بشكل Automatic وفي نفس الوقت تكون مفيدة للـ Developers والـ AI Tools
النهارده عملنا شوية Updates جديدة وحاجات مهمة اتضافت بناء علي الفيدباك اللي وصلنا وان شاءالله تبقي مفيدة
1. الـ Prerequisites & Setup Pipeline.
دلوقتي الـ arch-wiki تقدر …
بالنسبه لموضوع الخطوط والباكبورت اللي اتفتح والكوارث اللي في الشركات والمسخرة اللي بتحصل ويعني ايه اشترى خطوط بصور بطايق بتاعة ناس تانيه طبعا الناس اللي سرقت صور البطايق والناس اللي اشترتهم دول المفروض يتحبسوا وش والشركات الاتصالات تتدفع تعويضات وغرامات غصب عن اللي خلفوهم واللي جابهوم عشان شركات وسخه من الاخر وعارفين الفساد وعايشين فيه
طب عشان نحل الموضوع ده نعمل ايه
اولا اي واحد بيشترى اي خط جديد ومعندوش خط مسبق لو…
في المنتورشيب عندنا في الشهر التاني بيكون فيه آخر Task في جزء الـ Database وهو إننا نعمل Database Optimization للـ Queries اللي اشتغلنا عليها طول الشهر
بس قبل ما نبدأ الـ Optimization بيكون عندنا خطوة مهمة جدا
إننا نملي الـ Database بحجم Data كبير
الهدف مش مجرد إنك تعرف تعمل Insert لملايين الـ Records الهدف الحقيقي إنك تكسر رهبة التعامل مع الداتا الكبيرة
في المنتورشيب حجم الداتا بيوصل لـ 50 مليون Record عشان لما ت…
بصراحة السوق بقى أصعب من أي وقت فات
للأسف في شركات كتير خصوصا في الشرق الأوسط بقت شايفة إن طالما فيه AI Tools يبقى مفيش داعي تدفع مرتبات كبيرة، ونجيب أي حد يمشي الدنيا لكن الحقيقة إن الموضوع مش بالبساطة دي
في أوروبا لسه في شركات كتير بتدور على الشخص اللي عنده خبرة حقيقية وفي نفس الوقت بيعرف يستخدم الـ AI صح ليه؟ لأن الخبرة هي اللي بتفرق
الشخص اللي عنده خبرة هو اللي يعرف يعمل Architecture صح ويسأل الأسئلة الصح ويطلع…
Free kimi 3
https://www.tokenrouter.com/?fbclid=Iwb21leATYdyZjbGNrBNh3G3Bkb2YBZXh0bgNhZW0CMTEAc3J0YwZhcHBfaWQMMzUwNjg1NTMxNzI4AAEeEfzW14Iqf_U9VnmPsfXV5RGmHL2hnap20d8ljVSsdNlpJfdX7RNS99itaOU_aem_K9sFmz_UKen-pS-sJektag
الفكرة دي بقالها كام يوم شاغلة دماغي كل الناس دلوقتي بتتكلم عن AI Agents
Backend Agent
Frontend Agent
DevOps Agent
UI Agent
Architecture Agent
وكل ما عدد الـ Agents يزيد الناس تحس انها خلاص عملت كل حاجة بس وأنا بفكر حسيت إننا ممكن نكون بنحل المشكلة من الاتجاه الغلط بقي عندنا كمية agents كتير وكل مرة ببدا من الصفر
أنا ليه أصلا محتاج Backend Agent يفكر هيعمل Payment إزاي؟ وليه محتاج Architecture Agent يقرر Database …
من يومين نزلت ال Arch Wiki Skill وكان الهدف الأساسي منها إنها تساعد أي حد يدخل Project جديد أو حتى Project قديم مفيهوش Documentation محترمة إنه يفهم الدنيا أسرع بدل ما يقعد أيام بيدور ويسأل
من أكتر الحاجات اللي بتضيع وقت أي Software Engineer هي إنه يفهم ال Architecture بتاعة المشروع خصوصا إن في مشاريع كتير جدا مفيهاش أي Documentation تشرح هي ماشية إزاي
ومن هنا جات فكرة Feature من أهم الـ Features الموجودة في ال Ski…
Showing the 12 most recent of 22 posts we hold for @ta5rif_mj. 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 — 935,823 of 1,548,671entries 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 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 16 August 2026 — this
entry's latest reading, not the date you are reading this.
“تخاريف مبرمج” (@ta5rif_mj), 4,888 subscribers as measured 16 August 2026. Telegram Register, tgregister.com/channel/ta5rif_mj.
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.