https://mp.weixin.qq.com/s/G0CofYHly1uVekuE3fpywg 泪目,开源精神

Channel
Leon Hwang 碎碎念
@eBPFTalk001
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
319subscribers
+0 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
Register entry
| Telegram ID | -1001812600222 |
|---|---|
| Type | Channel |
| Username | @eBPFTalk001 |
| Description | This is a channel to talk about eBPF mainly from Leon Hwang. Welcome! |
| Created | Between 1 October 2022 and 30 September 2023— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 6 August 2026 |
| Last confirmed live | 12 August 2026 |
| Measurements held | 2 |
| On Telegram | t.me/eBPFTalk001 |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 6 Aug 2026, 22:03 | 319 | no change |
| 6 Aug 2026, 12:53 | 319 | first reading |
Engagement
19 posts held, back to 1 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 · 30 days
- 60.1%
- avg views ÷ 319 subscribers
- Avg views / post
- 192
- 11 posts measured
- Reaction rate
- 1.04%
- reactions ÷ views · ER floor
- Posts in window
- 11
- of 19 held
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. It is computed over the 5 of 11 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 5 August 2026 |
|---|---|
| Posts held | 19 (1 July 2026 – 5 August 2026) |
| Views total | 2,109 |
| Reactions total | 11 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 6 Aug 2026, 22:03 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.
What this channel posts
- Photos
- 199
- Links
- 511
Lifetime counters from Telegram’s own channel header, read 6 August 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.
Reaction mix
21 reactions across 10 posts, in 3 distinct kinds. The most used accounts for 76.2% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 👍 | 16 | 76.2% | |
| ❤ | 4 | 19.0% | |
| 👨💻 | 1 | 4.76% |
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 10 of the 19 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 21reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 19 most recent posts we hold, published 1 July 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.
Recent posts
坏消息: 1,str kfunc 优化的 RFC 被 Andrii 挡回来了,嫌弃改动的有点复杂。。。 2,还在给 #tracing_multi 清理一些边角料:cornor case bugfix,selftests 整理一下;然后拉一大坨支持一下 #tracing_multi trace bpf progs(bpfsnoop 的需求)。。 3,等 Andrii review #global_percpu_data ,期望早日合入;这个 series 已经相当成熟了。
月底了,公司的限额 Claude/Codex 蹬完了吗?
在 Codex 老师的指导下,研究了 ftrace&arm64-BL/BR 一晚上,觉得 ftrace 里的 DYNAMIC_FTRACE_WITH_DIRECT_CALLS 和 SINGLE_FTRACE_DIRECT_OPS 都是 Jiri 专门为 BPF 搞的 CONFIGs。。。 再看一下 Jiri 的回复, hmmm 他也用 Codex 研究 arm64 的 case 😑 我在给 arm64 开启一下 #tracing_multi 特性。。涉及 arm64&ftrace&BPF 看到 Anthropic 的 PATCH: arm64: ftrace: support DIRECT_CALLS without CALL_OPS ,就想到最近在搞的 tracing_multi 特性
👍1
经过 Codex 老师调戏优化后,新版 kfunc 吊打旧版 kfunc #bpf_str_kfunc
👍3
再修个 BUG:sleepable fentry 可以 trace 名为 __x64_sys_xx 的 XDP 程序;就是 __x64_ 前缀绕过了 verifier 的校验。 图一:艹了,发现是我曾经 review 过的 patch 引入的 BUG。 图二:跑起来后,会触发内核 BUG。 在搞 #tracing_multi trace bpf prog 的 series,用 AI review 出第 3 个已存在的 BUG 了。 :(
这是。。将 lwt-bpf 的老底打穿了? #lwt_bpf
麻了,AI review 出我之前 tailcall bugfix 的代码有 bug。。。 Shared trampoline flags can be corrupted at load time When loading a tracer for a tail-call-reachable target, the verifier does: tr->flags = BPF_TRAMP_F_TAIL_CALL_CTX; at kernel/bpf/verifier.c:19525. 得复现一下,再提个 bugfix 😵😵
👍3👨💻1
给 interpreter 修 BUG:bpf: Disallow interpreter fallback for interpreter-unsupported insns 估计 interpreter 要被干掉了的节奏 #interpreter
❤1👍1
最近看到 UAF 都害怕;已经分析了 2 个 UAF 引发的 CVE。。 bpf 社区里有人说 tracing link 在 release 时可能会触发 UAF,unbelievable。。。😤 (Jiri 背锅) 再继续问,是他们 OOT drivers 导致的 😠😠😠
mm 的 patch 就合入了??! 好吧,其实这个 patch 就修一下 typo 和修理一下 mseal.rst 和代码 comment Lance 提供的机会,紧紧抱住他的大腿
❤1
胆儿肥了,同时向 bpf, mm, and net 社区发 patch 。。
❤2
Showing the 12 most recent of 19 posts we hold for @eBPFTalk001. 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
Citation-graph rank — 41,609 of 1,340,412entries 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.
Forward network
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
Republishes
Channels on the register whose posts this channel has forwarded.
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 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.
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 6 August 2026 — this entry's latest reading, not the date you are reading this.
“Leon Hwang 碎碎念” (@eBPFTalk001), 319 subscribers as measured 6 August 2026. Telegram Register, tgregister.com/channel/eBPFTalk001.
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.