Channel
@seniorcpp
On this record: Topic · Growth · Engagement · What this channel posts · Advertising · Posts · Citations · Telegram's recommendations · Cite this entry
11,593subscribers
-120 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 10,000–31,623.
| Telegram ID | -1001427364047 |
|---|---|
| Type | Channel |
| Username | @seniorcpp |
| Created | Between 1 April 2019 and 30 September 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 25 September 2026 |
| Measurements held | 30 |
| Confirmed unchanged | 1 time, most recently 25 September 2026 |
| On Telegram | t.me/seniorcpp |
Technology — 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 55% 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.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 25 Sept 2026, 13:18 | 11,593 | -23 |
| 19 Sept 2026, 04:16 | 11,616 | -9 |
| 16 Sept 2026, 15:39 | 11,625 | -3 |
| 14 Sept 2026, 16:37 | 11,628 | -1 |
| 13 Sept 2026, 05:00 | 11,629 | -2 |
| 8 Sept 2026, 09:54 | 11,631 | -4 |
| 5 Sept 2026, 02:19 | 11,635 | -10 |
| 3 Sept 2026, 09:39 | 11,645 | -2 |
| 2 Sept 2026, 02:45 | 11,647 | -5 |
| 1 Sept 2026, 04:46 | 11,652 | -1 |
| 31 Aug 2026, 05:13 | 11,653 | -2 |
| 30 Aug 2026, 02:33 | 11,655 | -1 |
| 28 Aug 2026, 23:57 | 11,656 | -2 |
| 28 Aug 2026, 03:33 | 11,658 | -5 |
| 27 Aug 2026, 00:33 | 11,663 | -4 |
| 25 Aug 2026, 22:28 | 11,667 | -1 |
| 24 Aug 2026, 21:18 | 11,668 | -4 |
| 21 Aug 2026, 17:58 | 11,672 | -5 |
| 19 Aug 2026, 13:55 | 11,677 | -3 |
| 18 Aug 2026, 14:54 | 11,680 | first reading |
38 posts held, back to 8 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 46 pages of 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 2 September 2026 |
|---|---|
| Posts held | 38 (8 July 2026 – 2 September 2026) |
| Views total | 168 |
| Reactions total | — |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 3 Sept 2026, 00:38 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.
Measured directly from 1 video 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.
An ad marker, not a judgement about a post. A post is counted here because it carries one of two explicit markings: an erid token, which Russian law has required on paid placements since 2022 and which is issued against a specific advertising contract, or a #реклама / #ad hashtag in the body, which is the channel declaring it itself. The first is documentary; the second is a self-declaration and is weaker. No classifier reads the text and decides — nothing on this site guesses that a post is an advertisement.
This is a floor, and it can only ever be a floor. A channel that runs paid placements without marking them produces no marker for us to count, and an unmarked ad is indistinguishable from an ordinary post on the public surface. The ad load above therefore means “the share of posts that declared themselves”, never “the share of posts that were paid for”. A low figure is not evidence of a channel that runs few ads.
Both figures are medians, and no ratio between them is published. Each is a view reading that actually occurred on a post, picked by percentile_disc rather than averaged, so one viral post cannot move it and no interpolated value is invented between two readings. The sample on one side is under five posts, which is too thin to compare. The two figures are shown side by side with the count behind each, and deliberately not divided into a headline like “ads get x% fewer views” — an arithmetic that is easy to print and, at this sample size, means nothing.
| erid | Posts | First seen | Last seen |
|---|---|---|---|
| 2W5zFJMudc5 | 1 | 26 August 2026 | 26 August 2026 |
A token repeated across several posts is one advertising contract placed more than once, which is what the identifier is for. The strings are reproduced exactly as they appeared in the post or in its click-through URL and are not validated against any registry — we record the marker a channel published, and whether it resolves to a real contract is a question for the register that issued it.
Measured over the 38 most recent posts we hold, published 8 July 2026 to 2 September 2026. Views are the latest single reading held for each post, and any reading at or above 1,000 is rounded by Telegram to three significant figures.
std::weak_ptr std::weak_ptr является частью стандартной библиотеки и представляет собой "слабый указатель" на объект, управляемый std::shared_ptr. Он позволяет получать доступ к объекту, на который ссылается std::shared_ptr, но не влияет на его счётчик ссылок. Такой подход полезен в ситуациях, когда мы хотим избежать возможности утечек памяти из-за циклических ссылок между объектами. В этом примере мы создаем два о…
#вопросы_с_собеседований Какие есть особенности работы с shared memory? Работа с разделяемой памятью (shared memory) предполагает использование операций чтения и записи данных в общую область памяти, которая разделяется между несколькими процессами. Среди особенностей можно выделить основные: Синхронизация доступа к этой памяти должна происходить с помощью механизмов синхронизации, иначе возможны ситуации, когда н…
#вопросы_с_собеседований Какие примитивы синхронизации реализованы в C++? В с++ реализовано множество примитивов синхронизации, ниже представлены их предназначения: Mutex - используется для блокировки мьютекса при доступе к разделяемому ресурсу. lockguard и uniquelock - используются для автоматической блокировки и разблокировки мьютекса. condition_variable - используется для уведомления потоков о состоянии раздел…
Что нужно дописать, чтобы при вызове конструктора перемещения член класса действительно "переместился"? Нужно дописать std::move в списке инициализации перемещающего конструктора: A(A&& oth) : str(std::move(oth.str)){ } Но это гарантирует "перемещение" только в том случае, если у этого объекта, в свою очередь, есть перемещающий конструктор (в данном случае, у std::string он есть).
Вычисление количества цифр числа Чтобы вычислить количество цифр в числе, вместо цикла мы можем эффективно использовать log. В нашем примере мы получаем, что количество цифр числа 2468 равно 4.
❓Кто этот призрак в вашем коде: изучаем особенности работы с легаси на C++ Легаси — вот что объединяет всех разработчиков на всех языках программирования. Мы учимся уживаться с «наследием», встраиваем его в современную кодовую базу или стараемся не трогать. Пришло время разобраться с легаси в email-проекте Ghost in the code. Вы получите семь писем от инженеров, в числе которых представитель России в Международной …
Основные концепции библиотеки chrono (C++) Работа со временем как с безразмерной величиной может приводить к недоразумениям и ошибкам конвертации временных единиц измерения. Для избежания таких ошибок предусмотрена библиотека chrono (namespace std::chrono). Она была добавлена в C++11 и дорабатывалась в поздних стандартах. Смотреть статью
#вопросы_с_собеседований Бывает такое, что оператор new не выделяет память? Ответ: Да, бывает, когда new передаётся указатель на уже выделенную память (например, с помощью malloc). Это называется placement new. И оператор new без изменения возвращает второй параметр - указатель (void* operator new(std::size_t, void*)). Это используется для создания объектов в выделенном "хранилище" или после malloc. Важно! В этом с…
Приглашаем на бесплатный открытый вебинар курса «Программист С»: «С без компромиссов: обработка ошибок и полиморфизм» Когда: 25 августа, 20:00 (мск) Язык С даёт полный контроль над памятью и железом, но за эту мощь приходится платить — в нём нет встроенных исключений и классов. Однако, это не значит, что отказоустойчивость и гибкость недоступны. На вебинаре разберём техники, которые обычно остаются за кадром, и пока…
#вопросы_с_собеседований по Си Что такое void указатель? Можно ли разыменовать указатель void, не зная его типа? void указатель — это указатель, который можно использовать для указания на любые данные любого произвольного типа. Указатель void может быть разыменован только после явного приведения. Например: int a = 5; void *b = &a; printf(“%d\n”, *((int*)b));
Алгоритм rotate Меняет местами элементы в диапазоне [first, last) таким образом, что элемент n_first становится первым в новом диапазоне, а n_first-1 — последним. Параметры: first, last - диапазон элементов для изменения их порядка. n_first - элемент, который должен стать первым в новом диапазоне.
#вопросы_с_собеседований Виртуальный конструктор: что он собой представляет? Ответ: Это каверзный вопрос с IT-собеседований, который чаще всего задают после виртуальных деструкторов, чтобы запутать. Конструктор не может быть виртуальным, поскольку в этом нет никакого смысла: при создании объектов нет такой неоднозначности, как при их удалении.😁
Showing the 12 most recent of 38 posts we hold for @seniorcpp. 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.
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.
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.
This channel appears in 2 seed channels' Telegram-generated recommendation lists in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.
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 25 September 2026 — this entry's latest reading, not the date you are reading this.
“Senior C++ Developer” (@seniorcpp), 11,593 subscribers as measured 25 September 2026. Telegram Register, tgregister.com/channel/seniorcpp.
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.