3 measurements spanning 6 days, net +2. 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 1,034–1,036 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)
Subscribers
Change
7 Sept 2026, 07:18
1,036
+1
2 Sept 2026, 03:42
1,035
+1
1 Sept 2026, 07:16
1,034
first reading
Engagement
20 posts held, back to 30 June 2025 — 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 page 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 20 posts for this entry, the most recent from 2 August 2026. An engagement rate over an empty window would be a number about nothing.
Reaction mix
262 reactions across 18 posts, in 2 distinct kinds. The most used accounts for 99.2% of them.
Every reaction kind recorded on the sample, most used first
Reaction
Count
Share
Share, drawn
👍
260
99.2%
👎
2
0.763%
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 18 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 262 reactions 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 30 June 2025 to 2 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.
Telegram Stars
Stars received
1
across the posts below
Posts paid on
1
of 20 we hold a reading for · 5%
Most on one post
1
single highest reading
A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @NodeMaster. Telegram publishes the count on the public post preview alongside ordinary reactions, and this register reads it there. It is the only figure on this site that measures money moving rather than attention.
Stars are not reactions, and the two are never added. They are rendered in the same strip on Telegram and counted in the same shape, but one is a tap and the other is a purchase. The reaction totals and the engagement rate elsewhere on this page exclude every figure in this section, and no rate here is computed against a reaction count.
This is not revenue, and we publish no currency figure. What a Star costs a reader and what it pays a channel are different numbers, Telegram takes a share we cannot observe, and the terms have changed. Converting a Star count into money would be an estimate dressed as a measurement, so the count is where we stop.
Counted over the 20 most recent posts we hold for this entry, published 30 June 2025 to 2 August 2026. Star counts above 1,000 reach us in Telegram’s short form and carry the same three-significant-figure rounding as everything else on this page.
درود به همگی.
براتون آرزو شادی دارم.
همینطور که میدونید مدت زیادی هست این چنل تبدیل شده به چنل ارواح و فعالیت خاصی ندارم.
یکی از دلایل وضعیت AI و تغییراتی که به صورت نهادین با این اکوسیستم انجام داده هست و سردرگمی که خیلی از ما ممکنه داشته باشیم.
پیشنهاد میکنم این پست رو بخونید و نظرتون بگین.
این حاصل مشاهده و فکر کردن و حرف زدن با تعداد زیادی از دوستان برنامه نویسی هست که همه از قبل از دوران AI کار میکردن و حرفه ای…
این ویدیو هم که درمورد Netflix و چالش هاش بود رو من دیدم و خیلی جذاب بود. هرچند نیاز دارم دوباره ببینمش ولی پیشنهاد میکنم ببینیدش.
https://www.youtube.com/watch?v=XpunFFS-n8I&list=PLX8CzqL3ArzVV1xRJkRbcM2tOgVwytJAi&index=46&t=1720s&pp=iAQB
درود به همگی دوستان. امیدوارم حالتون خوب باشه. باتوجه به این که خیلی وقت هست چیزی ننوشتم واقعا نمیدونم باید از کجا شروع کرد.
حدود یک سال پیش با یکی از دوستانم داشتیم بحث های تکنیکال میکردیم و اشتراک تجربه که بهم کنفرانس JavaOne رو معرفی کرد. چندین ویدیو از مجموعه ای که از سال 2025 اومد رو دیدم و واقعا جذاب بود.
یه نکته ای که درمورد این کنفرانس نظرم رو جلب کرد این هست که همیشه از تمامی hype هایی که اتفاق میافته فاصله…
درود دوستان امیدوارم حالتون خوب باشه.
به عنوان Backend developer از موضوعاتی که حتما باید حداقل آشنایی کوچکی داشته باشید کار کردن با container ها هست. به طوری که حداقل بتونید پروژه خودتون رو به راحتی containerized کنید. در این مورد زیاد course دیدم معمولا خیلی از کورس ها اضافه گویی میکنند و تایم زیادی هم لازم دارن.
این کورس از Brian Holt از محدود course هایی هست که این اضافه گویی ها رو نداره و البته موضوع خیلی جالب و…
ما Developer ها به Magic عادت داریم. بیشتر وقت ها کدی که مینویسیم فقط میخوایم کار کنه. اما چطور کار کردن اون کد خیلی اهمیتی نداره تا وقتی که کدمون کار میکنه. حالا چه به صورت جادویی کار کنه چه با جزئیات کامل بدونیم پشت پرده چخبر هست. گاها بعضی از این جادو ها اینقدر پیچیده و ترسناک به نظر میان که اصلا بهشون نزدیک نمیشیم. یکی از این Magic ها Promise ها در #JavaScript هست. اکثرا فکر میکنیم یک چیزی هست که داخل گوشت و وجود…
این اولین بلاگ پست یکی از نزدیک ترین دوستان من هست که داخل AMD منتشر شده و درمورد استفاده از #k8s برای نیاز های AI برای کارت گرافیک ها AMD هست.
دوست داشتید نگاهی بندازید مخصوصا اگر #K8S آشنایی دارید.
https://rocm.blogs.amd.com/software-tools-optimization/gpu-operator-partitioning/README.html
یکی از معجزه های #JavaScript ویژگی Closure هست. البته هر زبانی که این ویژگی رو داشته باشه خیلی دست بازی برای پیاده سازی پترن هایی داره که بدون Closure ها شاید ممکن نباشه. خیلی وقت پیش درمورد Async Cps Style صحبت کردیم میتونید برید نگاهی بندازید. نکته ای که میخوایم امروز درموردش صحبت کنیم این که چه جادویی در این تکه کد ساده که به صورت روزانه مینویسیم و کار میکنیم وجود داره ولی خیلی ساده ازش رد میشیم چون کار میکنه! ولی…
درود رفقا امیدوارم حالتون خوب باشه.
بلاخره تلسم رو شکوندم بعد از چند ماه این ویدیو رو گرفتم.
در این ویدیو باهم یاد میگیرم که چطور از AsyncLocalStorage استفاده کنیم در #NodeJS البته قبل از هرچیزی میریم نگاهی به react context در #React میکنیم که از بچه های #FrontEnd یاد بگیرم چطور همچین مسائلی رو که AsyncLocalStorage به ما کمک میکنه حل کنیم رو با react context حل میکنن.
https://youtu.be/B_s401HuZAU
👍18
Signed Iman Hosseini Pour
Showing the 12 most recent of 20 posts we hold for @NodeMaster. 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.
Stars beside a post are paid reactions — Telegram Stars, bought with money and spent on that post. They are a different unit from reactions and are never added to them, here or anywhere else on this page.
Polls
The poll we hold for this entry, as Telegram rendered it when we read the post. A poll’s figures keep moving after that, so each one is dated.
آیا هنوز مطالب فنی ( ویدیو، داکیومنت، مقاله ) برای آموزش دنبال میکنید؟
همیشه مطالب فنی رو دنبال میکنم.47%
گاهی دنبال میکنم.22%
با AI سعی میکنم یاد بگیرم.32%
Shares as published, totalling 101%. No per-option vote count is published by Telegram, so none is shown.
Percentages only — there are no per-option vote counts here, because Telegram publishes none. The public post preview gives each option’s share and a single voter total, and nothing else. Multiplying one by the other would produce a per-option tally that looks measured and is not: the shares are rounded to whole numbers before we ever see them. We print what was published and leave the column that does not exist empty.
The shares need not add up to 100. Rounding alone puts many polls at 99 or 101. A poll that allows more than one answer per voter runs well past 100 by design, and several here do. The bars are drawn against a fixed 100% track at each option’s own percentage rather than normalised to the total, so a poll that exceeds it shows that it does instead of being quietly rescaled.
Read from the 20 most recent posts we hold, published 30 June 2025 to 2 August 2026. Telegram labels each poll by kind — an anonymous poll, a quiz, a closed set of final results — and that label is reproduced rather than paraphrased.
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.
آموزههای وادی فاثری @vadi_faseri · 34,582 Telegram ranks this channel #38 of 63 here — alongside 62 others — read 6 September 2026
DevTwitter | توییت برنامه نویسی @devtwitter · 31,912 Telegram ranks this channel #48 of 90 here — alongside 89 others — read 5 September 2026
Crypto Insights Hub @majale_digital · 37,394 Telegram ranks this channel #81 of 85 here — alongside 84 others — read 1 September 2026
This channel appears in 3 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 7 September 2026 — this
entry's latest reading, not the date you are reading this.
“Node Master” (@NodeMaster), 1,036 subscribers as measured 7 September 2026. Telegram Register, tgregister.com/channel/NodeMaster.
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.