Channel
@dsuse
On this record: Growth · Engagement · What this channel posts · Posts · Citations · Cite this entry
840subscribers
+0 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001145096067 |
|---|---|
| Type | Channel |
| Username | @dsuse |
| Description | import this: 美而不丑、明而不暗、短而不凡、长而不乱，扁平不宽，读而后码，行之天下，勿托地上天国。 异常勿吞，难过勿过，叹一真理。效率是很重要，盲目最是低效。 简明是可靠的先验，不是可靠的祭品。 知其变，守其恒，为天下式；穷其变，知不穷，得地上势。知变守恒却穷变知新，我认真理，我不认真。 技术相干订阅~ 另外有 throws 闲杂频道 @dsuset 转载频道 @dsusep 极小可能会有批评zf的消息 如有不适可退出 suse小站(面向运气编程)： a19a0b |
| Created | 22 June 2017 — measured — cross-checked against a third-party dataset (TGDataset) |
| First recorded | 6 August 2026 |
| Last confirmed live | 6 August 2026 |
| Measurements held | 2 |
| On Telegram | t.me/dsuse |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 6 Aug 2026, 15:04 | 840 | no change |
| 6 Aug 2026, 04:15 | 840 | first reading |
10 posts held, back to 24 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 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.
| Window | Rolling 30 days · latest post in window 5 August 2026 |
|---|---|
| Posts held | 10 (24 July 2026 – 5 August 2026) |
| Views total | 815 |
| Reactions total | — |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 6 Aug 2026, 15:04 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 6 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.
📢 FFmpeg 更新 — 9.0 版本代号为 "Lei"，纪念已故中国开发者@雷霄骅 🆕 核心更新： • 新增 Animated WebP 解码器与解封装器，支持动态 WebP 直接解码 • GPU 滤镜扩展：v360_vulkan（全景投影）、transpose_cuda（旋转）、AMF 帧率转换器与 HDR 色彩转换增强 • 硬件加速新增 ProRes RAW VideoToolbox 与 APV Vulkan hwaccel • ONNX Runtime DNN 后端支持 GPU 执行提供程序；新增 Dolby Vision 多层 HEVC 拆分 bitstream filter • HE-AAC 960 采样解码（DAB+ 数字广播）；SMPTE 2094-50 HDR 元数据透传 • 移除独立 CELT 解码与 ogg/celt 解析支持（Opus 内嵌 CELT 不受影响） • 移除已废弃的 NVENC 选项…
https://fxtwitter.com/isukkaw/status/2081101404865970280
没有应用层的【系统编程技术】是残缺的。 用到了多少，就有可能做多丰富的ABI PC和网页没有电池和后台限制，做不了Web推送，Native没有“流畅度需求”，被各种驱动的ABI绑架，它不理解async。 Native不可能做到pyjs和WASM那样神乎其技的import，GL不如ShaderToy和Taichi物理模拟懂GL，不可被观测的技术是债务不是资产。
#os C技术栈的技术债务 🥱 #ai探讨 https://chat.librechat.ai/share/0ZFV5Yya3BriBIdDmFC9x
印度政府命令 GitHub 移除 Jack Dorsey 的蓝牙聊天应用 Bitchat 2026-07-24 23:46 by 完美女孩 印度政府的网络犯罪协调中心命令 GitHub 移除 Jack Dorsey 的去中心化蓝牙聊天应用 Bitchat。前 Twitter CEO Dorsey 在 X/Twitter 上公布了收到的通知，通知的日期是 7 月 23 日，声称该应用能在网络受限的情况下进行通信，能被反国家分子、恐怖组织、有组织犯罪集团和网络犯罪分子滥用，他们试图逃避合法监测，继续在法律限制下进行通信。印度最近爆发了被称为“蟑螂人民党（Cockroach Janta Party)”的抗议活动。 https://www.thehindu.com/news/national/government-orders-github-to-remove-bluetooth-based-chat-app-bitchat-ov…
#math 还真是，充分必要王后🌚 ps.菲尔兹奖得主在发言
当然了，我简化了 accept() vs accept(then) 的问题，前者传入了自身pid（或者说整个ret2stack），后者另外传入了一个“代码和数据”双指针。 内核权限对后者是无能为力的，因为一个进程不能长两个头。 这个问题，真正是我说的“用非常愚蠢的方法实现闭包”：把 一个纯粹的token鉴权，和栈(pid)绑死在一起，所以有了各种语言的await。 这是养鸡场只有一个谷堆，一群鸡随机插着队来消化，但谷堆（网卡）本身是事件性的！😂 鸡确实没有两个头，但把进程视为单线的、有栈顶的，这种说法本身是错误的。并没有确定的执行顶部，只是一堆信号变量间的因果链！ 😅因为OOP封装和“阅后即焚”式计算太流行了，好像必须要有个栈vs堆一样。其实栈分配只是个内联优化，泄露进了认知里，还成教科书了。 不会真以为栈变量就能阅后即焚吧？ 这就好像某人发现了【文件名不占空间，可以拿来做压缩】，或觉得伪递归(continue fn(x…
#os #post libc不懂线程模型 一个默认不是EPOLLEXCLUSIVE的libc，和天生除了 onclick=()=>{if...; return true} 还支持capture和scroll特例优化的js，真不知道C设计时脑子在干什么。默认广播？广播什么？ C工具链的一切都是进程的尸体，和代码本身并无关系，也和作者的心流意图相去甚远。这不是性能的问题，纯粹是不会读空气充满跑通次抛的气质，否则下游为什么都在改、加框架才能脱离玩具。 能跑和【能活】是两码事，能绿就小心了。 C文件完全没有被调试的价值，它的typing就像它的隐转一样在静态语言里出戏，就连WASM也不咋样。 用C却从未自带“人肉编译器”的编程者是libc生态的受害者，而只为调几个API和“编译器隐藏大招”教人C开发应被视为某种犯罪，这是在传播思想残疾了。 整个污染性的await的编程世界，都是4K内存页和奇葩调度器搞的鬼。本来是串读串写的（…
#os 现在的人，真是CPU主循环（procfs粒度的）和GC（4K粒度的粗分配）都要手写(scx_wtf, jemalloc)，然而真能出可见效果的，寥寥无几。还不如直接改sw.js来的省电。 🤓
#ai速答 #os #post Linux引导链、二进制 https://chat.librechat.ai/share/NH_o6nWE2OeF0nGOLXoaG Grub 现在还流行吗？确实老牌都还在用，但现在运维都用网页panel了…… sd-boot很快阿 Limine和rEFInd对比呢？后者是带界面的，类似Ventoy UKI不就是一个elf加cpio么。。 确实，但可以给cmdline签名 PE相比elf有什么好处，作为EFI的捆绑？ 图标协议？ 就不能在elf里塞一个000权限的zip字节当静态资源？打开argv[0]就能当文件夹用 强行默认sec名，或者自动扫描有没有fat节不就行了。 再加个第三方可挂载可修改 不比usr分发强？ - 我的意思不是配置状态自包含，是纯粹资源文件的 - 还是不如smalltalk的概念，图标直接在镜像里，不需要命名，打开页面就能知道用了什么资源 - 没错，h5和相似…
Showing the 10 most recent of 10 posts we hold for @dsuse. 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 — 851,324 of 1,169,250entries 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 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.
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.
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.
“duangsuse::Echo” (@dsuse), 840 subscribers as measured 6 August 2026. Telegram Register, tgregister.com/channel/dsuse.
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.