Telegram RegisterThe public register of Telegram
Telegram profile photo for Welcome to the Black Parade

Channel

Welcome to the Black Parade

@Welcome2TheBlackParade

On this record: Topic · Previous handles · Growth · Engagement · Reactions · Stars · Posts · Citations · Cite this entry

1,113subscribers

+66 since we began measuring on 6 August 2026

Risers and fallers across the register · movement among entries of 1,000–3,162.

Register entry

Telegram ID-1001459082815
TypeChannel
Username@Welcome2TheBlackParade
CreatedBetween 1 April 2019 and 31 October 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded6 August 2026
Last confirmed live17 September 2026
Measurements held11
Confirmed unchanged1 time, most recently 17 September 2026
On Telegramt.me/Welcome2TheBlackParade

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

Previous handles

@Welcome2TheBlackParade was previously reachable at this handle, before switching to its current one. This says nothing about who or what answers at the old handle today — only that this channel no longer does.

@TheB1ackParade
held 6 August 20266 August 2026

Growth

1,0461,1131,079.56 August 2026 — 1,047 subscribers6 August 2026 — 1,047 subscribers13 August 2026 — 1,046 subscribers16 August 2026 — 1,055 subscribers27 August 2026 — 1,079 subscribers28 August 2026 — 1,084 subscribers31 August 2026 — 1,093 subscribers3 September 2026 — 1,099 subscribers9 September 2026 — 1,103 subscribers12 September 2026 — 1,106 subscribers17 September 2026 — 1,113 subscribers6 August 202617 September 2026
11 measurements spanning 41 days, net +66. 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 1,036–1,123 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
17 Sept 2026, 00:181,113+7
12 Sept 2026, 20:201,106+3
9 Sept 2026, 04:561,103+4
3 Sept 2026, 20:571,099+6
31 Aug 2026, 06:231,093+9
28 Aug 2026, 00:151,084+5
27 Aug 2026, 09:001,079+24
16 Aug 2026, 21:171,055+9
13 Aug 2026, 11:181,046-1
6 Aug 2026, 12:521,047no change
6 Aug 2026, 12:481,047first reading

Engagement

24 posts held, back to 17 June 2026the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 2 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
69.0%
avg views ÷ 1,113 subscribers
Avg views / post
768
1 post measured
Reaction rate
4.17%
reactions ÷ views · ER floor
Posts in window
1
of 24 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.

What these figures were computed from
WindowRolling 30 days · latest post in window 27 August 2026
Posts held24 (17 June 202627 August 2026)
Views total768
Reactions total32
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken27 Aug 2026, 09: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.

Reaction mix

261 reactions across 20 posts, in 15 distinct kinds. The most used accounts for 36.4% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
9536.4%
🤯3413.0%
👍197.28%
😁186.90%
🥰186.90%
🔥145.36%
134.98%
👏114.21%
👀83.07%
😐83.07%
🙏72.68%
🤮72.68%
🍌62.30%
🌭20.766%
🙊10.383%

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 21 of the 24 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 261 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 24 most recent posts we hold, published 17 June 2026 to 27 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.

Telegram Stars

Stars received
3
across the posts below
Posts paid on
3
of 24 we hold a reading for · 13%
Most on one post
1
single highest reading

A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @Welcome2TheBlackParade. Telegram publishes the count on the public post preview alongside ordinary reactions, and this register reads it there. It is the only figure on this site that measures money moving rather than attention.

Stars are not reactions, and the two are never added. They are rendered in the same strip on Telegram and counted in the same shape, but one is a tap and the other is a purchase. The reaction totals and the engagement rate elsewhere on this page exclude every figure in this section, and no rate here is computed against a reaction count.

This is not revenue, and we publish no currency figure. What a Star costs a reader and what it pays a channel are different numbers, Telegram takes a share we cannot observe, and the terms have changed. Converting a Star count into money would be an estimate dressed as a measurement, so the count is where we stop.

Counted over the 24 most recent posts we hold for this entry, published 17 June 2026 to 27 August 2026. Star counts above 1,000 reach us in Telegram’s short form and carry the same three-significant-figure rounding as everything else on this page.

Recent posts

17 Aug 2026, 13:31 UTC696 viewsread 27 August 2026
Photo

终于看懂 3sum 算法了,太难了但开心,发张裸照庆祝一下 写一篇 telegram article 庆祝一下😃

14 Aug 2026, 08:52 UTC≈1,950 views28 reactions1 Starread 27 August 2026

发现 go 的 chan 性能比我想象中好很多,大吃遗精。 一开始是我有个 SPSC 的场景,一个 goroutine 从内核读数据塞给 chan,另一个 goroutine 读 chan 处理事件。perf 一下发现 25% 的 cpu 浪费在 chan 通知机制,我才想起这里应该用 buffered chan 减少通知次数。linux kernel 收包流程有类似的工程设计了,NAPI 处理 rx 时硬中断通知网络收包,然后 mask rx queue、用软中断持续 poll 直到没有流量再重新打开硬中断,显著降低通知次数。 然后我冲冠一怒,觉得区区 SPSC,手搓场景特化 ringbuf 轻轻松松快到飞起,弱智 golang 快来见识我的神力吧! 第一版是用 bpf ringbuf 的设计,裸字节消息 + 双重 mmap (Welcome to the Black Parade),SPSC 也不需用原子指令,仔细编排

18🍌6🔥3🙊1

13 Aug 2026, 01:49 UTC855 views16 reactionsread 27 August 2026

我才从前同事听说 Kubecon 明文要求三人及以上的联合演讲必须有女性: https://events.linuxfoundation.org/kubecon-cloudnativecon-north-america/co-located-events/cfp-colocated-events/#submission-types Panel Discussion: 35 minutes of discussion amongst 3 to 5 speakers https://events.linuxfoundation.org/kubecon-cloudnativecon-north-america/co-located-events/cfp-colocated-events/#important-notes In an effort to promote speaker equity and inclusivity, C

😐8🤮71

6 Aug 2026, 03:25 UTC≈1,070 views6 reactionsread 27 August 2026
Photo

悲剧啊😭大意了,因为初始症状没有刀片嗓我就没有第一时间做肛拭子,还坚持去办公室投毒,问心有愧,决定翘班从现在开始🤨

🔥6

1 Aug 2026, 09:32 UTC≈1,970 views0 reactionsread 27 August 2026

手滑眼瞎型 bug 是我一生之敌,下面的 n 皇后我一次写出然后 wrong answer,肉眼观察+心灵分析+小黄鸭debug十多分钟毫无进展只能请教 LLM 才发现写错变量。别问为什么不一开始就 LLM debug,面试考察心灵😭至于为什么我还在用心灵面试,中老年再就业是这样的,人无再少年😊 class Solution: def solveNQueens(self, n: int) -> List[List[str]]: chess = [[0] * n for _ in range(n)] ans = [] def search(idx): if idx == n: o = [] for line in chess: o.append(''

24 Jul 2026, 08:41 UTC≈1,840 views13 reactionsread 27 August 2026

看了昨天 @ManjusakaH 转发的 simd 科普之后我才知道原来字符串搜索也可以 simd,我当时就萌生了一个大胆的想法,何不买一根 335mm Φ8mm 的金属棒 何不让 bpf 也用 simd 搜索 http header,目前的实践都是狗屎,我和同事在 6.1 ec2 上编译 kfunc 的惨痛经历仿佛还在昨天😭 任务是从巨型 HTTP/1.1 payload 里搜索你喜欢的 header,比如 Host: GET /url HTTP/1.1 User-Agent: xxx X-Forward: xxx X-Metadata: xxx [...1000+ bytes...] Host: xxx 虽然 bpf simd 是做不了的,但可以 SWAR 啊,我用 go 写一遍是这样的 const ( repeatLF = uint64(0x0a0a0a0a0a0a0a0a) ones = uint64

13

24 Jul 2026, 07:10 UTC≈1,580 views11 reactionsread 27 August 2026

下面的 go 程序能跑起来吗? package main import ( "log" "net" "os" ) func main() { ln, err := net.Listen("tcp", ":"+os.Args[1]) if err != nil { log.Fatal(err) } defer ln.Close() select {} } 有了 LLM 就跟玩游戏输秘籍似的,operation CWAL,猜谜都不 exciting 了😵 直接快进到答案,取决于 CGO_ENABLED,=0 会被判定死锁,=1 可以跑起来,原因就问 LLM 吧🤬 (发现 ps -o wchan 很好用,还有 /proc/pid/stack,procfs 真是大秘宝

🤯11

23 Jul 2026, 17:09 UTC799 views11 reactionsread 27 August 2026
Photo

我手搓的 HTTP/1.1 header 搜索居然比 bpf kfunc 还快,直达天际的好奇心,咕咕咕咕,不可思议都成了常识,拉哩噜雷啦啦啦。 事已至此,先发一张AI裸体虎杖悠仁 奥西里斯天空龙冷静一下,明天 wfh 摸鱼的时候再仔细介绍,感谢隔壁频道给我零感让我异想天开,性奋。

👀8🔥3

20 Jul 2026, 10:01 UTC≈1,890 viewsread 27 August 2026
Photo

中午已经听到捷报,AI在人类看世界杯的时候随手证否了八十多年前的著名数学猜想😂 猜你喜欢:OpenAI 证明单位距离猜想 https://m.bilibili.com/video/BV1G7jJ6nEbV

19 Jul 2026, 12:19 UTC≈1,910 views16 reactionsread 27 August 2026
Photo

病假当年假休了十天,在b站学习筛法证明素数的有界间距,独立战旗游戏《Tactical Breach Wizards》全成就进度68%,三场中老年异性恋地下情人故事会,不看书不学习一行代码都不写,马龙甚至还拿了男双冠军,这样的日子不多,要珍惜。

16

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

Stars beside a post are paid reactions — Telegram Stars, bought with money and spent on that post. They are a different unit from reactions and are never added to them, here or anywhere else on this page.

Forward network

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

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

“Welcome to the Black Parade” (@Welcome2TheBlackParade), 1,113 subscribers as measured 17 September 2026. Telegram Register, tgregister.com/channel/Welcome2TheBlackParade.

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.