原来芯片上有元数据记载它刻在晶圆哪里,而且有固件能读
😭1
Channel
@streams1024
On this record: Growth · Engagement · Reactions · Posts · Citations · Cite this entry
618subscribers
+3 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001330846827 |
|---|---|
| Type | Channel |
| Username | @streams1024 |
| Created | 7 July 2019 — measured — cross-checked against a third-party dataset (TGDataset) |
| First recorded | 6 August 2026 |
| Last confirmed live | 15 August 2026 |
| Measurements held | 4 |
| Confirmed unchanged | 1 time, most recently 15 August 2026 |
| On Telegram | t.me/streams1024 |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 15 Aug 2026, 20:04 | 618 | +2 |
| 7 Aug 2026, 12:44 | 616 | +1 |
| 6 Aug 2026, 17:46 | 615 | no change |
| 6 Aug 2026, 12:43 | 615 | first reading |
18 posts held, back to 13 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 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. It is computed over the 2 of 6 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 4 August 2026 |
|---|---|
| Posts held | 18 (13 June 2026 – 4 August 2026) |
| Views total | 1,952 |
| Reactions total | 1 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 6 Aug 2026, 17:46 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.
46 reactions across 10 posts, in 12 distinct kinds. The most used accounts for 28.3% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 👍 | 13 | 28.3% | |
| 😱 | 5 | 10.9% | |
| 🥰 | 5 | 10.9% | |
| 🌚 | 4 | 8.70% | |
| 💩 | 4 | 8.70% | |
| 😴 | 4 | 8.70% | |
| 🔥 | 3 | 6.52% | |
| ❤ | 2 | 4.35% | |
| 👎 | 2 | 4.35% | |
| 🥴 | 2 | 4.35% | |
| 🍾 | 1 | 2.17% | |
| 😭 | 1 | 2.17% |
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 11 of the 18 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 46reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 18 most recent posts we hold, published 13 June 2026 to 4 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.
原来芯片上有元数据记载它刻在晶圆哪里,而且有固件能读
😭1
讲个笑话,一个设计公司 正文字体产品中,有 2/3 是大量借鉴且仅借鉴欧洲作品 网站字体是欧洲人做的 客户都是欧洲的 公司名叫 U.S. Graphics Company
https://usgraphics.com/products 这位的最新最热 Los Alamos 不是 OCR-B 重制吗?打开你的护照看看 MRZ,不能说很像,只能说完全一样。而且 OCR-B 是一款欧洲字体,这位的宣传方式可能不妥。
https://www.omg.org/about/staff.htm 谁能告诉我这个出 UML 标准的组织的生态位是什么
如果你说某些语言的键盘没有 AltGr,那我觉得这些机械键盘脑残粉也没必要花巨大成本把每一个按键做成可独立更换,全部按键一起换的量产键盘就是他们想要的。
现在这些设计键盘的,脑子里进什么了? 本来上档字符放上边,有些厂上档字符偏偏放右边,那我请问 AltGr 档的字是不是就要放下边?没事把上下左右的传统改掉有意义吗?你会毫无理由把交通规则改成靠左行吗? 还有按键刻字横向居中导致的不对齐。这显然是不会 typography 的结果。并且因为 AltGr 档的存在,大量刻字本来就不应该是居中的。 更别说不成套的字体和对不齐的基线了。
公元 2026 年,武陵有个低代码架构师以调包为业。某日沿着微服务拓扑巡查,忽然忘记了调用栈的深度。继续往前,突然遇到一片原生手写 C 语言森林,夹岸数百行,没有多余的冗余冗长,零外部依赖,函数纯粹。架构师十分诧异,继续往前走,想看看这片手工智慧的尽头。 逻辑流尽头,抽象语法树汇聚成一处汇编引导文件。文件里竟然有个内联硬编码,初极狭,才通人。再走几十步,豁然开朗。只见土地平旷,屋舍俨然,有内核裁剪精简之属。接口解耦,解包相闻。其中往来种作,男女衣着,悉如外人。汇编长者、极客少年,并怡然自乐。 看见架构师,大为吃惊,问从哪里来的。架构师一一回答。于是邀请他到家中,摆出交叉编译器,跑 benchmark 调优来款待。村中人听说来了这么个人,都来打听消息。他们自己说,祖先是为了躲避互联网降本增效,带领妻子儿女和同乡来到这个与世隔绝的地方,不再出去,于是就与外面的人断绝了来往。 问现在外面技术栈迭代如何,竟然不知道有 Cursor,更不…
😴4🥰1
如果你做计算机学术,请 不要在学术代码上做工程了! 我不需要你的主程序帮我从某个地方找数据集、跑完实验又存到某个你拼出来的路径。你的数据集应该是 stdin,你的计算结果应该是 stdout,你的日志应该是 stderr! 因为你的数据集 DSL 有 bug! 因为你的代码有 bug,每 30 条甚至 29 条数据都会自己炸掉,我不应该为此去碰你的数据集 DSL!我应该用 tail -n +31 或 jq '.[30:]' 从坏掉的地方继续! 因为我的 GPU 是限时的,所以一定需要中断并继续跑!你的 GPU 不限时那你很有钱哦。 因为你拼出来的输出路径有 bug! 因为你的 evaluation 代码的输入路径还是有 bug! 我不需要你到处 try catch!真正的错误被藏起来了,给我看到的都是些无意义的 null pointer exception!我需要准确认识你的程序的所有错误模式! 重试网络请求的正确做法是不处理 …
👍9
为什么欧洲这么热没有强对流天气?
🥴2
鉴于当前软件安全漏洞问题的严重性,我建议开发非线性操作系统
❤1
连我这个 58°N 的温带海洋性地区都达到了 30°C 的气温!
🔥3🍾1
https://www.thepaper.cn/newsDetail_forward_33459417 日常使用中很多用户都有这样的习惯,那就是为了防止系统卡顿,特意将大型软件安装在D盘或E盘。 然而,WPS却玩起了“明修栈道,暗度陈仓”。软件本体在D盘,几十个G的缓存和云备份文件却默认写入C盘系统目录。 什么时候普通用户不在同一块硬盘上分多个 NTFS 区,中国就实现现代化了
👍4🥰4👎2
Showing the 12 most recent of 18 posts we hold for @streams1024. 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.
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.
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 15 August 2026 — this entry's latest reading, not the date you are reading this.
“Streams 1024” (@streams1024), 618 subscribers as measured 15 August 2026. Telegram Register, tgregister.com/channel/streams1024.
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.