Channel
@cpp_geek
On this record: Growth · Engagement · Reactions · Posts · Citations · Cite this entry
3,542subscribers
-24 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
| Telegram ID | -1001544053563 |
|---|---|
| Type | Channel |
| Username | @cpp_geek |
| Created | Between 1 August 2021 and 28 February 2023— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 26 August 2026 |
| Measurements held | 8 |
| Confirmed unchanged | 1 time, most recently 26 August 2026 |
| On Telegram | t.me/cpp_geek |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 26 Aug 2026, 22:55 | 3,542 | -10 |
| 23 Aug 2026, 19:52 | 3,552 | -4 |
| 19 Aug 2026, 22:03 | 3,556 | -2 |
| 16 Aug 2026, 17:36 | 3,558 | -6 |
| 13 Aug 2026, 12:17 | 3,564 | -2 |
| 10 Aug 2026, 10:06 | 3,566 | -1 |
| 7 Aug 2026, 10:20 | 3,567 | +1 |
| 7 Aug 2026, 06:16 | 3,566 | first reading |
20 posts held, back to 26 June 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 3 pagesof 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 5 August 2026 |
|---|---|
| Posts held | 20 (26 June 2026 – 5 August 2026) |
| Views total | 1,615 |
| Reactions total | 22 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 7 Aug 2026, 23:08 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.
106 reactions across 20 posts, in 8 distinct kinds. The most used accounts for 58.5% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 👍 | 62 | 58.5% | |
| 🔥 | 16 | 15.1% | |
| ❤ | 14 | 13.2% | |
| 👎 | 5 | 4.72% | |
| 💩 | 4 | 3.77% | |
| ✍ | 2 | 1.89% | |
| ❤🔥 | 2 | 1.89% | |
| 🤝 | 1 | 0.943% |
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 106reactions 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 26 June 2026 to 5 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.
Move-семантика: где можно ловко сэкономить Многие знают про std::move, но не всегда используют его там, где это реально ускоряет код. Простой пример — возврат локального объекта из функции: #include <string> std::string make_string() { std::string s = "Hello"; return s; // RVO или move } С C++17 тут почти всегда RVO (Return Value Optimization). Но если RVO невозможен (например, возвращаем тернарный опер…
👍2❤1❤🔥1
Зачем std::move от std::string в emplace_back? Кажется, emplace_back(std::move(str)) — избыточно: ведь emplace_back сам конструирует объект на месте. Но с std::string и другими перемещаемыми типами всё не так просто. Пример: std::vector<std::string> vec; std::string str = "hello"; vec.emplace_back(str); // копия vec.emplace_back(std::move(str)); // перемещение Почему? Потому что: > emplace_back в…
👍4❤3
Что такое ADL и как она может вас подставить Argument-Dependent Lookup (ADL) — это фича, которая может как упростить код, так и привести к сюрпризам. Представьте: namespace math { struct Vec {}; void print(const Vec&) { std::cout << "Vec\n"; } } void foo() { math::Vec v; print(v); // компилятор найдёт math::print через ADL! } Хотя print не в текущем скоупе, компилятор ищет её в nam…
👍3✍2❤1🤝1
std::thread std::thread является частью стандартной библиотеки C++ и предоставляет возможность создания и управления потоками выполнения. Он позволяет запускать функции в отдельных потоках, обеспечивая параллельное выполнение кода. Обратите внимание, что после создания потока std::thread, вы должны вызвать join() или detach() для корректной обработки завершения потока. В приведенном примере мы использовали join(),…
👍2❤1🔥1
Полезные функции, которые будут полезны продвинутым C++ разработчикам. 1. void assert_or_throw(bool cond, const std::string& msg) Универсальная замена assert в runtime-среде: void assert_or_throw(bool cond, const std::string& msg) { if (!cond) throw std::runtime_error(msg); } 2. template<typename T> std::string to_string_precise(const T& val, int precision = 6) Преобразование чисел с точностью: template…
👍2🔥2
🚀 Подборка полезных IT каналов в Max Системное администрирование, DevOps 📌 https://max.ru/i_odmin Все для системного администратора https://max.ru/bash_srv Bash Советы https://max.ru/sysadminof Книги для админов, полезные материалы https://max.ru/i_odmin_book Библиотека Системного Администратора https://max.ru/i_devops DevOps: Пишем о Docker, Kubernetes и др. https://max.ru/tipsysdmin Типичный Сисадмин https://max…
💩4❤1👎1
🧵 Сегодня покажу вам простой способ логгировать вызовы функций в C++ — пригодится для отладки и анализа кода. Часто бывает нужно понять, какие функции вызываются, в каком порядке и с какими параметрами. Вручную вставлять std::cout — неудобно. Вместо этого используем RAII-макрос с выводом в консоль: #include <iostream> #include <string> struct FunctionLogger { std::string func_name; FunctionLogger(const st…
👍7🔥1
Невидимый UB: возвращаем ссылку на локальную переменную Одна из самых коварных ошибок в C++ — возврат ссылки на переменную, срок жизни которой закончился. Казалось бы, всё компилируется, запускается... и даже иногда "работает". А под капотом — undefined behavior. Пример: const std::string& getName() { std::string name = "John"; return name; // 💥 Возвращаем ссылку на локальный объект } Функция возвращае…
👍5
Тема: Почему std::vector<bool> - не совсем std::vector На первый взгляд std::vector<bool> — обычный вектор, только из булевых значений. Но это особенный шаблон. Вместо хранения bool как полноценного байта, он упаковывает их в биты. Экономит память? Да. Но есть нюансы. Пример: std::vector<bool> flags = {true, false, true}; auto x = flags[0]; // Не bool, а прокси-объект! bool y = flags[0]; // OK — коп…
👍2🔥2❤1
Ключевые библиотеки Boost, которые полезно знать каждому C++ разработчику Вот топ-5 библиотек Boost: 1️⃣ Boost.Asio Асинхронный ввод-вывод и сетевое программирование. Незаменим для серверных приложений. 2️⃣ Boost.Beast HTTP и WebSocket клиенты/серверы. Построен на Asio. 3️⃣ Boost.Serialization Сериализация сложных структур данных в потоки байтов и обратно. 4️⃣ Boost.Graph Алгоритмы на графах: поиск путей, обходы…
👍4❤1
Зачем [[nodiscard]] нужен не только для возврата значения Если ты думаешь, что [[nodiscard]] — это просто защита от игнора Result, то вот фокус: его можно вешать и на классы, и на функции, и даже на enum — и это реально помогает избежать багов. Пример: struct [[nodiscard]] Error { std::string message; }; Error do_something() { return {"Что-то пошло не так"}; } void foo() { do_something(); // warning…
🔥2❤1👍1
Сейчас покажу вам простой, но очень полезный приём, как аккуратно и безопасно управлять ресурсами в C++ с помощью RAII (Resource Acquisition Is Initialization). Когда вы работаете с ресурсами (файлы, сокеты, мьютексы и т.д.), важно не забывать освобождать их. Особенно если программа может завершиться по исключению. И вот тут RAII — наш лучший друг. Рассмотрим пример: #include <fstream> #include <string> void wri…
👍4
Showing the 12 most recent of 20 posts we hold for @cpp_geek. 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 — 1,416,319 of 1,621,754entries 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.
Named by 3 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.
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.
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 26 August 2026 — this entry's latest reading, not the date you are reading this.
“C++ geek” (@cpp_geek), 3,542 subscribers as measured 26 August 2026. Telegram Register, tgregister.com/channel/cpp_geek.
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.