这软件还订阅制啊
😇5

Channel
@haruhi_channel
On this record: Topic · Growth · Engagement · Reactions · Posts · Cite this entry
699subscribers
+5 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001340985646 |
|---|---|
| Type | Channel |
| Username | @haruhi_channel |
| Created | 29 August 2020 — measured — cross-checked against a third-party dataset (ext.tg_channel) |
| First recorded | 7 August 2026 |
| Last confirmed live | 7 October 2026 |
| Measurements held | 7 |
| Confirmed unchanged | 1 time, most recently 7 October 2026 |
| On Telegram | t.me/haruhi_channel |
Other / unclassifiable — 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 20 September 2026 and assigned it the closest of 31 fixed categories, at 97% 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.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 7 Oct 2026, 11:37 | 699 | +3 |
| 26 Sept 2026, 15:59 | 696 | -1 |
| 13 Sept 2026, 03:57 | 697 | +5 |
| 21 Aug 2026, 15:49 | 692 | -1 |
| 14 Aug 2026, 14:48 | 693 | -1 |
| 7 Aug 2026, 05:01 | 694 | no change |
| 7 Aug 2026, 04:48 | 694 | first reading |
20 posts held, back to 4 November 2025 — 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 page of Telegram’s post history, 20 posts per page.
Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 20 posts for this entry, the most recent from 3 June 2026. An engagement rate over an empty window would be a number about nothing.
47 reactions across 10 posts, in 8 distinct kinds. The most used accounts for 38.3% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 😢 | 18 | 38.3% | |
| 🤯 | 6 | 12.8% | |
| 🥰 | 6 | 12.8% | |
| ❤ | 5 | 10.6% | |
| 😇 | 5 | 10.6% | |
| 👍 | 3 | 6.38% | |
| 🤔 | 3 | 6.38% | |
| 😱 | 1 | 2.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 11 of the 20 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 47 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 20 most recent posts we hold, published 4 November 2025 to 3 June 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.
这软件还订阅制啊
😇5
感觉真 substances usage 活不了这么久
https://x.com/i/status/2059326970224382217
❤2
在 Codex 的帮助下又斗老黄!现在 5090 除了 P2P,也有 GPUDirect RDMA 用了,32 卡 allreduce 性能从 8GB/s 上升到了 20GB/s。 最终修改只是 libcuda.so 中的一个字节,等有空让大模型给我写篇博客,讲一讲如何对付刀法。 更新:博客初稿已完成 https://harrychen.xyz/2026/05/20/enable-gpudirect-rdma-on-rtx-5090/
一个写得还挺好的带background介绍的writeup:https://mp.weixin.qq.com/s/Pwm7sJ12K20FKbzxzFELkw 原writeup: https://xint.io/blog/copy-fail-linux-distributions
👍3
https://cloud.google.com/blog/products/identity-security/introducing-google-cloud-fraud-defense-the-next-evolution-of-recaptcha/
什么时候给 AI Agent 也发一个 Root of Trust
要求使用大厂商的设备才能运行 Trusted AI
🤔3
还是太ctf了
😢8
https://x.com/i/status/2024469696423026816 这么多好用的?
😢10❤2
fish v4 改了 Alt/Ctrl + Backspace/Left/Right 的行为,参照 https://github.com/fish-shell/fish-shell/issues/10926 改回来即可,不过原文中的 Ctrl/Alt 和我的习惯是反着的
绕过方法也比较简单,kernel 修改浮点寄存器 undo 掉对 kernel 的修改,然后从 EL3 回来后再 redo
❤1
Showing the 12 most recent of 20 posts we hold for @haruhi_channel. 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.
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 October 2026 — this entry's latest reading, not the date you are reading this.
“Haruhi的日常” (@haruhi_channel), 699 subscribers as measured 7 October 2026. Telegram Register, tgregister.com/channel/haruhi_channel.
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.