Telegram RegisterThe public register of Telegram
Telegram profile photo for Channel RC

Channel

Channel RC

@channel_rc

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

55subscribers

+0 since we began measuring on 31 August 2026

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

Register entry

Telegram ID-1001434713975
TypeChannel
Username@channel_rc
Created18 April 2020 — measured — dated from the channel’s first post
First recorded31 August 2026
Last confirmed live2 October 2026
Measurements held4
Confirmed unchanged1 time, most recently 2 October 2026
On Telegramt.me/channel_rc

Topic

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 29 September 2026 and assigned it the closest of 31 fixed categories, at 100% 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

545554.531 August 2026 — 55 subscribers31 August 2026 — 55 subscribers17 September 2026 — 54 subscribers2 October 2026 — 55 subscribers31 August 20262 October 2026
4 measurements spanning 32 days. 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 54–55 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
2 Oct 2026, 09:3655+1
17 Sept 2026, 22:4054-1
31 Aug 2026, 22:3755no change
31 Aug 2026, 03:3255first reading

Engagement

18 posts held, back to 18 April 2020 — 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 page 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 18 posts for this entry, the most recent from 22 January 2022. An engagement rate over an empty window would be a number about nothing.

Recent posts

22 Jan 2022, 16:05 UTC322 viewsread 31 August 2026

一个很有趣的 talk: It's Time for Operating Systems to Rediscover Hardware https://www.youtube.com/watch?v=36myc8wQhLo

Signed 一只腊鸡的阿西

30 Dec 2021, 08:53 UTC287 viewsread 31 August 2026

PIC、PIE 和 Copy Relocation https://stdrc.cc/post/2021/12/30/pic-pie-and-copy-relocation/

Signed 一只腊鸡的阿西

2 Dec 2021, 15:39 UTC267 viewsread 31 August 2026

以及今天和实验室某同学交流解决的一个 Rust 和 C 互调用时传 trait object 参数遇到的问题: https://stdrc.cc/post/2021/12/02/rust-ffi-trait-object/

Signed 一只腊鸡的阿西

2 Dec 2021, 15:36 UTC251 viewsread 31 August 2026

上个月在实验室新人培训分享了 CMake 的一些基础用法,以一个无聊项目演进的过程作为例子,感觉还不错,也在这里分享一下~(刚想起来我还有个频道 2333 GitHub:https://github.com/richardchien/modern-cmake-by-example 录屏:https://www.bilibili.com/video/BV14h41187FZ

Signed 一只腊鸡的阿西

3 Jul 2021, 11:45 UTC274 viewsread 31 August 2026

昨天在实验室组会上宣传 Rust 大成功! Slides:https://stdrc.cc/slides/write-os-in-rust-2.0/slides.html 录屏:https://www.bilibili.com/video/BV1tP4y1x7h7 另外感谢迟先生帮忙 review 第一版小 team 分享时的 slides( https://stdrc.cc/slides/write-os-in-rust/slides.html ),前一个链接的第二版在此基础上加入了 Language Basics 部分,并在 Thread Safety 部分换了更好的例子,以及在部分细节处做了细微调整。

Signed 一只腊鸡的阿西

27 Feb 2021, 16:23 UTC253 viewsread 31 August 2026

https://pvs-studio.com/en/blog/posts/0733/ 这篇文章挺精彩,标题是“C++ Is Faster and Safer Than Rust: Benchmarked by Yandex”,但文章主题是反驳这个观点。文章作者 Roman Proskuryakov 针对 C++ 标准委员会的一个代表 Anton Polukhin 在 C++ CoreHard 会议上的演讲中的几个点一一进行了反驳,解释了 Anton 之所以会看到其所说的现象并得出对应观点的原因,句句打脸,厉害!

Signed 一只腊鸡的阿西

26 Sept 2020, 12:56 UTC244 viewsread 31 August 2026

https://www.linux-kvm.org/images/7/79/03x09-Aspen-Andre_Przywara-ARM_Interrupt_Virtualization.pdf 这个 slides 把 ARM 的 GIC 中断虚拟化总结得挺不错,一开始直接看 GIC 手册,看迷糊了,回头看这个 slides + Linux KVM 代码,就清晰很多

Signed 一只腊鸡的阿西

12 Sept 2020, 03:48 UTC228 viewsread 31 August 2026

折腾静态博客生成器很久了,从刚开始学 Python 时候写的 BlogA,到后来重写的「功能看起来更丰富」的 VeriPress,基本满足了自己对一个博客生成器的需求。可是渐渐地,越来越觉得不太对,写 VeriPress 时试图让它变得可扩展,结果导致做了许多对我的需求没有帮助的抽象,代码变得看似解耦实则混乱,最终完全没有动力维护了。 于是前些时间决定再重来一次,对 VeriPress 做一个充分的精简,只保留自己真正需要的功能,尝试用最少的代码实现完美符合自己需求的博客生成器。经过好几次的忙里偷闲,终于写完了,命名为 PurePress。项目的核心 Python 代码只有两个文件,一个是 __init__.py,330 行,用来实现博客的 preview 功能,包括文章的加载、Flask 的路由等,另一个是 __main__.py,260 行,用来实现命令行工具和 build 功能。 PurePress 的一切都是基于我对…

Signed 一只腊鸡的RC

24 Aug 2020, 14:19 UTC216 viewsread 31 August 2026
File

需要先新建一个空文件夹(cmd+shift+n),然后右击该文件夹运行

Signed 一只腊鸡的RC

24 Aug 2020, 14:19 UTC193 viewsread 31 August 2026

分享三个 macOS 上方便开发调试的文件/文件夹快速操作,放在 ~/Library/Services 里面即可,Finder 里面右击文件夹在「快速操作」菜单里可以运行

Signed 一只腊鸡的RC

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

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

“Channel RC” (@channel_rc), 55 subscribers as measured 2 October 2026. Telegram Register, tgregister.com/channel/channel_rc.

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.