رسالت ما – توانمندسازی توسعهدهندگان و علاقهمندان به فناوری با ارائهی نوشتهها، آموزشها، اخبار و تجربههای جذاب و بهروز!
ارتباط و تبلیغات :
@Afsh6n
Created
Between 1 November 2023 and 31 May 2024— estimated from Telegram’s id allocation, not measured. How this range is calculated.
7 measurements spanning 15 days, net -6. 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 9,270–9,294 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)
Subscribers
Change
22 Aug 2026, 11:25
9,273
-18
19 Aug 2026, 12:08
9,291
+13
16 Aug 2026, 20:53
9,278
-6
13 Aug 2026, 12:09
9,284
+11
10 Aug 2026, 11:13
9,273
-5
7 Aug 2026, 21:44
9,278
-1
7 Aug 2026, 03:17
9,279
first reading
Engagement
50 posts held, back to 31 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 27 pagesof Telegram’s post history, 20 posts per page.
ERR · 30 days
14.4%
avg views ÷ 9,273 subscribers
Avg views / post
1,330
50 posts measured
Reaction rate
2.20%
reactions ÷ views · ER floor
Posts in window
50
of 50 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 48 of 50 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 21 August 2026
Posts held
50 (31 July 2026 – 21 August 2026)
Views total
66,622
Reactions total
1,448
Forwards / comments
not exposed by the public surface — not measured, not estimated
Readings taken
22 Aug 2026, 17:55 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
Photos
348
Videos
189
Links
277
Lifetime counters from Telegram’s own channel header, read 22 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.
Video runtime
1m 13s
Average length
18s
Measured directly from 4 videos with a duration reading, out of the posts we hold for this channel — not this channel’s whole posting history, only the sample this register has actually read. An exact reading to the second, taken from the post itself rather than from Telegram’s own rounded chrome, so it carries no ≈ mark.
Reaction mix
1,448 reactions across 48 posts, in 24 distinct kinds. The most used accounts for 21.4% of them.
Every reaction kind recorded on the sample, most used first
Reaction
Count
Share
Share, drawn
❤
310
21.4%
🤣
291
20.1%
😁
238
16.4%
👍
223
15.4%
💔
143
9.88%
👏
63
4.35%
💘
42
2.90%
🔥
41
2.83%
🤬
38
2.62%
💅
13
0.898%
🤔
9
0.622%
😢
6
0.414%
🤓
6
0.414%
🍓
4
0.276%
🕊
4
0.276%
🙏
3
0.207%
🤝
3
0.207%
👻
2
0.138%
💯
2
0.138%
🤯
2
0.138%
4 further kinds
5
0.345%
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 48 of the 50 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 1,448reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 50 most recent posts we hold, published 31 July 2026 to 21 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.
تلگرام دسکتاپ در حال آمادهسازی یک نوع پروکسی جدید به نام WEB Proxy است.
این پروکسی از WebView استفاده میکند تا ترافیک معمولی MTProxy را از طریق ارتباطات HTTPS/WebSocket منتقل کند.
به زبان ساده، تلگرام چند اتصال را داخل یک ارتباط WebView قرار میدهد و به سرور ارسال میکند. در سمت سرور هم یک Relay این اتصالها را از هم جدا کرده و به MTProxy معمولی منتقل میکند.
این Relay به محتوای ترافیک MTProxy دسترسی ندارد و مقصد…
اگه به دنیای تکنولوژی و برنامهنویسی علاقه دارید، این کانال رو از دست ندید!
داخل کانال کدهالیک هر روز میتونید خبرها، اتفاقات و موضوعات داغ دنیای تک و برنامهنویسی رو دنبال کنید.
@codehalics
منتظرتونیم 🤍
رهایی از سندروم «هنوز آماده نیستم» قبل از شروع پروژه
خیلی وقتها مشکل ما کمبود مهارت نیست؛ منتظر موندن برای لحظهایه که احساس کنیم «کاملا آمادهایم».
اما واقعیت اینه که آمادگی معمولا قبل از شروع بهوجود نمیاد؛ حین انجام پروژه ساخته میشه.
اگر صبر کنی همهچیز رو بلد باشی، تجربهای رو عقب میندازی که فقط با انجام دادن بهدست میاد.
پروژه قرار نیست ثابت کنه چقدر بلدی؛ قراره چیزهایی رو که بلد نیستی بهت یاد بده.
شروع…
🔥هر چیزی که برای رشد کانال، گروه یا پیجت نیاز داری، اینجاست!
⭐ پریمیوم تلگرام، استارز و گیفت⭐
📱 خدمات تلگرام (ممبر، ویو، ریاکشن و...)
📱 خدمات اینستاگرام (فالوور، لایک، ویو)
📞 شماره مجازی بیش از ۱۰۰ کشور
✅انجام سفارشات آنی میباشد‼️
👆برای سفارش وارد ربات بشید:
⏺ @yoozseenfabot
سلام به همگی، من روی یک موتور دانلود اوپنسورس به زبان راست به نام HYDRA کار کردم که شامل نسخه CLI سازگار با curl/wget و یک اپلیکیشن دسکتاپ کراسپلتفرم است. نسخه GUI این ابزار با کتابخانه iced پیادهسازی شده و سعی کردم ظاهر و حس کاربری آن را شبیه به IDM درآورم تا استفاده از آن در سیستمعاملهای مختلف حس آشنا و راحتی داشته باشد. هایدرا برخلاف ابزارهایی مثل IDM یا aria2 که هنگام لگ کانکشن منتظر تایماوت میمانند، با سی…
در نسخه بتا 12.10.0 از تلگرام برای اندروید، رباتها یک دکمه جدید برای متوقف کردن ارسال پیام در یک چت دریافت کردهاند.
پیامی که در حال ارسال است، باید شامل پارامتر can_stop باشد، که به کاربر اجازه میدهد ارسال آن را متوقف کرده و به کار دیگری بپردازد.
@DevYara
مشکل چیزی که بهش میگن «همکار هوش مصنوعی» (مثل Grok، Claude، Devin و بقیه) اینه که برای بهتر انجام دادن کارم، نیازی ندارم دوباره با یه نفر دیگه حرف بزنم! فرقی هم نمیکنه آدم باشه یا هوش مصنوعی.
من دقیقا برعکسش رو میخوام.
میخوام کارها رو خودکار کنم، نه اینکه مکالمات بیشتری داشته باشم. اینطوری میتونم تمرکزم رو حفظ کنم و کارها بدون اینکه مدام بهشون جهت بدم، خودشون انجام بشن.
هدف ابزارهای هوش مصنوعی باید اتوماسیون باشه، …
- ما تلاش میکنیم که همزمان ده کار را انجام دهیم، اما در نهایت، هیچکدام را به طور کامل به سرانجام نمیرسانیم.
- توجه ما به کجا معطوف باشد، انرژی نیز به همان سمت جریان پیدا میکند.
وقتی توجه ما تکهتکه میشود - یک دقیقه اینستاگرام، یک دقیقه اخبار، یک دقیقه کار، یک دقیقه خانواده - انرژی ما نیز به طور ناکارآمد پخش میشود.
و در پایان روز، با احساسی که "امروز هیچ کاری نکردم" میخوابیم.
@DevYara
خود همین مدل محتوا هم میتونه یه بنر تبلیغاتی خیلی خوب باشه؛ چون تبلیغ رو مستقیم و خشک جلوی مخاطب نمیذاره.
اول یه مشکل یا موضوع واقعی مطرح میشه، بعد یه راهکار پیشنهاد میشه و در نهایت تبلیغ به عنوان همون راهکار وارد متن میشه. اینطوری مخاطب قبل از دیدن تبلیغ، دلیل و زمینه استفاده ازش رو هم دریافت کرده.
تبلیغات:
t.me/DevsAds/83
@DevYara
❤5😁1
Showing the 12 most recent of 50 posts we hold for @DevYara. 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,127,962 of 1,584,142entries 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 3 registered channels — 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.
Appears in Telegram’s recommendations for other channels
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.
کتاب_جزوه و اخبار دانشگاهی @jozve_iq · 97,942 Telegram ranks this channel #30 of 85 here — alongside 84 others — read 16 August 2026
برنامه نویسی | پایتون @Pythoni_Developers · 75,700 Telegram ranks this channel #57 of 82 here — alongside 81 others — read 19 August 2026
مهندسی کامپیوتر @maghalecomputer · 60,160 Telegram ranks this channel #60 of 85 here — alongside 84 others — read 22 August 2026
آموزش برنامه نویسی و هوشمصنوعی | Max academy @max_academy · 70,893 Telegram ranks this channel #65 of 83 here — alongside 82 others — read 20 August 2026
This channel appears in 4 seed channels' Telegram-generated recommendation lists in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.
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 22 August 2026 — this
entry's latest reading, not the date you are reading this.
“توسعه دهندگان” (@DevYara), 9,273 subscribers as measured 22 August 2026. Telegram Register, tgregister.com/channel/DevYara.
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.