Telegram RegisterThe public register of Telegram
Telegram profile photo for VHKD 字说字话

Channel

VHKD 字说字话

@vhkdzszh

On this record: Topic · Growth · Engagement · Reactions · Posts · Cite this entry

16subscribers

+8 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1003429133689
TypeChannel
Username@vhkdzszh
CreatedBetween 1 November 2025 and 31 March 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded12 August 2026
Last confirmed live3 October 2026
Measurements held6
Confirmed unchanged1 time, most recently 3 October 2026
On Telegramt.me/vhkdzszh

Topic

Politics & activism — 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 1 October 2026 and assigned it the closest of 31 fixed categories, at 90% 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.

Growth

816127 August 2026 — 8 subscribers12 August 2026 — 8 subscribers23 August 2026 — 10 subscribers30 August 2026 — 11 subscribers9 September 2026 — 15 subscribers3 October 2026 — 16 subscribers7 August 20263 October 2026
6 measurements spanning 56 days, net +8. 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 7–17 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
3 Oct 2026, 01:4116+1
9 Sept 2026, 06:3815+4
30 Aug 2026, 09:3311+1
23 Aug 2026, 15:1410+2
12 Aug 2026, 15:168no change
7 Aug 2026, 19:068first reading

Engagement

16 posts held, back to 5 August 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 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 16 posts for this entry, the most recent from 10 August 2026. An engagement rate over an empty window would be a number about nothing.

Reaction mix

4 reactions across 2 posts, in 1 kind.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
❤4100.0%

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 3 of the 16 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 4 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 16 most recent posts we hold, published 5 August 2026 to 10 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

10 Aug 2026, 13:09 UTC15 views2 reactionsread 12 August 2026

原谅我用第二人称,没有冒犯各位的意思,只是想表达一种情绪。 你觉得他烂透了,他觉得你以及这个世界烂透了。你们站在了不同的立场上,所谓屁股决定脑袋。你没有权利对他提出法律及公序良俗外更多的要求,但他可以指责你的过错。因为当你提要求的时候本质上是在行使一种由身份、职位等带给你的公权力,那不是你作为一个普通个体本就拥有的权利,因此你只能在特定的范畴内行使。任何越界的行为,他都没有义务执行。如果你试图以这种上位者的身份强行施压以及实行不公的待遇,那么你是垃圾。 各位领导,当你们要求员工无偿加班的时候,你们就是垃圾。别总拿体制和社会说事,你们就是组成这些个体制和社会的一员。少了你们的“助力”,这个体制不会崩坏,这个社会也不会运转不下去。什么?你说你是为了保住自己作为领导的更多的利益?所以就可以压榨员工了是吗?那么你是垃圾中的垃圾。 或者你想把话说得漂亮一点:是为了大家共同的利益。那么请你扪心自问,大家最终得到这些共同利益了嘛?和付出的…

❤2

9 Aug 2026, 14:41 UTC14 viewsread 12 August 2026

又部署了 deepseek-v4-flash-abliterated-q2 做了一些不能说出来的事情。梁的伟大无需多言,dsv4 flash真正让我看到了本地模型的价值。之前部署的那些什么 qwen 27b, 35b A3b 一度让我觉得本地模型很鸡肋。

9 Aug 2026, 09:23 UTC14 views0 reactionsread 12 August 2026
Photo

害怕,现在一下子成了全市场最耀眼的了,未必是好事啊,闷声发大财的机会没有了。周末药明的讨论热度爆了,必定会涌进来大量散户,短期股价可能会继续抬升,但主力也可能会借机收割一波。看讨论有人说周一跌停的,有人说周一涨停的,意见分化这么严重你就知道怎么回事了。历史总是一遍遍的重演,散户在无限放大这支票的风险,让人想不杀杀热度都难,而散户就是在一次次追热点过程中亏钱的。

8 Aug 2026, 10:40 UTC12 viewsread 12 August 2026
Photo

好便宜,十次卡,冲了。要是常呆长沙就季卡了,太划算了。

7 Aug 2026, 05:23 UTC10 viewsread 12 August 2026

CRO已疯。有上半年存储芯片那味了。几年疫情及后面几年医药股被毒打的日子依旧印象深刻,现在仿佛都过去了。

7 Aug 2026, 05:00 UTC10 viewsread 12 August 2026

果然不用AI的时候,中午的时间都慢了下来。

7 Aug 2026, 02:17 UTC10 viewsread 12 August 2026

药明康德真是好公司啊。与其学一堆技术,不如选一个好公司。谨记祖师爷的话。

6 Aug 2026, 14:03 UTC9 viewsread 12 August 2026
Photo

DeepSeek V4 Flash 本地量化对比:IQ3_XXS 与 Q2_K_XL 还行?

6 Aug 2026, 07:44 UTC14 viewsread 12 August 2026
Photo

用这些题目考验 deepseek v4 flash 会不会太为难它了。。不过我挺期待测试结果的,虽然预估不会太好,但是不知道有没有惊喜。

Signed geekinney

6 Aug 2026, 04:19 UTC10 viewsread 12 August 2026
Photo

这种时候就体现出 dgx spark 的优势了,虽然咱内存带宽没那么高,但是内存大呀,可以玩玩 deepseek v4 flash 量化模型。 在部署和测评 unsloth/DeepSeek-V4-Flash-0731-GGUF 的 UD-Q2_K_XL 和 UD-IQ3_XXS 量化模型的能力差异。目前低精度的 UD-IQ2_M 版本的已经跑起来了,131K 上下文,让 gpt 设计了问题简单测试了下还不错。前面两个更高精度的模型后续会做更详细的 AB 测评,然后决定日常如何使用。官方说 v4 flash 正式版主要优化了 agent 能力,我体验了一会儿,工具调用挺稳的(没有出现莫名其妙的问题),日常使用估计不成问题。

Signed geekinney

5 Aug 2026, 12:38 UTC40 views2 reactionsread 12 August 2026

omx 给了我一个启发:可以根据任务难度让 gpt 5.6 的模型互相调用。刚刚在用 luna max 修一个 bug,我发现它反复搞了几次都没解决,就说 “搞不定的话就用 sol xhigh 来做”,然后它应该是起了一个子进程调用 sol xhigh 一下子就解决了。这种操作实际是一种人工路由,以 luna max 作为模型调度器,然后根据实时的执行情况升级到更强的模型,不用停下来切换模型和推理级别。这种基于人工判断的执行方式可以更精细化的使用模型,兼顾执行速度和解决问题的难度,应该也是很省 token 的方式。

❤2

Signed geekinney

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

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

“VHKD 字说字话” (@vhkdzszh), 16 subscribers as measured 3 October 2026. Telegram Register, tgregister.com/channel/vhkdzszh.

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.