Channel
@ta5rif_mj
On this record: Topic · Growth · Engagement · Reactions · Posts · Citations · Telegram's recommendations · Cite this entry
4,879subscribers
+1 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
| Telegram ID | -1001820437319 |
|---|---|
| Type | Channel |
| Username | @ta5rif_mj |
| Created | Between 1 October 2022 and 30 September 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 18 September 2026 |
| Measurements held | 12 |
| Confirmed unchanged | 2 times, most recently 18 September 2026 |
| On Telegram | t.me/ta5rif_mj |
Technology — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-FP8, prompt version 1) read this channel’s own recent posts on 13 September 2026 and assigned it the closest of 31 fixed categories, at 47% 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 |
|---|---|---|
| 13 Sept 2026, 21:18 | 4,879 | -4 |
| 9 Sept 2026, 19:37 | 4,883 | +3 |
| 4 Sept 2026, 13:39 | 4,880 | -5 |
| 1 Sept 2026, 08:28 | 4,885 | +1 |
| 29 Aug 2026, 05:53 | 4,884 | +4 |
| 26 Aug 2026, 06:28 | 4,880 | -2 |
| 23 Aug 2026, 14:46 | 4,882 | -4 |
| 20 Aug 2026, 08:28 | 4,886 | -2 |
| 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 |
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 pages of Telegram’s post history, 20 posts per page.
Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 22 posts for this entry, the most recent from 11 August 2026. An engagement rate over an empty window would be a number about nothing.
83 reactions across 17 posts, in 6 distinct kinds. The most used accounts for 74.7% of them.
| 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 83 reactions 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 وبصيت علي كل مشروع وعرفت ف…
❤5
شباب كتير اللهم بارك بيبعتلي عشان Consultation sessions وللاسف اشتراك لينكدان premium انتهي فكل ال requests اللي بتيجي بشوفها متأخر جدا فاي حد من الشباب محتاج Consultant session يتواصل مباشرة DM علي لينكدان مباشرة * ----------------------- * بالنسبه لل Connection Requests انا فعليا مش عارف اعمل accept وغالبا بسبب المشكله الخاصه بالوصول الي 30 الف Connection او عشان الاشتراك انتهي فللاسف مش عارف اعمل accept فرجاء اع…
❤4
في حد من الشباب جرب ال arch wiki علي المشروع بتاعه وما شاء الله منبهر بيها جدا 👏👏👏👏👏
❤3🍓1
بعد ما وصلنا بفضل الله لـ 117 🌟 علي الـ repo فده شجعني ان اكمل في مشروع الـ arch-wiki من فترة كنت اشتغلت على arch-wiki وكانت الفكرة إننا نعمل Architecture Documentation للمشاريع بشكل Automatic وفي نفس الوقت تكون مفيدة للـ Developers والـ AI Tools النهارده عملنا شوية Updates جديدة وحاجات مهمة اتضافت بناء علي الفيدباك اللي وصلنا وان شاءالله تبقي مفيدة 1. الـ Prerequisites & Setup Pipeline. دلوقتي الـ arch-wiki تقدر …
❤2
بالنسبه لموضوع الخطوط والباكبورت اللي اتفتح والكوارث اللي في الشركات والمسخرة اللي بتحصل ويعني ايه اشترى خطوط بصور بطايق بتاعة ناس تانيه طبعا الناس اللي سرقت صور البطايق والناس اللي اشترتهم دول المفروض يتحبسوا وش والشركات الاتصالات تتدفع تعويضات وغرامات غصب عن اللي خلفوهم واللي جابهوم عشان شركات وسخه من الاخر وعارفين الفساد وعايشين فيه طب عشان نحل الموضوع ده نعمل ايه اولا اي واحد بيشترى اي خط جديد ومعندوش خط مسبق لو…
👍2
في المنتورشيب عندنا في الشهر التاني بيكون فيه آخر Task في جزء الـ Database وهو إننا نعمل Database Optimization للـ Queries اللي اشتغلنا عليها طول الشهر بس قبل ما نبدأ الـ Optimization بيكون عندنا خطوة مهمة جدا إننا نملي الـ Database بحجم Data كبير الهدف مش مجرد إنك تعرف تعمل Insert لملايين الـ Records الهدف الحقيقي إنك تكسر رهبة التعامل مع الداتا الكبيرة في المنتورشيب حجم الداتا بيوصل لـ 50 مليون Record عشان لما ت…
❤2
بصراحة السوق بقى أصعب من أي وقت فات للأسف في شركات كتير خصوصا في الشرق الأوسط بقت شايفة إن طالما فيه AI Tools يبقى مفيش داعي تدفع مرتبات كبيرة، ونجيب أي حد يمشي الدنيا لكن الحقيقة إن الموضوع مش بالبساطة دي في أوروبا لسه في شركات كتير بتدور على الشخص اللي عنده خبرة حقيقية وفي نفس الوقت بيعرف يستخدم الـ AI صح ليه؟ لأن الخبرة هي اللي بتفرق الشخص اللي عنده خبرة هو اللي يعرف يعمل Architecture صح ويسأل الأسئلة الصح ويطلع…
👏6❤5👍2
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 …
❤5👍5
ازيكم يا شباب اخباركم ايه حد جرب Arch Wiki ال skill اللي بتعمل documentation للمشاريع لو حد جربها يقولي feedback
من يومين نزلت ال Arch Wiki Skill وكان الهدف الأساسي منها إنها تساعد أي حد يدخل Project جديد أو حتى Project قديم مفيهوش Documentation محترمة إنه يفهم الدنيا أسرع بدل ما يقعد أيام بيدور ويسأل من أكتر الحاجات اللي بتضيع وقت أي Software Engineer هي إنه يفهم ال Architecture بتاعة المشروع خصوصا إن في مشاريع كتير جدا مفيهاش أي Documentation تشرح هي ماشية إزاي ومن هنا جات فكرة Feature من أهم الـ Features الموجودة في ال Ski…
❤6
عشان كده بنقول ذاكر
❤3👍2
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.
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.
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.
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.
This channel appears in 10 seed channels' Telegram-generated recommendation lists in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.
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 13 September 2026 — this entry's latest reading, not the date you are reading this.
“تخاريف مبرمج” (@ta5rif_mj), 4,879 subscribers as measured 13 September 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.