Telegram RegisterThe public register of Telegram

Channel

Мастерская системного программирования ИТМО

@itmosysint

On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry

212subscribers

+0 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1002956294673
TypeChannel
Username@itmosysint
DescriptionСообщество ценителей системного программирования ИТМО: firmware, drivers, hypervisor, kernels, BIOS, compilers,.... Канал автора: https://t.me/+2TZRYbxns6tlZjA6
CreatedBetween 1 August 2025 and 6 October 2025— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded8 August 2026
Last confirmed live8 August 2026
Measurements held2
On Telegramt.me/itmosysint

Growth

2127 Aug 2026, 21:29 — 212 subscribers8 Aug 2026, 11:01 — 212 subscribers7 Aug 2026, 21:298 Aug 2026, 11:01
2 measurements taken within a single day. 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 211–213 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
8 Aug 2026, 11:01212no change
7 Aug 2026, 21:29212first reading

Engagement

20 posts held, back to 6 October 2025the 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.

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 7 June 2026. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Photos
12
Videos
5
Links
25

Lifetime counters from Telegram’s own channel header, read 8 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
11m 32s
Average length
2m 53s

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

38 reactions across 12 posts, in 5 distinct kinds. The most used accounts for 42.1% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
1642.1%
🔥1128.9%
👍821.1%
🍓25.26%
🤝12.63%

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 12 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 38reactions 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 6 October 2025 to 7 June 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.

Recent posts

7 Jun 2026, 08:12 UTC448 viewsread 8 August 2026

Подключайтесь! Скоро начинаем! Doom на языке Brainfuck — оно работает! Today, 12:00 – 15:00 GMT+3 https://itmo.ktalk.ru/se85la5vu8gd

5 Jun 2026, 10:52 UTC532 views7 reactionsread 8 August 2026
Video

Друзья! Приглашаю всех на лекцию о том как нам удалось перевести Doom на язык brainfuck! И он заработал. Про эту удивительную технологию вам расскажут непосредственно авторы проекта. Регистрируйтест: https://itmo.events/events/120384 И мы вас ждём: Воскресенье, 7 июня, 12:00-15:00 📍 Гибрид, Песочная Набережная, 14, 306 ауд. + Контур.Толк(Ссылка будет выслана на почту после регистрации) 🧑‍🎓 Для всех желающих

🔥7

4 Jun 2026, 09:29 UTC83 viewsread 8 August 2026
Forwarded from @it_sspacePhoto

😎 Мастерская системного программирования: Doom на языке Brainfuck — оно работает! 💻 Мы скомпилировали легендарный DOOM в один из самых абсурдных эзотерических языков программирования — brainfuck. Заодно написали собственный супербыстрый интерпретатор, чтобы все это действительно заработало 🗣 Вместе с Алексеем Никольским (личный канал), Александром Кравченко и Иваном Сакаевым из Мастерской системного программировани

6 May 2026, 15:03 UTC180 viewsread 8 August 2026
Forwarded from @it_sspaceVideo

👨‍💻 Семинар: VibeCoding в системном программировании 👨🏻‍💻 Алексей Никольский, преподаватель ФБИТ ИТМО из Мастерской системного программирования ИТМО, практикующий эксперт в области программирования, реверс-инжиниринга и работы с операционными системами, в преддверии запуска своего авторского курса Системное программирование 2026 предлагает вам погрузиться в мир настоящего вайбкодинга и выяснить как эффективно и прав

4 May 2026, 13:49 UTC157 views4 reactionsread 8 August 2026
Forwarded from @fbit_livePhoto

🔥Открыта регистрация на интенсив: Системное программирование 2026 На занятиях разберемся: ▪️как работает процессор ▪️как формируются инструкции ▪️как устроена виртуальная и сегментная память ▪️как работают прерывания и взаимодействие с устройствами ▪️основы аппаратной виртуализации ▪️современные технологии защиты TDX/TXT/TPM/VMX и др. ▪️что происходит в первую секунду после включения компьютера На курсе поделимся н

🍓2🔥2

31 Dec 2025, 11:10 UTC374 views6 reactionsread 8 August 2026
Photo

Всем привет! С натупающим новым годом! В этом году мы запустили проект DoomBF - и это очень круто! Уверен в новом 2026м мы это проект успешно завершим и начнем что-то не менее интересное новое! Всех с праздником и удачи вам в новом году!

6

20 Dec 2025, 16:26 UTC802 viewsread 8 August 2026

Всем привет! Начинаем наш стрим в 20:00. При соединяйтесь: https://itmo.zoom.us/j/82746636386

13 Dec 2025, 10:03 UTC339 views1 reactionsread 8 August 2026
Forwarded from @it_sspacePhoto

👨‍💻 Стрим: Кодинг Doom на языке Brainfuck №3 Продолжаем писать Doom на языке Brainfuck вместе с Алексеем Никольским из Мастерской системного программирования ИТМО 🧠 В формате стрима будем доделывать tcc кросс компиляцию для BF. Начнем прописывать основные элементы инфраструктуры C. Участники Мастерской значительно продвинулись - пора генерировать BF код с простого кода на С. Все будет происходить с последнего комми

1

12 Dec 2025, 10:01 UTC221 viewsread 8 August 2026
Forwarded from @ebfecodePhoto

🔥 Hello Coder 2025: Ох уж этот Windows Старт — 15 декабря Внимание: даты курса изменились! Вместо 22–26 декабря мы перенесли интенсив на 15–21 декабря — успевайте присоединиться! На прошлой неделе в Hello Coder мы уже успели: ▪️разобрать основы разработки ПО и проектирование через UML; ▪️полностью написать простой платформер Skybound; ▪️применить множество паттернов (от Singleton и RAII до Factory Method, Facade,

27 Nov 2025, 10:12 UTC218 views1 reactionsread 8 August 2026
Forwarded from @ebfecodePhoto

🎓 Hello Coder 2025: Проектирование ПО Старт 1 декабря. Мы продолжаем интенсив и переходим к важной теме — проектированию программного обеспечения. За 2 недели мы уже: 🕹 создали арканоид под Linux и Windows ⚙️ разобрались с компиляцией и работой C 🎮 изучили C++ и ООП, сделали платформер 🔤 подключили freetype, PNG и др. 👉 Материалы прошлых лекций доступны участникам. На этой неделе: • первый релиз платформера • арх

👍1

25 Nov 2025, 18:35 UTC585 views3 reactionsread 8 August 2026
Photo

Всем привет! Вот запись нашего стрима по tcc в рамках DoomBF. https://vkvideo.ru/video-215805549_456239061 https://rutube.ru/video/7e605935d18ee02308ea664e635c8fa3/ https://youtu.be/EvosXkY_Ccg Всем приятного просмотра! И в декабре ждите продолжение!

👍2🤝1

23 Nov 2025, 13:15 UTC513 views2 reactionsread 8 August 2026
Photo

Всем привет! Скоро начинаем стрим по кодингу tcc для проекта DoomBF! Старт в 18, готовьте чаек :Р https://itmo.zoom.us/j/85152361321

1👍1

Showing the 12 most recent of 20 posts we hold for @itmosysint. 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,068,583 of 1,183,361entries 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

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.

Names

Channels on the register whose handles appear in this channel's posts.

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 8 August 2026 — this entry's latest reading, not the date you are reading this.

“Мастерская системного программирования ИТМО” (@itmosysint), 212 subscribers as measured 8 August 2026. Telegram Register, tgregister.com/channel/itmosysint.

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.