Channel
@techstuff100
On this record: Growth · Engagement · Reactions · Posts · Citations · Cite this entry
1,038subscribers
+20 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
| Telegram ID | -1002439139166 |
|---|---|
| Type | Channel |
| Username | @techstuff100 |
| Created | Between 1 September 2024 and 31 March 2025— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 14 August 2026 |
| Measurements held | 4 |
| Confirmed unchanged | 1 time, most recently 14 August 2026 |
| On Telegram | t.me/techstuff100 |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 14 Aug 2026, 09:47 | 1,038 | +3 |
| 11 Aug 2026, 08:05 | 1,035 | +13 |
| 7 Aug 2026, 23:28 | 1,022 | +4 |
| 7 Aug 2026, 04:01 | 1,018 | first reading |
9 posts held, back to 17 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 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.
| Window | Rolling 30 days · latest post in window 6 August 2026 |
|---|---|
| Posts held | 9 (17 July 2026 – 6 August 2026) |
| Views total | 5,439 |
| Reactions total | 86 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 7 Aug 2026, 04: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.
119 reactions across 9 posts, in 4 distinct kinds. The most used accounts for 75.6% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 90 | 75.6% | |
| 👍 | 22 | 18.5% | |
| 👏 | 4 | 3.36% | |
| 🔥 | 3 | 2.52% |
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 9 of the 9 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 119reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 9 most recent posts we hold, published 17 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.
مقالاتی که اخیرا خوندم (قسمت اول) 🔺 XSS in hidden input fields [لینک] 🔺 How I Actually Prepare for Coding Interviews [لینک] 🔺Design Google Docs Like a Senior Engineer [لینک] 🔺 مسیر ساخت WAF در ترب [لینک] 🔺 رایتآپ تصاحب حساب کاربری از زیرِ بغلِ مار [لینک] 🔺 I Used Git Wrong for Years [لینک] 🔺 The Team Matching Round: The Interview Where You Should Be Doing the Interviewing [لینک] #recent_reads @techstuff100
👍8
یه نکته کوچیک درباره XSS وجود داره که خیلیا موقع تست امنیت یادشون میره. بعضی وقتا context ای که ورودی کاربر توش قرار میگیره، یه اتریبیوت از تگ HTML هست. بخصوص اگه اون اتریبیوت خودش قابلیت اجرای کد داشته باشه. مثلا تگ a رو در نظر بگیرید. اگه بتونیم مقدار href رو کنترل کنیم، میتونیم به جای یه URL معمولی از پروتکل javascript استفاده کنیم. وقتی کاربر روی این لینک کلیک کنه، به جای رفتن به یه صفحه، کد جاوااسکریپت داخل h…
❤6👏2
طراحی سیستم: Multipart Upload این پست درباره Multipart Upload هست که برای آپلود فایلهای بزرگ استفاده میشه و باعث میشه هم در برابر قطعی شبکه مقاومتر باشیم، هم بتونیم با آپلود همزمان بخشهای مختلف، زمان آپلود رو کمتر کنیم. #system_design_interview_volume_2 @techstuff100
❤9👍1
همه چیز درباره پکیج Module Federation توی این ویدیو، بهصورت کامل با پکیج Module Federation آشنا میشیم و یاد میگیریم چطور یه پروژه کامل باهاش بسازیم. این ویدیو کمکتون میکنه با معماری میکروفرانتاند هم آشنا بشین و ببینین چطور اپلیکیشنهای مختلف میتونن بهصورت مستقل توسعه داده بشن و در نهایت توی یه اپلیکیشن روت (host) کنار هم لود و نمایش داده بشن. ویدئوی یوتوب: https://www.youtube.com/watch?v=bhUZVxr4mP0&list=PL1b…
❤7👍4👏2
پذیرش بازخورد در برنامهنویسی معمولا تنها کار نمیکنیم و بخش زیادی از رشد ما از تعامل با بقیه اعضای تیم اتفاق میفته. یکی از مهمترین جاهایی که این موضوع رو میبینیم Code Review هست. وقتی کسی کدی که نوشتیم رو بررسی میکنه، هدفش پیدا کردن ایراد، بهتر کردن کیفیت کد و انتقال تجربه است؛ نه اینکه توانایی ما رو زیر سوال ببره. البته دریافت بازخورد همیشه راحت نیست. وقتی چند نفر کدی که نوشتیم رو بررسی میکنن، ممکنه حس کنیم د…
❤20👍4
نتفلیکس چطور ۲۶۰ میلیلون استریم همزمان رو بدون Buffering مدیریت میکنه؟ نتفلیکس فقط به افزایش تعداد سرورها متکی نیست؛ بخش بزرگی از موفقیتش به معماری توزیع محتوا برمیگرده. ویدیوها قبل از اینکه کاربری درخواستشون رو بده، روی هزاران سرور CDN اختصاصی به اسم Open Connect که داخل شبکه ISPها قرار دارن توزیع میشن تا درخواستها از نزدیکترین نقطه پاسخ داده بشن. از طرف دیگه هر کاربر با استفاده از Adaptive Bitrate (ABR) کیفیت …
❤13
حمله SSL Stripping و روشهای دفاع این پست درباره SSL Stripping و مکانیزم HSTS هست. HSTS یک Response Header ساده است که باعث میشه مرورگر فقط از HTTPS برای یک دامنه استفاده کنه. همچنین میبینیم چرا HSTS به تنهایی کافی نبود و مرورگرها برای حل مشکل اولین بازدید، HSTS Preload List رو معرفی کردن. #cyber_security @techstuff100
❤5👍3🔥2
کتابی که اخیرا شروعش کردم. #Skills_of_a_Successful_Software_Engineer @techstuff100
❤26
مفهوم Downsampling در دادههای متریک توی این پست درباره downsampling در دادههای متریک و استفاده ازش در طراحی سیستمهای مانیتورینگ صحبت کردم. این موضوع کمک میکنه حجم دادههای time-series کنترل بشه و هزینه ذخیرهسازی و کوئریها کمتر بشه. پ.ن: منبع این پست کتاب System Design Interview – An Insider's Guide: Volume 2 هست. #system_design_interview_volume_2 @techstuff100
❤4👍2🔥1
Showing the 9 most recent of 9 posts we hold for @techstuff100. 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 — 390,166 of 1,481,243entries 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.
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 2 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.
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 14 August 2026 — this entry's latest reading, not the date you are reading this.
“Tech Stuff” (@techstuff100), 1,038 subscribers as measured 14 August 2026. Telegram Register, tgregister.com/channel/techstuff100.
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.