Telegram RegisterThe public register of Telegram
Telegram profile photo for 层叠 - The Cascading

Channel

层叠 - The Cascading

@outvivid

On this record: Growth · Engagement · Reactions · Posts · Posts edited after publishing · Citations · Telegram's recommendations · Cite this entry

8,986subscribers

+189 since we began measuring on 6 August 2026

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

Register entry

Telegram ID-1001378594303
TypeChannel
Username@outvivid
Created19 February 2018measured — cross-checked against a third-party dataset (TGDataset)
First recorded6 August 2026
Last confirmed live7 September 2026
Measurements held12
Confirmed unchanged1 time, most recently 7 September 2026
On Telegramt.me/outvivid

Growth

8,7978,9868,891.56 August 2026 — 8,797 subscribers6 August 2026 — 8,799 subscribers9 August 2026 — 8,836 subscribers12 August 2026 — 8,844 subscribers15 August 2026 — 8,854 subscribers18 August 2026 — 8,856 subscribers21 August 2026 — 8,873 subscribers24 August 2026 — 8,880 subscribers27 August 2026 — 8,884 subscribers30 August 2026 — 8,901 subscribers2 September 2026 — 8,974 subscribers7 September 2026 — 8,986 subscribers6 August 20267 September 2026
12 measurements spanning 32 days, net +189. 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 8,769–9,014 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
7 Sept 2026, 05:168,986+12
2 Sept 2026, 19:338,974+73
30 Aug 2026, 22:538,901+17
27 Aug 2026, 17:048,884+4
24 Aug 2026, 21:168,880+7
21 Aug 2026, 10:468,873+17
18 Aug 2026, 18:338,856+2
15 Aug 2026, 16:258,854+10
12 Aug 2026, 12:388,844+8
9 Aug 2026, 21:318,836+37
6 Aug 2026, 14:418,799+2
6 Aug 2026, 06:478,797first reading

Engagement

32 posts held, back to 5 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 30 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
29.8%
avg views ÷ 8,986 subscribers
Avg views / post
2,680
9 posts measured
Reaction rate
0.957%
reactions ÷ views · ER floor
Posts in window
9
of 32 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 28 August 2026
Posts held32 (5 June 202628 August 2026)
Views total24,130
Reactions total231
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken28 Aug 2026, 16:07 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

1,022 reactions across 29 posts, in 26 distinct kinds. The most used accounts for 21.7% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
🤡22221.7%
💩17216.8%
👎11010.8%
👍747.24%
😁716.95%
😱474.60%
🥰464.50%
🤬444.31%
🖕393.82%
363.52%
🤯262.54%
👏252.45%
😢232.25%
😭222.15%
😈201.96%
🤔141.37%
🔥100.978%
🤮50.489%
🎉30.294%
👀30.294%
6 further kinds100.978%

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 31 of the 32 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 1,094 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 32 most recent posts we hold, published 5 June 2026 to 28 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

28 Aug 2026, 04:45 UTC≈1,520 views36 reactionsread 28 August 2026

SourceHut 宣布禁止包含 LLM 生成内容的项目,包括代码/邮件/工单等。 - 此政策将于两周后的 9/10 生效;不合规的已有项目被要求迁走,但并无期限要求。 - 关于代码方面,政策只对最上游 repo 作出限制。包含 LLM 生成代码项目(例如 Linux kernel)的镜像/fork 则不在此限。 - 这个政策比 Codeberg 的 [thread] 更强:前者只限制主要由 LLM 生成的项目。 https://sourcehut.org/blog/2026-08-27-tos-changes-and-llms/ thread: /4888 #Sourcehut #Opensource #LLM

🤡28👏5🗿1🥱1🙏1

27 Aug 2026, 04:44 UTC≈1,550 views29 reactionsread 28 August 2026

nitter 项目宣布应 X (Twitter) 法律文书要求而暂停工作;官方实例已经停用。 nitter.net 称收到了来自 X Corp. 的 Cease & Desist 要求。 - https://nitter.net/ - techcrunch.com/~ linksrc: https://t.me/k3yt4x/1700 #Twitter #Nitter

😢23🤬3🫡3

27 Aug 2026, 02:44 UTC≈1,380 views19 reactionsread 28 August 2026

JPEG XL 将在 Firefox 和 Chrome 中被默认启用。 - 自 Firefox 157 [1] 和 Chrome 155 [2] 起将默认启用 JPEG XL 支持。Safari 现已默认启用支持。 - Chrome 在 2022 年曾移除 JPEG XL 支持。现在它又回来了。 1. groups.google.com/~ 2. groups.google.com/~ EDIT 8/27: 修正 Safari 支持状态;感谢一位订户纠正。 #JPEGXL

👍16👀3

25 Aug 2026, 03:45 UTC≈4,270 views23 reactionsread 28 August 2026

IPFS 的主要维护团队之一 Shipyard 将停止其工作;原因是 Protocol Labs 不再续期赞助。 - IPFS 是由 Protocol Labs 发布的去中心化文件共享协议。 - Shipyard 是 IPFS 的「独立」‌开发组织,此前一直由 Protocol Labs 赞助 [1]。也是 IPFS 项目目前的主要维护者。 ipshipyard.com/~ seealso: HackerNews:49421489 1. ipshipyard.com/~ #IPFS

😭22🤯1

23 Aug 2026, 02:45 UTC≈2,400 views24 reactionsread 28 August 2026

教育网联合镜像站发布;使用 MirrorZ 系统。 地址是 https://mirrors.cernet.edu.cn 。 linksrc: https://t.me/abcthoughts/7669 #OpenSource

🥰16😁5🎉2🤡1

21 Aug 2026, 02:45 UTC≈2,880 views29 reactionsread 28 August 2026

OpenRouter 宣布被 Stripe 收购。 OpenRouter 是 LLM 网关/路由服务提供商;Stripe 是支付服务提供商。 openrouter.ai/~ #OpenRouter #Stripe

👎21🤔7🥴1

20 Aug 2026, 12:33 UTC≈4,400 views32 reactionsread 28 August 2026

🔴 crates.io 发现恶意包 proc-macro1;arrayref 部分版本受影响。 - 受影响的包包括 [email protected][email protected][email protected]。 - 恶意包则是 proc-macro1, proc-macro-en, aovine, arone, aronenao 及 tinymember 的所有版本。 blog.rust-lang.org/~ #Rust #Ecosystem

😈20😱7😁5

20 Aug 2026, 02:45 UTC≈2,370 views13 reactionsread 28 August 2026

[旧闻] GitHub 发布 8/17 outage 的 postmortem;问题起源是 autoscaling 配置不当。 - 整体故障自 8/17 晚九时半起约持续八小时。 - VS Code 的重试逻辑问题导致 Copilot token 端点流量激增,使得端点恢复所需时间较久。 https://www.githubstatus.com/incidents/zkxwbgr0cnmx #Outage #GitHub

🤡11😁2

13 Aug 2026, 02:45 UTC≈3,360 views26 reactionsread 28 August 2026

Microsoft Entra ID 宣布自 2027/2/1 起停用短信/电话 2FA,并鼓励用户转而使用 Passkey。 - 9/1 起 Passkey 将为所有用户默认启用;用户在登录后会被提示为账户添加 Passkey。 - 依然需要短信/电话 2FA 的 tenant 可自 10/30 起自行选购第三方服务。 microsoft.com/~ #Microsoft #Passkey #Security

👍19🤡51😁1

12 Aug 2026, 02:45 UTC≈3,800 views19 reactionsread 28 August 2026

Nixpkgs 规模两人的 core team 解散;原因是工作量过大导致 burnout。 - 这并不代表 NixOS/Nixpkgs 项目结束运作! - 作者认为由少数受信任人士为社区做出决策效率更高。Steering Committee 的多数投票模式导致决策低效,甚至产生反效果。 https://discourse.nixos.org/t/-/79413 seealso: HackerNews:49217993 EDIT 8/12: 修正描述。 #NixOS

😁19

7 Aug 2026, 03:15 UTC≈7,090 viewsread 28 August 2026

🔴 Linux 内核 Open vSwitch 模块本地提权漏洞 OVSwrap。 - 在用户命名空间有 CAP_NET_ADMIN 权限的进程 (unshare -Urn) 即可以利用此漏洞提权。 - 大多主流发行版均受到影响。 - Mitigation 是禁用 openvswitch 模块或 unprivileged user namespace 。 - Kernel 上游和 Debian 各支持版本已经发布修复。 heyitsas.im/~ CVE: CVE-2026-64531 CVSS: 7.8 (kernel.org) Fixed-In: 5.15.212, 6.1.178, 6.6.145, 6.12.97, 6.18.40, 7.1.5 [感谢一位匿名订户提供信息。] EDIT 8/7: 修正对利用此漏洞条件的描述。 #OpenvSwitch #Kernel

7 Aug 2026, 02:45 UTC≈11,000 views7 reactionsread 28 August 2026

🔴 Linux 内核 sctp 模块本地提权漏洞 SCTPhantom。 - 腾讯朱雀实验室利用 AI 辅助发现了一个于 2008 年引入的 sctp 模块的漏洞。 - Kernel 上游和 Debian Trixie/Sid 已经发布修复版本。 CVE: CVE-2026-64564 CVSS: 8.5 (作者自评) Fixed-In: 6.6.148, 6.12.101, 6.18.42, 7.1.6, 7.2-rc5 matrix.tencent.com/~ [感谢一位匿名订户提供信息。] #SCTPhantom #Kernel

👏7

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

Posts edited after publishing

@outvivid edited 2 posts after it first published — the same permalink now carries different wording than the one this register originally read, caught because our own crawl held a copy of the earlier text.

An edit is not deception. Typo fixes, price updates and corrections look exactly like this too — this register can tell you the wording changed and when, not why. How this is measured.

First edit seen
22 August 2026
Most recent edit
28 August 2026

Forward network

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 2 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.

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.

Appears in Telegram’s recommendations for other channels

The reverse of the list above, and a different kind of signal. This does not require this channel to have ever been asked about directly — each row below is a channel we DID ask Telegram about, whose Telegram-generated list happened to include this one. A channel can appear here with an empty list above it, because being named by someone else’s query is independent of having been queried itself.

Iyouport
@iyouport · 27,857
Telegram ranks this channel #5 of 55 here — alongside 54 others — read 10 September 2026
Solidot
@solidot · 45,292
Telegram ranks this channel #5 of 59 here — alongside 58 others — read 28 August 2026
cnBeta.COM中文业界资讯站 - 总频道(精选新闻)
@cnbeta_com · 27,538
Telegram ranks this channel #8 of 55 here — alongside 54 others — read 10 September 2026
每日消费电子观察
@CE_Observe · 74,327
Telegram ranks this channel #8 of 62 here — alongside 61 others — read 19 August 2026
蓝点网订阅频道
@landiansub · 44,453
Telegram ranks this channel #9 of 58 here — alongside 57 others — read 28 August 2026
科技&趣闻&杂记
@kejiqu · 36,425
Telegram ranks this channel #11 of 48 here — alongside 47 others — read 1 September 2026
LoopDNS资讯播报
@DNSPODT · 71,577
Telegram ranks this channel #11 of 59 here — alongside 58 others — read 20 August 2026
风向旗参考快讯
@xhqcankao · 161,279
Telegram ranks this channel #11 of 45 here — alongside 44 others — read 12 August 2026
小声读书 🙈
@weekly_books · 38,114
Telegram ranks this channel #13 of 59 here — alongside 58 others — read 31 August 2026
APPDO 数字生活指南
@AppDoDo · 40,324
Telegram ranks this channel #15 of 57 here — alongside 56 others — read 30 August 2026
Newlearnerの自留地
@NewlearnerChannel · 67,141
Telegram ranks this channel #15 of 62 here — alongside 61 others — read 21 August 2026
VPS信号旗播报
@vps_xhq · 49,492
Telegram ranks this channel #16 of 57 here — alongside 56 others — read 26 August 2026
科技圈🎗在花频道📮
@zaihuapd · 281,658
Telegram ranks this channel #16 of 40 here — alongside 39 others — read 12 August 2026
赛博忏悔室
@cyber_confessional · 40,013
Telegram ranks this channel #17 of 35 here — alongside 34 others — read 30 August 2026
Shadowrocket News
@ShadowrocketNews · 46,595
Telegram ranks this channel #17 of 60 here — alongside 59 others — read 27 August 2026
黑洞资源笔记
@piracy6 · 77,239
Telegram ranks this channel #17 of 61 here — alongside 60 others — read 19 August 2026
Yummy 😋
@GodlyNews1 · 68,658
Telegram ranks this channel #20 of 55 here — alongside 54 others — read 20 August 2026
2019-nCoV疫情实时播报🅥
@nCoV2019 · 33,153
Telegram ranks this channel #22 of 59 here — alongside 58 others — read 4 September 2026
如何与沙雕相处
@ruheyushadiaoxiangchu · 28,845
Telegram ranks this channel #24 of 44 here — alongside 43 others — read 9 September 2026
平壤卫视
@pingrangTV · 29,111
Telegram ranks this channel #26 of 45 here — alongside 44 others — read 8 September 2026
树洞🌳群友问❓有点意思🗳
@qunyouwen · 89,534
Telegram ranks this channel #26 of 67 here — alongside 66 others — read 17 August 2026
飛蛾書庫
@MothLib · 34,553
Telegram ranks this channel #27 of 50 here — alongside 49 others — read 3 September 2026
竹新社
@tnews365 · 159,452
Telegram ranks this channel #28 of 59 here — alongside 58 others — read 12 August 2026
即刻精选
@jike_collection · 35,774
Telegram ranks this channel #31 of 48 here — alongside 47 others — read 2 September 2026

This channel appears in 39 seed channels' Telegram-generated recommendation lists in total, of which the 24 where it ranks highest are shown above. Each is Telegram’s list for THAT channel, not this one — see how this is measured.

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

“层叠 - The Cascading” (@outvivid), 8,986 subscribers as measured 7 September 2026. Telegram Register, tgregister.com/channel/outvivid.

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.