Channel
@r_cpp
On this record: Growth · Engagement · Posts · Citations · Cite this entry
229subscribers
+1 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001312615644 |
|---|---|
| Type | Channel |
| Username | @r_cpp |
| Created | Between 1 March 2018 and 31 July 2021— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 21 August 2026 |
| Measurements held | 3 |
| Confirmed unchanged | 1 time, most recently 21 August 2026 |
| On Telegram | t.me/r_cpp |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 21 Aug 2026, 01:33 | 229 | +1 |
| 7 Aug 2026, 03:00 | 228 | no change |
| 6 Aug 2026, 16:26 | 228 | first reading |
20 posts held, back to 29 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 1 pageof 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 (29 July 2026 – 5 August 2026) |
| Views total | 273 |
| Reactions total | — |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 7 Aug 2026, 03:00 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.
Cpp YouTubers Anyone know any good c++ YouTubers? I’m not looking for tutorials or learning the language, I’m looking for videos where people are coding complex projects in C++. Thanks! https://redd.it/1vfpihi @r_cpp
How fast is C++26's std::hive? https://lemire.me/blog/2026/08/02/how-fast-is-c26s-stdhive/ https://redd.it/1vdx0rf @r_cpp
BeCPP Symposium 2026 - Bryce Adelstein Lelbach - The CUDA C++ Developer's Toolbox https://youtu.be/XShALzyd0YU https://redd.it/1vd27y6 @r_cpp
Static Analysis Experiment with Reflection I want to share a little experiment that I made using reflection. It’s a compile-time style checker using C++26 static reflection. It validates the conventions I use in my own projects (the H_ curried callable thing, Mut/Mov/Ref/Cpy qualifier aliases, plus class/namespace naming). Because reflection can’t properly see into uninstantiated templates yet, I had to write a pars…
ranges and views for stack, queue, and priority_queue I've always felt that exposing iterators for `std::stack` or `std::queue` doesn't quite make sense because iterating over them would typically change their state. That said, the range features introduced in C++20/23 are just too tempting. 😄 I bet many C++ developers have had this thought at least once: queue | views::values | views::to<std::vector>() ...o…
Interconverting std::function with copyable_function – Arthur O'Dwyer https://quuxplusone.github.io/blog/2026/07/26/function-explosion/ https://redd.it/1vbjtef @r_cpp
Top 7 desktop app frameworks in 2026 https://teamdev.com/mobrowser/blog/top-7-desktop-app-frameworks-in-2026/ https://redd.it/1vaprni @r_cpp
phase took 2040.9372ms." Anyway. Conclusion: * I now have the data to know how I should go about modularising a codebase for build perf. * Surprisingly, there is a middle-ground between 0% modules and 100% modules where you get optimal build performance. It seems extlibs and your common lib should be modularised and nothing else. Or maybe my internal lib headers are too small to benefit. * Because of that, I might…
1 calls 04.295 seconds Submodules: 1> 141 ms MSBuild 16 calls 1> 775 ms SetModuleDependencies 10 calls 1> 1015 ms CL 2 calls 1> 1132 ms MultiToolTask 1 calls 03.427 seconds The CL entry is for cpp files and it's 4.39x as fast as header-ba…
Build timings from auto-modularised VS solution with external and internal libs To investigate how well modules work with MSVC without rewriting projects and putting up with malfunctioning intellisense, I made a little python script to modularise a whole VS solution (yes, *I* made it, using real bio-neurons). The script lets me try out different modularisation strategies on a VS Solution on a per-project basis: * …
const_cast: A Necessary Evil https://www.elbeno.com/blog/?p=1858 https://redd.it/1v9zcrn @r_cpp
available on [GitHub](https://github.com/PyXiion/pxkorka) (warning: ugly code ahead!). Any feedback and comments are more than welcome. *P.S. This article is an English translation of a post I originally published on Habr a while ago. Keep in mind that some benchmarks and discussions here may be dated.* https://redd.it/1v9v41m @r_cpp
Showing the 12 most recent of 20 posts we hold for @r_cpp. 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,554,226 of 1,602,822entries 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 7 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.
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 21 August 2026 — this entry's latest reading, not the date you are reading this.
“C++ - Reddit” (@r_cpp), 229 subscribers as measured 21 August 2026. Telegram Register, tgregister.com/channel/r_cpp.
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.