3 measurements spanning 8 days, net -3. 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 309–312 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)
Subscribers
Change
15 Aug 2026, 11:06
309
-3
7 Aug 2026, 20:58
312
no change
7 Aug 2026, 03:16
312
first reading
Engagement
20 posts held, back to 28 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
70.8%
avg views ÷ 309 subscribers
Avg views / post
219
20 posts measured
Reaction rate
1.86%
reactions ÷ views · ER floor
Posts in window
20
of 20 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 19 of 20 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 6 August 2026
Posts held
20 (28 July 2026 – 6 August 2026)
Views total
4,374
Reactions total
80
Forwards / comments
not exposed by the public surface — not measured, not estimated
Readings taken
7 Aug 2026, 03:16 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
80 reactions across 19 posts, in 6 distinct kinds. The most used accounts for 82.5% of them.
Every reaction kind recorded on the sample, most used first
Reaction
Count
Share
Share, drawn
❤
66
82.5%
🔥
6
7.50%
👍
4
5.00%
❤🔥
2
2.50%
🍌
1
1.25%
💩
1
1.25%
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 20 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 80reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 20 most recent posts we hold, published 28 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.
دوستان ما برای این کار به آمادهسازی نیاز داریم.
۳ تا فاز تعریف میکنیم که به زودی توی سایت هم اطلاعاتش قرار میگیره و همینجا اطلاعرسانی میکنیم براش 📢
هدفمون تبدیل شدن به بهترین و بزرگترین مرجع برای برنامهنویسها، مهندسهای نرمافزار، مهندسهای سختافزار و هر حوزه دیگهای که با کد زدن سرو کار داره، هست.
به زودی بهروزرسانی های جدید در رابطه با این اپدیت بزرگ رو همینجا اعلام میکنیم. منتظرمون باشید.
مثل همیشه …
نوشته جدید: اصول SOLID 🛠️
اصول SOLID احتمالاً یکی از پرتکرارترین موضوعاتی هست که تو مصاحبههای برنامهنویسی ازش سؤال میشه 🤔، ولی همین تکرار زیاد باعث شده خیلی وقتها به یه سری تعریف حفظی تبدیل بشه که کسی واقعاً نمیدونه کِی و چرا باید ازشون استفاده کنه. 🧠
این پنج اصل، راهنمای طراحی کلاسها و ماژولها هستن که هدفشون کد قابل نگهداریتر و کمتر شکننده در برابر تغییره 🛡️؛ نه یه سری قانون مقدس که باید همیشه و همهجا کور…
نکست جی اس ورژن ۱۶.۳ منتشر شد. 🚀
- مصرف کمتر RAM در حالت توسعه 💾
- بیلد سریعتر 🏗️
- تایپ چک سریعتر با تایپ اسکریپت ۷ ⚡
- SSR سریعتر 🚀
- درخواستهای کمتر برای Prefetch 📉
- کش بهتر برای فایلهای استاتیک ⚡
آپدیت رو بررسی کردیم. اگر نکست کار میکنید حتما بخونید. 📖
امیدواریم مفید باشه 😊
https://codoloper.ir/blog/nextjs-163-mntshr-shd-tjrbh-twsah-bhtr-shdh
#خبر
⚙️ یه سؤال ساده: وقتی یه سرور کش رو اضافه یا حذف میکنی، چرا یهو کل کش خالی میشه و همهی درخواستها میریزن رو دیتابیس؟ 🤔
جواب این سؤال به یه فرمول ساده برمیگرده: hash(key) % N. تا وقتی N ثابته همهچیز خوبه ✅، ولی همین که یه سرور کم یا زیاد بشه، تقریباً همهی کلیدها جابهجا میشن 🔄. تو مقالهی جدید کدلپر، از صفر توضیح دادیم consistent hashing چطور این مشکل رو حل میکنه 🛠️ و چرا فقط K/N کلید (بهجای همهشون) جابهج…
خبر هست مثل اینکه دیپ سیک داره یک هارنس درست میکنه یچیزی مثل(codex یا claude code).
اگر رایگان باشه یا حداقل بیشتر از بقیه رایگان بزاره استفاده کنیم، بعد از اینکه مدل فلش جدیدش انقدر خوب بوده توی همه کار ها، احتمالا انتخاب همه بشه.
البته اگر با چین مشکلی نداشته باشید
نوشته جدید: قضیه CAP در دیتابیس
یکی از مهم ترین مباحثی که باید راجع به دیتابیس های توزیع شده بدونید قضیه CAP هست
میگن که یک دیتابیس هیچوقت نمیتونه این سه تا رو باهم تضمین کنه Consistancy, Availability و Partition tolerance
این مطلب مهمی هست در کل
امیدواریم مفید باشه
https://codoloper.ir/blog/qdhyhy-cap-chra-hych-dytabys-twzyashdhay-nmytwnh-hmhchyz-rw-ba-hm-dashth-bashh
#آموزش
خبر انتشار عمومی بتا دیپ سیک فلش ورژن ۴ رو داخل سایت بررسی کردیم. 📢
این مدل از مدل pro خودش فراتر رفته و مثل ایکه خیلی خوب بوده
اپ Cline رایگان میزاره استفاده کنید ازش فکر میکنم با ۵۰ میلیون توکن 💬✨
قیمتشم خیلی مناسبه بررسی کنید بد نیست
امیدواریم مفید باشه 🤞
https://codoloper.ir/blog/deepseek-v4-flash-mdly-kh-adaa-myknh-az-nskhhy-pro-khwdsh-hm-jlw-zdh 🔗
#خبر
نوشته جدید: Message Queues 📬
در مقالهی جدید کدلپر، از صفر توضیح دادیم که queue دقیقاً چیکار میکنه 🤔، چرا فقط یه background thread ساده کافی نیست، و چطور مفاهیمی مثل durability و retry باعث میشن سیستم در برابر کرش و قطعی مقاومتر بشه 🛡.
مقایسهی RabbitMQ و Kafka هم توش هست — با یه جمعبندی ساده از اینکه کِی کدومشون منطقیتره ⚖️.
نکتهای هم دربارهی idempotency و dead letter queue گفتیم که تو خیلی از tutorial ها …
نوشته جدید: Rate Limiting 🔒
فرض کن یک endpoint ساده داری که لیست محصولات رو برمیگردونه 📦. یک روز متوجه میشی سرورت زیر فشار عجیبی رفته، درحالیکه تعداد کاربر واقعی زیاد نشده 📉. وقتی لاگها رو نگاه میکنی، میبینی یک IP تنها، چند هزار درخواست در ثانیه فرستاده — یا یک اسکریپت خرابه 🤖، یا یک نفر داره عمداً دادههات رو میخراشه (scrape میکنه) 🕸️، یا حتی داره تلاش میکنه با حجم درخواست سرویس رو از کار بندازه 🛑. Rate limiting …
نوشته جدید: cuid و cuid2 - چرا نسخهی دوم عملاً از صفر بازنویسی شد 🔄
وقتی میخوای برای رکوردهای دیتابیست یک شناسهی یکتا بسازی، احتمالاً اول به auto increment فکر میکنی، بعد به UUID، و اگه دنبال چیزی سبکتر و url-friendly تر باشی، به cuid میرسی. ولی نکتهای که خیلی وقتها گم میشه اینه که cuid و cuid2 دو چیز کاملاً متفاوتن — نه یک آپدیت جزئی، بلکه یک بازطراحی کامل با فرضهای امنیتی متفاوت 🔐🔧
یک نکته بگم که اگر از…
نوشته جدید: پنجشنبه، OpenAI اعلام کرد قیمت دو مدل از خانوادهی GPT-5.6 رو بهطور قابلتوجهی کاهش داده — این اتفاق فقط حدود سه هفته بعد از عرضهی همین مدلها افتاده، که خودش نشونهی خوبیه از اینکه فشار رقابتی روی OpenAI چقدر واقعیه. 📉🤖
شخصا از مدل Gpt 5.4 mini استفاده میکردم قبل این چون تقریبا همه چیز اوکی بود. ولی خب الان اگر یه روز اکانتمو شارژ کنم، لونا قراره باشه 💸🔋
امیدواریم مفید باشه ✨
https://codoloper.ir/b…
❤4
Showing the 12 most recent of 20 posts we hold for @codoloper. 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 — 1,378,112 of 1,481,217entries 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.
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 15 August 2026 — this
entry's latest reading, not the date you are reading this.
“Codoloper” (@codoloper), 309 subscribers as measured 15 August 2026. Telegram Register, tgregister.com/channel/codoloper.
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.