3 measurements spanning 6 days, net +1. 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 354–355 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)
Subscribers
Change
13 Aug 2026, 11:48
355
+1
7 Aug 2026, 02:53
354
no change
7 Aug 2026, 01:02
354
first reading
Engagement
20 posts held, back to 3 February 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
47.4%
avg views ÷ 355 subscribers
Avg views / post
168
5 posts measured
Reaction rate
4.88%
reactions ÷ views · ER floor
Posts in window
5
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.
What these figures were computed from
Window
Rolling 30 days · latest post in window 2 August 2026
Posts held
20 (3 February 2026 – 2 August 2026)
Views total
841
Reactions total
41
Forwards / comments
not exposed by the public surface — not measured, not estimated
Readings taken
7 Aug 2026, 01:02 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
234 reactions across 20 posts, in 7 distinct kinds. The most used accounts for 76.9% of them.
Every reaction kind recorded on the sample, most used first
Reaction
Count
Share
Share, drawn
🔥
180
76.9%
❤
31
13.2%
💔
10
4.27%
😐
7
2.99%
💩
2
0.855%
😁
2
0.855%
🤯
2
0.855%
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 20 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 234reactions 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 3 February 2026 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.
به احتمال زیاد اسم Context Switch به گوشتون خورده. توی سیستم عامل وقتی CPU از یه برنامه به یه برنامه دیگه اختصاص داده میشه (سویچ میکنه) میگن Context Switch اتفاق افتاده.
تو کتاب استالینگز به این عمل به جای context switch میگن Process switch! 📚
برای منم اینجوری جا افتاده بود که Cpu داره بین پراسس ها سویچ میکنه در صورتی که به طور فنی پراسس چیزی جز یه موجودیت و یه سری دیتا نیست.
بخش زنده داخل Process ها Thread ها هستن…
دِوچن (DevChan) پلتفرمیه که توسط یه تیم سه نفره متشکل از من و دو نفر دیگه از اعضای کامیونیتی CS12 راه اندازی شده.
هدف دِوچن ایجاد یه بستر برای پرزنت پروژه های نرم افزاری هستش.
پروژه هایی که نه فقط به قصد تولید یک محصول بلکه یادگیری و مهندسی ایجاد میشن! بر خلاف اکثر پروژه هایی که امروزه طی چند ساعت و چند تا پرامپت میان بالا و فقط کار میکنن.
توی DevChan ما فقط پروژه هامونو پرزنت نمیکنیم بلکه مسیر ایجادشون، چالش های م…
پلتفرم DevChan
این روزا همهجا پر شده از پروژههایی که با چندتا پرامپت به AI ساخته شدن، بدون اینکه سازندهشون واقعاً بفهمه زیرش چی میگذره. به این نوع محتوا و پروژهها میگن slop؛ چیزی که سریع تولید شده، شبیه محصول واقعیه، ولی پشتش درک، تلاش و فکر نیست. حجمش هم هر روز بیشتر میشه؛ فیدها، گیتهاب، حتی کامیونیتیهای برنامهنویسی هم دارن پر میشن از این جنس چیزا.
DevChan دقیقاً واکنش به همینه.
یه پلتفرم و کامیونیتی که …
این همون پروژه ایه که گفتم با بچه های CS12 دارم پیش میبرم :)
یه سیستم آموزشی مدرن (Learn with Threads) که این اجازه رو میده مباحث مختلف رو به صورت متنی یاد بگیرید. بدون اینکه مثل سایر منابع و متود های آموزشی مطالب خیلی خشک یا خسته کننده باشن!
خیلی خوشحالم که همچین زمینه ای فراهم شده و من هم جزوی از این پروژه هستم :)
- موفق باشین :) 🎄
سیستم عامل به سبکِ تِرِد قسمت 1
منتشر شد (مطالعه کنید)
نویسنده این کورس : @Univerbity
این کورس بخشی از پروژه NTB در کامیونیتی کامپیوتر ساینتفیک CS12 هست اگر دوست داشتید میتونید عضوی از جامعه CS12 باشید.
@cbe_archive
@ccismywife
#os_cs12
تو سیستم عامل های Unix like (شبه یونیکسی) یه نوع Process وجود داره(البته بیشتر یه وضعیته) به نام Zombie 🧟♂️
اینها پراسس هایی هستن که کارشون تموم شده و Terminate شدن اما هنوز موجودیتشون توی Process table وجود داره.
در واقع کد برنامه تموم شده، فایل ها،منابع و مموری آزاد شده اما PCB اون پراسس همچنان وجود داره و از بین نرفته.
حالا چرا؟ چون پراسس والد باید از پایان کار پراسس فرزند مطلع شه!
وقتی پراسس فرزند تموم میشه اط…
یه چیز بامزه پیدا کردم (تو C، که البته تو زبان های دیگم هست) به نام Bitwise operators که یه سری عملگر هستن و برخلاف عملگر های دیگه با خود مقدار کاری ندارن بلکه با تک تک بیت های مقدار کار میکنن. 🔋
& // AND
| // OR
^ // XOR
~ // NOT (unary)
>> // Shift to right
<< // Shift to left
این عملگر ها با منطق بولی(Boolean logic) کار میکنن و اسماشون بر اساس Logic gate ها نام گذاری شده.(ارجاع به مدار منطقی)
مثلا عدد 5 و 10 رو د…
توی C ما یه مفهوم بامزه داریم به نام Garbage value (مقدار زباله). وقتی یه متغیر local تعریف کنی و بهش مقدار ندی و بخوای ازش استفاده کنی ممکنه با یه خروجی عجیب مواجه شی.
مثلا:
int main()
{
int x;
printf("%i\n",x); //627 🤷
}
این پرینت میتونه هر خروجی بده چون هیچ مقداری بهش assign نکردی.
زبان C ساخت متغیر بدون مقداردهی رو یه undefind behavior (رفتار تعریف نشده) میدونه و هیچ تضمینی بابت خروجی بهت نمیده. ممکنه هر…
بیاید نگاهی هم به پروسه بوت لینوکس داشته باشیم. اینکه وقتی دکمه پاور کامپیوتر رو میزنیم دقیقا چه اتفاقی میوفته👾
خب اول از همه ما یه firmware روی مادربرد داریم که اجرا میشه(میتونه BIOS یا UEFI باشه)
حالا این فرمور که BIOS هستش میادو و اولین سکتور دیسک که MBR هست رو (512 بایت اول دیسک) میخونه. توی این سکتور بوت لودر ما قرار داره. البته این برای قدیما بود. الان با فرمور UEFI بوت لودر(مثلا grub) توی ESP که یه پارتیشن رو…
داداشم اومد گفت بریم برای xbox360 اش بازی بخریم. منم گفتم تا وقتی کپی خور هست چرا DVD 📀
خلاصه این دردسرو به جون خریدمو بعد از تقریبا یه روز ور رفتن با کنسولش و بررسی کلی ریپو تو گیتهاب تونستم کپی خورش کنم(این خودش یه خاطره طولانی میشه).
با کلی چالش برخوردم که به File system بر میگشت و بعد از تحقیق کردن به کلی نکات جالب و بامزه برخوردم.
اولیش این بود که اگر دیوایس استوریجتون(مموریSD،فلش مموری و...) فایل سیستم FAT32 …
مثل دفعه قبل که اینترنت قطع شد همچنان کتاب بهترین یار و یاور بود. کتاب Operating systems and internal design از ویلیام استالینگز رو شروع کردم(که البته بنا به دلایلی تمومش نکردم) و اوایلش به یه کانسپت باحال به نام Instruction execution رسیدم!📚
(تو کتاب های ترجمه شده خیلی بد توضیح داده شده بود)
این که دقیقا تو پایین ترین لایه CPU چجوری دستورالعمل ها رو اجرا میکنه.
ما یه سری رجیستر تو CPU داریم که در حال حاضر با دو تا …
خب اینترنتو بعد از تقریبا ۳ ماه وصل کردن ❤️🩹
به چه قیمتی؟ با چه رویی؟
چند تا کسب و کار باید نابود میشدن؟چند تا آدم باید بیکار میشدن؟ چند تا امید باید ناامید میشد؟
در عرض یه دیقه اینترنتو قطع میکنید و در طی چند هفته قطره چکونی و با منت وصل میکنید.(قطعا محدود تر از قبل)
اینترنت استیبل نیست و معلوم نیست کی دوباره قطع بشه.
یه ریپو ساختم تو گیتهاب داخلش میرورها و ابزار های آفلاین یا قابل دسترس در زمان قطع اینترنت رو گذ…
💔10😐1
Signed Farzad
Showing the 12 most recent of 20 posts we hold for @Univerbity. 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 — 967,437 of 1,478,351entries 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
Republishes
Channels on the register whose posts this channel has forwarded.
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 13 August 2026 — this
entry's latest reading, not the date you are reading this.
“Univerbity” (@Univerbity), 355 subscribers as measured 13 August 2026. Telegram Register, tgregister.com/channel/Univerbity.
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.