Channel

C++ and other lectures

@cpp_lects_rus

On this record: Topic · Growth · Engagement · Reactions · Posts · Citations · Cite this entry

9,899subscribers

+167 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of 3,162–10,000.

Register entry

Telegram ID	-1001685993545
Type	Channel
Username	@cpp_lects_rus
Created	Between 1 December 2021 and 30 April 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded	7 August 2026
Last confirmed live	16 September 2026
Measurements held	13
Confirmed unchanged	1 time, most recently 16 September 2026
On Telegram	t.me/cpp_lects_rus

Topic

Education — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-FP8, prompt version 1) read this channel’s own recent posts on 11 September 2026 and assigned it the closest of 31 fixed categories, at 57% confidence. This is a model’s judgement about what the channel is likely to be about, not a fact this register measured the way a subscriber count or a view count is measured — it can be revised on a later pass, and it carries no weight anywhere else on this page. How this classification works, and why it has no browse page of its own yet.

Growth

13 measurements spanning 40 days, net +167. 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,706–9,924 and does not start at zero.

Measurement log — every subscribers count we have recorded
Measured (UTC)	Subscribers	Change
16 Sept 2026, 07:42	9,899	+23
12 Sept 2026, 08:16	9,876	+5
8 Sept 2026, 12:00	9,871	+25
3 Sept 2026, 06:36	9,846	+26
30 Aug 2026, 15:54	9,820	+39
27 Aug 2026, 22:27	9,781	+33
24 Aug 2026, 22:08	9,748	-4
21 Aug 2026, 06:44	9,752	+14
17 Aug 2026, 21:58	9,738	+1
14 Aug 2026, 14:26	9,737	+3
10 Aug 2026, 19:11	9,734	+3
7 Aug 2026, 16:54	9,731	-1
7 Aug 2026, 03:01	9,732	first reading

Engagement

23 posts held, back to 18 May 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 35 pages 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 23 posts for this entry, the most recent from 21 August 2026. An engagement rate over an empty window would be a number about nothing.

Reaction mix

2,481 reactions across 23 posts, in 30 distinct kinds. The most used accounts for 29.4% of them.

Every reaction kind recorded on the sample, most used first
Reaction	Count	Share
🔥	729	29.4%
👍	606	24.4%
❤	360	14.5%
👎	221	8.91%
💩	119	4.80%
😁	83	3.35%
🤩	83	3.35%
❤‍🔥	69	2.78%
🤮	68	2.74%
🥴	26	1.05%
🤯	25	1.01%
🥰	18	0.726%
✍	15	0.605%
🙏	9	0.363%
🗿	7	0.282%
🤣	7	0.282%
🌭	6	0.242%
🥱	6	0.242%
👏	5	0.202%
🫡	4	0.161%
10 further kinds	15	0.605%

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 23 of the 23 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 2,481 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 23 most recent posts we hold, published 18 May 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.

Recent posts

21 Aug 2026, 19:17 UTC≈4,150 views113 reactionsread 29 August 2026

Photo

Чем заняться вечером и на выходных? Конечно чтением книги по C++. Я как раз выложил главы 2.3 и 2.4 https://boosty.to/cpp_lects_rus/posts/0b557d7e-d4a2-4d30-881a-c8ea704d67ba Спасибо всем моим подписчикам на boosty за поддержку которая вдохновляет меня работать над этой книгой и подписчикам уровня principal и выше за участие в ревью. Я, между прочим, суммарно написал уже больше, чем моя прошлая книга по компилятор…

🔥77🥰17❤13🌭5😁1

20 Aug 2026, 18:42 UTC≈4,520 views65 reactionsread 29 August 2026

Выложили выступление на C++ Russia моего коллеги Юлия Тарасова. https://youtu.be/Zrwe4vCzvbM Юлий рассказывает про std::simd 00:00 Начало. Опрос про векторные интринсики, язык боли и язык страданий. 06:00 Автовекторизация в компиляторе 12:05 Абстрагирующие библиотеки и std::simd 18:35 Интеграция со стандартной библиотекой и выравнивание 23:15 Время некоторых конкретных замеров 30:22 Ограничения std::simd и альтерн…

❤‍🔥32👍19🔥12✍1❤1

13 Aug 2026, 13:18 UTC≈7,320 views76 reactionsread 29 August 2026

Выложили наш с Лизой доклад на ZCC. Спасибо организаторам за оперативность. https://youtu.be/ohYtMHBXLvM?is=lwvD3swa1fLQOPff 00:00 Начало и немного о мире стабильного ABI: немного C и ассемблера 10:35 Про ABI в C++ и генерализованную перегрузку сущностей 16:02 Появление Лизы и много компиляторной магии 35:20 Возвращение меня и история про static chain register 40:10 Ответы на вопросы. #conference

🔥40👍24❤10🥴1🙏1

1 Aug 2026, 18:53 UTC≈9,510 views181 reactionsread 29 August 2026

Forwarded from @postironic_cppPhoto

Photo, posted without a caption

🤩83😁70❤17🤣6⚡1🌭1🍓1👍1

1 Aug 2026, 18:53 UTC≈8,460 views39 reactionsread 29 August 2026

Выступил на C++ ZCC. Видео выложу по мере появления. А пока мне тут скинули бинго по моим докладам на конференциях. Не знаю только при чем тут userver. #official

👍30❤9

31 Jul 2026, 15:37 UTC≈8,560 views45 reactionsread 29 August 2026

И снова пятничный зачилл. Подумайте вот о таком коде. Сначала не открывая годболт. Что скажете? struct T { const int &p; }; void foo() { T t{0}; } // ??? void bar() { T t(0); } // ??? Теперь откройте ссылку и сверьте ощущения. https://godbolt.org/z/6rfGzx991 Кто прав — gcc или clang? Или... оба? ))) Ссылки на стандарт обязательны. За нейронку — штрафные баллы )) Пример восхитителен не глубокими причинами в ст…

🥴25❤14🤔3❤‍🔥1🎉1👏1

24 Jul 2026, 06:24 UTC≈9,990 views113 reactionsread 29 August 2026

К слову о разговорных жанрах. Выложили интервью со мной на C++ Russia. Вроде неплохо получилось. https://youtu.be/jeX96GPYSlI?is=kwLq3K1Qtvy64oE1 #conference

🔥66👍30❤13🐳2👏1🙏1

22 Jul 2026, 18:54 UTC≈9,320 views55 reactionsread 29 August 2026

Photo

Всем привет. Отчётный стрим на boosty проведу в воскресенье, 26 июля в 20 по Москве. https://boosty.to/cpp_lects_rus Уровень доступа: студент и выше. Обсудим прогресс по книге, прошедшую конференцию C++ Russia, предстоящую Zero Cost Conf и многое другое. #boosty

👍34❤13🔥5❤‍🔥1🥰1🙏1

16 Jul 2026, 20:14 UTC≈11,100 views123 reactionsread 29 August 2026

Выложили моё видео на C++ Russia 2026, посвящённое выводу типов, его тонкой связи с перегрузкой и некоторым моим мечтам о языке. https://youtu.be/ebyXav1JAEQ?is=rAumvFRI4sFTRFPQ 00:00 Intro: немного болтовни 03:20 Начало. Напоминаю про семантические процессы 06:10 Мечта про инференс в стиле Хиндли-Милнера и как перегрузка ломает унификацию. 11:58 Почему мы любим перегрузку и как мы пишем множества перегрузки? 16:54…

🔥73👍27❤21❤‍🔥1🙏1

15 Jul 2026, 10:42 UTC≈8,030 views531 reactionsread 29 August 2026

Сделал свой канал в Max публичным. Теперь буду туда всё дублировать: https://max.ru/channel_cpp_lects_rus И появились комментарии. #official

👎219💩119🤮68👍67✍14🔥14❤12🗿7

5 Jul 2026, 09:01 UTC≈11,900 views86 reactionsread 29 August 2026

Выложил лекцию Анастасии Черниковой о практическом внедрении llvm-snippy в верификацию аппаратуры на примере открытого RISC-V ядра Ibex. https://youtu.be/fSsq5mm3I40 Эта лекция -- настоящее путешествие по применению llvm-snippy в живой DV-инфраструктуре. Она затрагивает вопросы: как встроиться в существующий маршрут с riscv-dv, как написать хороший враппер и как доработать загрузчик и обработчики прерываний. Всё и…

👍44❤21🔥16❤‍🔥3🤯1😍1

27 Jun 2026, 17:39 UTC≈10,800 views72 reactionsread 29 August 2026

У llvm-snippy теперь есть DOI. Мы добавили в репозиторий citation metadata и заархивировали проект на Zenodo: https://doi.org/10.5281/zenodo.20969925 Если вы используете llvm-snippy в статьях, отчётах, диссертациях, прототипах, исследовательских проектах или просто в воспроизводимых экспериментах, пожалуйста, ссылайтесь на него. Это важно не только как формальная благодарность авторам. Для нас, как команды разраб…

👍49🔥16❤6👏1

Showing the 12 most recent of 23 posts we hold for @cpp_lects_rus. 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.

Forward network

Republishes

Channels on the register whose posts this channel has forwarded.

C++: Хроники Дурки🚑
@cpp_durka · 9161 post Постироничные идеи для ебаного C++
@postironic_cpp · 5531 post

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 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.

C++: Хроники Дурки🚑
@cpp_durka · 9162 posts GPGPU Russia
@gpgpu_ru · 5201 post

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

“C++ and other lectures” (@cpp_lects_rus), 9,899 subscribers as measured 16 September 2026. Telegram Register, tgregister.com/channel/cpp_lects_rus.

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.