2 measurements taken within a single day. 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 840–842 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)
Subscribers
Change
7 Aug 2026, 18:50
841
no change
6 Aug 2026, 22:01
841
first reading
Engagement
19 posts held, back to 25 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 1 pageof Telegram’s post history, 20 posts per page.
ERR · 30 days
40.1%
avg views ÷ 841 subscribers
Avg views / post
337
19 posts measured
Reaction rate
3.28%
reactions ÷ views · ER floor
Posts in window
19
of 19 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 6 August 2026
Posts held
19 (25 July 2026 – 6 August 2026)
Views total
6,410
Reactions total
210
Forwards / comments
not exposed by the public surface — not measured, not estimated
Readings taken
6 Aug 2026, 22:01 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
210 reactions across 19 posts, in 8 distinct kinds. The most used accounts for 41.4% of them.
Every reaction kind recorded on the sample, most used first
Reaction
Count
Share
Share, drawn
👍
87
41.4%
❤
34
16.2%
🤣
30
14.3%
🔥
28
13.3%
😁
15
7.14%
🤬
13
6.19%
👎
2
0.952%
💔
1
0.476%
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 19 of the 19 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 210reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 19 most recent posts we hold, published 25 July 2026 to 6 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.
خِفتم کن!
وقتی با AI کد میزنید، بزرگترین سم اینه که شما فقط بگی چی میخوای و اونم یه مشت کد بپاشه جلتون و شما هم بیفکر فقط «Accept» بزنید. اینجوری بعد از نیم ساعت کلاً پرت میشید که پروژه داره به کجا میره و کنترل از دستتون در میره.
تکنیک اینه که بهش بگی: «Grill me» (خفتم کن!)
درواقع داری بهش میگی قبل از اینکه دست به کد بشی، حتی قبل از اینکه به پلن برسی، زیر و بم قضیه رو ازم بکش بیرون. سوالای سخت بپرس، حالت…
کلاین مدل های فیری رایگانی داره و من نمیدوستم!
مدل جدید دیپ سیک رو هم اد کرده و محدودیت هاش خیلی کمه!
همین الان پیشنهاد میکنم اوکی کنید برا خودتون
https://cline.bot/
CODELAB | GpCodeLab
⭕️اگر روی گوشی VPN دارید، دیگر لازم نیست برای لپتاپ هم VPN جداگانه تهیه یا تنظیم کنید.
ریپو Relay یک ابزاریه که با اسکن یک QR Code، اینترنت گوشی به همراه VPN فعال روی آن را بهسرعت روی ویندوز به اشتراک میگذارد
https://github.com/Mahdi-mortazavi/relay
ریپو Chatwoot یک پنل پشتیبانی برای سایت و اپ هاست.
پیام های کاربران از جا های مختلف مثل تلگرام، ایمیل، چت سایت و... رو یکجا جمع میکنه تا راحت بتونید جواب بدین.
مثل سیستم پشتیبانی شرکت های بزرگه، ولی اوپن سورس و قابل نصب روی سرور خودتون
https://github.com/chatwoot/chatwoot
CODELAB | GpCodeLab
چطور بهترین پرامپت را از خودِ هوش مصنوعی بگیریم؟
بیشتر افراد مستقیماً سؤالشان را میپرسند، اما کاربران حرفهای یک مرحله قبلتر میروند؛ از هوش مصنوعی میخواهند بهترین پرامپت ممکن را برایشان طراحی کند.
کافی است این دستور را به هر مدل هوش مصنوعی بدهید:
««به عنوان یک Prompt Engineer حرفهای عمل کن. قبل از نوشتن پرامپت، اگر اطلاعات کافی نیست از من سؤال بپرس. سپس بهترین پرامپت ممکن را با تعیین نقش، هدف، زمینه، محدودیت…
💻 T3 Code
همهی ایجنتهای کدنویسیت (Claude Code، Cursor، Codex و ...) رو از یه اپ واحد کنترل کن، حتی از موبایل!
دیگه لازم نیست برای هر ایجنت هوش مصنوعی که رو دستگاهت نصب کردی، یه ترمینال یا اپ جدا باز کنی؛ T3 Code یه لایهی کنترلی میسازه که به اشتراکهای موجودت (Claude Code, Codex, Cursor, Grok Build, OpenCode) وصل میشه و از موبایل، وب یا دسکتاپ مدیریتشون میکنه.
🔹 اجرای سریع بدون نصب با npx t3@latest، یا نصب اپ…
🚀 اگر برای توسعه رابط کاربری از ابزارهایی مانند Claude Code، Codex یا سایر ایجنتهای هوش مصنوعی استفاده میکنید، این پروژه گیتهاب را از دست ندهید.
⭕️ با استفاده از این مجموعه میتوانید:
💻🎨 ظاهر و کیفیت بصری رابط کاربری را بهبود دهید.
🖌️ رنگبندی و تمهای هماهنگ و استاندارد ایجاد کنید.
🔤 تایپوگرافی، فاصلهگذاری و خوانایی متون را بهینه کنید.
📐 چیدمان و ساختار صفحات را به شکل اصولیتر طراحی کنید.
♿ دسترسپذیری (Acces…
دیگر نیازی به آموزش مدلها بر روی کل مجموعه دادهها به صورت یکجا نیست!
یکپارچهسازی آموزش پویا و دادهمحور با چارچوب جدید DataFlex
چالش اصلی در آموزش مدلهای زبان بزرگ (LLM) همواره این بوده است که روشهای «انتخاب داده»، «ترکیب دامنهها» و «وزندهی مجدد» در کدهای جداگانه و ایزوله پیادهسازی میشدند. این موضوع فرآیند مقایسه و ترکیب آنها را دشوار میکرد. اکنون DataFlex برای گردآوری تمام این روشها تحت یک چارچوب واحد …
🔴 طبق گزارشات متعدد اپراتور های تلفن همراه به اینترنت بین الملل ضریب ۲.۷ دادن یعنی مردم اگه ۱ گیگ اینترنت مصرف کنن اونا ۲.۷ گیگ ازشون کم میکنن و اینطوری بسته های اینترنت با سرعت چند برابر تموم میشه تا مجبور بشید زود به زود بسته بگیرید
اینستا یه آپدیت جدید داده؛ میتونین تو قسمت «یادبود» اینستا یک نفرو مشخص کنین که بتونه بعد مرگتون در پیجتون فعالیت کنه و توی بیوی پیجتون هم میزنه صفحه یادبود و یا کلا اکانتتون حذف بشه
😁10
Signed 𝘮𝘰𝘯𝘪𝘣 𝘴𝘢𝘭𝘦𝘩𝘪
Showing the 12 most recent of 19 posts we hold for @c0delab. 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 — 678,388 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 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 7 August 2026 — this
entry's latest reading, not the date you are reading this.
“Code Lab” (@c0delab), 841 subscribers as measured 7 August 2026. Telegram Register, tgregister.com/channel/c0delab.
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.
