Telegram RegisterThe public register of Telegram
Telegram profile photo for 搞机日记

Channel

搞机日记

@gaojiriji

On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry

5,084subscribers

-2 since we began measuring on 6 August 2026

Risers and fallers across the register · movement among entries of 3,162–10,000.

Register entry

Telegram ID-1001293289931
TypeChannel
Username@gaojiriji
Created24 March 2018measured — cross-checked against a third-party dataset (TGDataset)
First recorded6 August 2026
Last confirmed live12 August 2026
Measurements held5
Confirmed unchanged1 time, most recently 12 August 2026
On Telegramt.me/gaojiriji

Growth

5,0845,0875,085.56 August 2026 — 5,086 subscribers6 August 2026 — 5,086 subscribers7 August 2026 — 5,087 subscribers9 August 2026 — 5,086 subscribers12 August 2026 — 5,084 subscribers6 August 202612 August 2026
5 measurements spanning 7 days, net -2. 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 5,084–5,087 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
12 Aug 2026, 23:335,084-2
9 Aug 2026, 19:015,086-1
7 Aug 2026, 04:025,087+1
6 Aug 2026, 04:165,086no change
6 Aug 2026, 04:085,086first reading

Engagement

17 posts held, back to 21 March 2026the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 8 pagesof Telegram’s post history, 20 posts per page.

ERR · 30 days
40.0%
avg views ÷ 5,084 subscribers
Avg views / post
2,030
5 posts measured
Reaction rate
0.451%
reactions ÷ views · ER floor
Posts in window
5
of 17 held

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 4 of 5 measured posts that carry a reaction reading, and over those same posts' views.

What these figures were computed from
WindowRolling 30 days · latest post in window 11 August 2026
Posts held17 (21 March 202611 August 2026)
Views total10,157
Reactions total42
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken12 Aug 2026, 04:49 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.

What this channel posts

Video runtime
7s
Average length
7s

Measured directly from 1 video with a duration reading, out of the posts we hold for this channel — not this channel’s whole posting history, only the sample this register has actually read. An exact reading to the second, taken from the post itself rather than from Telegram’s own rounded chrome, so it carries no mark.

Reaction mix

133 reactions across 11 posts, in 12 distinct kinds. The most used accounts for 43.6% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
😁5843.6%
👍3324.8%
2418.0%
😇64.51%
🕊32.26%
👏21.50%
🤷‍♂21.50%
🐳10.752%
👻10.752%
💩10.752%
🗿10.752%
🤗10.752%

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

Measured over the 17 most recent posts we hold, published 21 March 2026 to 11 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, 23:26 UTC852 viewsread 12 August 2026

beta 5 拓展了液态玻璃两端的极限,修复了最透明玻璃下的超明显锯齿问题。不过应该也因设备而异。

31 Jul 2026, 04:30 UTC≈3,090 views31 reactionsread 12 August 2026

今天又被某些国产模型浇了冷水。在一个国产在线文档产品里面对AI说了一句「去掉所有多余空行」,这个模型居然用英文思考了三分钟又用中文思考了很久,久到我发完这条都没思考完,还多次调用mcp,依然没有搞定。所有思考的过程基本就是 ummm wait unless but wait but wait wait so wait final final 无限纠结,不敢反驳用户「我没看到多余空行啊」显得自己很蠢,陷入了无尽的循环…… 是模型智能太低又把思考拉满的结果吗?先去吃个饭,回来看看它到底能纠结多久。地球母亲啊,原谅我,泡面不等人。 update:吃完饭了,没有检测出空行。

😁28🕊3

30 Jul 2026, 02:49 UTC≈1,940 views6 reactionsread 12 August 2026
Photo

之前碰到有个神秘问题:每一次重启后,我的 Jump Desktop Connect 就会卡在初始化动不了,一开始我以为是软件的bug或者是 macOS 27 beta 的bug,但是重新安装后并没有解决,所以我让 DeepSeek V4 Flash/ Big Pickle去解决这个问题。 这些小模型的回复是,软件的 launch 进程失败了,所以帮我写了一个 plist,我一看真启动成功了,真棒!但是我第二次重启发现问题依然在。这次我找了 GPT terra high,它先拟了三个请求去互联网上查询类似的问题,最后给了我这样的回答。 我很意外。我确实记得因为没认出 PhaseFive Systems 是哪个软件从而关掉了它的后台运行权限……去设置里开了就好了。 PS:最近 all in GPT,terra就很棒了,是几百K token 就能帮我搞定日常小问题还是一次过的了。而且 5.6 给我感觉在 work/codex 里

4👍2

21 Jul 2026, 02:57 UTC≈3,380 views2 reactionsread 12 August 2026

受这件事情,最近一个月喜欢用小模型干活,V4 Flash类型的那种,什么国产模型匿名模型都在用。只有复杂的嵌套任务才会用 GLM 5.2( K3 出来后GLM都显得慢了)。 比较有意思,我发现小模型在目前普遍的harness下基本都能乖乖老实干活,只是偶尔会犯蠢——不知道怎么做傻在原地思考打转、自作主张用自己的方法尝试忽略原文档等等。这时候只要插嘴一句就能让它继续做下去。这已经不是实习生了,更像是班主任去差使高中生干杂活。 我觉得大部分人想让模型完成的就是这些脏活累活。如果这个提点的动作不是人来完成,而是让更聪明、更大参数量的模型来扮演班主任,会更加无感。

👍2

14 Jul 2026, 08:16 UTC≈2,970 viewsread 12 August 2026
Photo

跟前几年的情况类似,beta 1 像一个分支的产物,打个样给WWDC后的营销用。后面的 beta 2 和 3 像是另一个分支的东西,汉化都统统还回去了,根据WWDC后的用户反馈重新开发?做到差不多 beta 1 的稳定性后就推送个公测版。 后面 beta 4 beta 5 可能才会稍微更稳定一些。 怀念 nugget,如果想升级 iOS 27 测试版的话,记得在 iOS 26 上用 nugget 干掉遥测再上,iOS 27 测试版目前暂不支持用 nugget了。

11 Jul 2026, 06:15 UTC≈3,090 viewsread 12 August 2026

https://fixupx.com/sunnny1583/status/2075796043195994317 iOS 27 到 beta 3 一直在微调液态玻璃滑块,现在回到了类似 beta 1 的状态,最透明的情况下文字和图标边缘会产生明显的锯齿很不美观;而且可读性差劲。 PS:我觉得默认一档的液态玻璃是最漂亮的。现在还解决了液态玻璃动画连续性的问题(比如音乐app中缩放播放界面最后一帧)。 喜欢透明质感的话还是需要往回拉一点加点模糊。 目前还是不建议升级 beta,一想到还有两个月的bug要品尝😑每天跑几十M的log。

25 Jun 2026, 04:16 UTC≈3,250 views15 reactionsread 12 August 2026
Photo

某些大模型现状:纯烧token,不产出。地球母亲何时惩罚?

😁15

23 Jun 2026, 04:54 UTC≈2,770 views10 reactionsread 12 August 2026
Photo

iOS 27 beta 2 不出意外改动又比较大。 beta 1 的时候除了漫山遍野的index未完成哀嚎,还有一大堆KOL吹嘘续航和性能双提升。但是在我看来,这个在官网与 26.4.2 版本对比的 beta 1 还是太早期了: 1、液态玻璃透明档背后是能看出很明显的锯齿状的。 2、低电量模式下的流畅度还不如 26.6 beta。 3、也没觉得续航有什么提升,无论是否索引完。 作为第一个beta是比较出色了,但是说「比 iOS 26 正式版bug还要少」就有点太过了。言归正传,beta 2 这次: 1、液态玻璃又大改了一版本参数,没有明显的背景采样锯齿了,相应地玻璃的边缘折射感也少了(可以对比一下小角)。没有锯齿感的话就可以放心开最透明一档了,特别会影响可读性的场景(比如控制中心)苹果也做了兜底,不会真的透。 2、性能和续航都感觉更好了一点,尤其是低电量模式下。也可能是错觉,因为我也经历过好几次刚升级完感觉不错、两周后又开始

7👏2😁1

19 Jun 2026, 07:08 UTC≈2,760 views5 reactionsread 12 August 2026

https://play.google.com/store/apps/details?id=com.vwfndr.mbl 更新支持焦段切换,物理长焦能用了。 Android现在不需要Pi了,暂时。 小Tip,音量键切换Preset,可选不同快门速度或闪光灯模式,太实用了吧。 Pixel反而不能用,原以为不会出现什么兼容性问题。

👍32

11 Jun 2026, 04:08 UTC≈3,020 views26 reactionsread 12 August 2026

昨天太忙了没发频道消息,今天补发一下。 去年 26 没有第一时间冲DB,后悔,没有见到那个唯一高透的版本。今年索性 27 beta 系列第一时间全部都冲了。负责任地说,再喜欢尝鲜也要等下个月的公测版。目前这个版本最晚也是是四月就做好的,后面几个开发版可能还会相对目前这个版本大改,甚至可能还要不稳定,真正要稳定一点是要等公测版的。真的不喜欢 26.5.1 的话可以上 26.6 beta1, 我试过不错。 网传大量铺天盖地的性能改进,我没感觉,和 26.6 beta 差不多,主屏幕开了低电量模式依然掉帧的。比较好的一点是一直摆脱不掉的「延迟感」少了,就算动画卡卡的也会很快响应,应该是CPU调度改进了。 体感提升最明显是 AirDrop,响应快得离谱,成功率目前还是100%(此前基本是0%)。 macOS beta 感觉bug挺多的,微信商店最新版是无法打开的。放了快两天性能起码没那么差了。最喜欢的一个功能是后台偷偷运行的Mac

😁147👍3🤷‍♂2

13 May 2026, 08:42 UTC≈3,350 views32 reactionsread 12 August 2026

如果说iOS的问题是基础性能/可用性,国产系统给我的感觉就是「没边界感」,比如用户关掉某个功能后,就会有弹窗一直问要不要开。 很典型的案例如我特地把下载服务的流体云关掉,就是觉得它弹来弹去烦,结果现在每点一下应用更新的下载按钮,就弹出一个流体云提醒我可以把下载服务的流体云通知开起来。把我当什么了,能不能尊重一下我的意愿?

👍23😇51👻1🗿1🤗1

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

Citation-graph rank — 390,387 of 1,481,217entries 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.

Forward network

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.

Mentions

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.

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.

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

“搞机日记” (@gaojiriji), 5,084 subscribers as measured 12 August 2026. Telegram Register, tgregister.com/channel/gaojiriji.

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.