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

Channel
@outvivid
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Telegram's recommendations · Cite this entry
8,844subscribers
+47 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
| Telegram ID | -1001378594303 |
|---|---|
| Type | Channel |
| Username | @outvivid |
| Description | 主要话题大概是开源业界新闻。 所有以 #today 标签的内容均为本台编辑的个人意见,可能可以代表本台观点。 在 Fediverse 关注我们: https://misskey.io/@cascading 在 Bluesky 关注我们: https://bsky.app/profile/thecascading.bsky.social 反馈/建议/吐槽:请使用 Direct Messages 吹水群: https://t.me/+VaUZgXjPSOI2NDAx |
| Created | 19 February 2018 — measured — cross-checked against a third-party dataset (TGDataset) |
| First recorded | 6 August 2026 |
| Last confirmed live | 12 August 2026 |
| Measurements held | 4 |
| Confirmed unchanged | 1 time, most recently 12 August 2026 |
| On Telegram | t.me/outvivid |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 12 Aug 2026, 12:38 | 8,844 | +8 |
| 9 Aug 2026, 21:31 | 8,836 | +37 |
| 6 Aug 2026, 14:41 | 8,799 | +2 |
| 6 Aug 2026, 06:47 | 8,797 | first reading |
23 posts held, back to 5 June 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 14 pagesof 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. It is computed over the 13 of 14 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 12 August 2026 |
|---|---|
| Posts held | 23 (5 June 2026 – 12 August 2026) |
| Views total | 48,510 |
| Reactions total | 464 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 12 Aug 2026, 15:52 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.
Lifetime counters from Telegram’s own channel header, read 12 August 2026 — not the date at the top of this page, which is when the subscriber count was last read. A count marked ≈ was rounded by Telegram before we ever saw it — t.me prints these counters in full below 1,000 and to three significant figures above, so ≈142,000 means somewhere between 141,500 and 142,499.
769 reactions across 20 posts, in 18 distinct kinds. The most used accounts for 22.4% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 💩 | 172 | 22.4% | |
| 🤡 | 172 | 22.4% | |
| 👎 | 88 | 11.4% | |
| 😁 | 51 | 6.63% | |
| 🤬 | 41 | 5.33% | |
| 😱 | 40 | 5.20% | |
| 🖕 | 39 | 5.07% | |
| ❤ | 34 | 4.42% | |
| 👍 | 34 | 4.42% | |
| 🥰 | 30 | 3.90% | |
| 🤯 | 25 | 3.25% | |
| 👏 | 18 | 2.34% | |
| 🔥 | 9 | 1.17% | |
| 🤔 | 7 | 0.91% | |
| 🤮 | 5 | 0.65% | |
| 🥱 | 2 | 0.26% | |
| 🎉 | 1 | 0.13% | |
| 😍 | 1 | 0.13% |
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 22 of the 23 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 841reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 23 most recent posts we hold, published 5 June 2026 to 12 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.
Nixpkgs 规模两人的 core team 解散;原因是工作量过大导致 burnout。 - 这并不代表 NixOS/Nixpkgs 项目结束运作! - 作者认为由少数受信任人士为社区做出决策效率更高。Steering Committee 的多数投票模式导致决策低效,甚至产生反效果。 https://discourse.nixos.org/t/-/79413 seealso: HackerNews:49217993 EDIT 8/12: 修正描述。 #NixOS
😁15
🔴 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
🔴 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
Jeff Dean 离开 Google 创立新公司 Discovery Loop AI。 Jeff Dean 在 Google 供职 27 年,据称是 Google 的第 30 名雇员。 twitter.com/JeffDean/~ #JeffDean #Google
👏9
Telegram 目前被从 App Store 下架。 - 现有安装似乎不受影响;Play Store 上的 Telegram 目前尚可搜索到。 EDIT 8/4: 似乎已恢复。 #Telegram #AppStore
🤯20🥰4❤3😁3🎉1
数个虚假的 SQLite 漏洞报告被分配 CVE 编号。 - JFrog 团队发现, GitHub repo programmervuln/cveadvisory- 中发布了大量的漏洞报告,绝大多数为 AI 生成的错误内容。 - MITRE 在未对其进行验证的情况下就为这些虚假漏洞报告分配了 CVE 编号;目前编号已被撤回。 https://research.jfrog.com/post/sqlite-critical-cves-or-llm-slops/ #SQLite #CVE
🤡30😁1
OpenAI 及 Anthropic 发公开信呼吁美国政府推动措施控制 AI 发展速度。 公开信中提到,AI 发展速度越来越快且过于强大;社会需要时间来为 AI 带来的潜在威胁做准备。 https://pacingthefrontier.com/ #OpenAI #Anthropic
🤡57😁12👍4👎3🖕2
Anthropic 发文回应开放权重模型公开信,再次强调中国威胁论。 - 上周,一篇发布在微软网站上的公开信呼吁美国政府支持开放权重模型 [1]。 - 除 Anthropic 外的超过 130 家科技公司,包括英伟达、谷歌、Meta、英格尔、Amazon 等,均参与了此公开信的联署。 - 和以往一样,Anthropic 的回应中表达了对开放权重模型安全性的担忧,以及对中国共产党利用或蒸馏强大 AI 模型以达成威权政府目的的担忧。 anthropic.com/~ 1. microsoft.com/~ #Anthropic #LLM
🤡81😁18🖕10👍6👎3
《千恋*万花》宣布动画化。2027 年上映。 twitter.com/yuzusoft/~ linksrc: https://t.me/rynif/41055 #YuzuSoft
🥰26😍1
Codeberg 更新条款,禁止加密货币项目和主要由 LLM 生成的项目。 - 条款中提到的理由是加密项目损害 Codeberg 声誉,而 LLM 生成项目存在版权风险。 - 博客文章中另有展开描述,提到不希望 Codeberg 成为存放 LLM 生成的一次性代码的填埋场。 [1] codeberg.org/~ 1. blog.codeberg.org/~ #Codeberg #Opensource
👎45👍21❤3🤯2🔥1
🔴 WordPress RCE;请尽快更新。 - SQL 注入漏洞影响 6.8 及以后版本;RCE 漏洞影响 6.9 及以后版本。 - Cloudflare WAF 已部署 mitigation。 [1] CVE: CVE-2026-63030, CVE-2026-60137 (WPScan) CVSS: 9.8, 5.9 Fixed-In: 6.8.6, 6.9.5, 7.0.2, 7.1.beta2 wordpress.org/~ 1. blog.cloudflare.com/~ linksrc: https://t.me/MiaoTonyChannel/21604 #WordPress
😱7
domain .ME 解释:一个 Telegram 频道被美国制裁导致 t.me 域名被停止解析。 - .me 是欧洲国家黑山的国别域名 (ccTLD)。 - domain .ME 是 .me 域名的注册局。 twitter.com/domainME/~ thread: /4884 #Telegram #TLD #US
👎21🖕5
Showing the 12 most recent of 23 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.
Citation-graph rank — 36,315 of 1,160,990entries 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.
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.
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.
Named by
Channels on the register whose posts name this channel's handle.
Names
Channels on the register whose handles appear in this channel's posts.
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.
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.
This channel appears in 3 seed channels' Telegram-generated recommendation lists in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.
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 12 August 2026 — this entry's latest reading, not the date you are reading this.
“层叠 - The Cascading” (@outvivid), 8,844 subscribers as measured 12 August 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.