#iOS27 Safari 网站变化通知 之前设定了一个,还真成功了,点进去看的确降价了
❤3
Signed o1x

Channel
@o1xinsight
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
2,104subscribers
+8 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
| Telegram ID | -1001497448341 |
|---|---|
| Type | Channel |
| Username | @o1xinsight |
| Created | Between 1 April 2019 and 30 September 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 6 August 2026 |
| Last confirmed live | 17 September 2026 |
| Measurements held | 13 |
| Confirmed unchanged | 1 time, most recently 17 September 2026 |
| On Telegram | t.me/o1xinsight |
Technology — 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 16 September 2026 and assigned it the closest of 31 fixed categories, at 99% 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 |
|---|---|---|
| 17 Sept 2026, 14:41 | 2,104 | +6 |
| 13 Sept 2026, 15:17 | 2,098 | +10 |
| 9 Sept 2026, 19:18 | 2,088 | -2 |
| 4 Sept 2026, 18:01 | 2,090 | -2 |
| 1 Sept 2026, 04:58 | 2,092 | -4 |
| 28 Aug 2026, 19:27 | 2,096 | +1 |
| 26 Aug 2026, 02:32 | 2,095 | -4 |
| 23 Aug 2026, 13:13 | 2,099 | -2 |
| 20 Aug 2026, 03:43 | 2,101 | +3 |
| 16 Aug 2026, 21:23 | 2,098 | +1 |
| 13 Aug 2026, 13:07 | 2,097 | +1 |
| 6 Aug 2026, 20:45 | 2,096 | no change |
| 6 Aug 2026, 20:39 | 2,096 | first reading |
12 posts held, back to 15 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 2 pages 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 12 posts for this entry, the most recent from 4 August 2026. An engagement rate over an empty window would be a number about nothing.
Measured directly from 3 videos 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.
10 reactions across 4 posts, in 2 distinct kinds. The most used accounts for 90.0% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 9 | 90.0% | |
| ❤🔥 | 1 | 10.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 5 of the 12 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 10 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 12 most recent posts we hold, published 15 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.
#iOS27 Safari 网站变化通知 之前设定了一个,还真成功了,点进去看的确降价了
❤3
Signed o1x
#PhotoStatus 正式发布 https://apps.apple.com/us/app/photo-status/id6784043470 开启“优化 iPhone 储存空间”后,你很难直接确认哪些照片和视频的全分辨率原片只保存在iCloud 中。Photo Status 为你的图库提供清晰本地状态,并帮助你将选中的原片下载回设备。 掌握离线可用状态 快速找到需要的内容 清晰跟踪下载进度 为大型图库设计 隐私优先:所有图库分析都通过 Apple Photos API 在设备本机完成。Photo Status 不会上传你的照片图库,不使用第三方分析服务,不连接额外照片服务器,也不会把原片复制到 App 自己的存储中。
❤1
Signed o1x
#iOS27 好像可以自动翻译字幕
❤5
Signed o1x
又发现一款不错的足迹记录 app https://apps.apple.com/app/id6757199948
Signed o1x
#iOS27 更智能和精准的订单追踪 - 更快更精准,处理时间超快,新版本后没有漏过订单(个人体感) - 邮件被移动不再影响追踪,以往邮件移动后订单会缺失具体信息,并且下面不再显示邮件跳转 - 所有渠道都支持详细商品图片➕名称,支持多商品列表(图 3 是以前的亚马逊效果。。)
Signed o1x
#iOS27 beta2 已修复,直接没了indexing 也不知道啥意思🌚
Signed o1x
#iOS27 Indexing 绝对是有bug,卡在50%至少3天了,再往前没查过,可能都一星期了卡着不动
Signed o1x
#iOS27 #SiriAI 系统 AI主打就是方便顺手,如果很多基础东西都可以覆盖,还是快上不少的 目前快速下滑这个动作到打字还需要再优化,测试版来说已经很靠谱了 未来支持其他语言后,就不用打字了,更快,现在 typeless 替代
Signed o1x
#iOS27 #SiriAI 虽然用起来的确顺手,不过还是没chatgpt准啊 长按选择 Ask 可以手动选择使用 chatgpt 而不是 Siri AI 图1为 chatgpt 正确的答案 图2-4 为Siri
Signed o1x
#iOS27 录制视频的 AI 字幕功能 目前仅支持英文
Signed o1x
#iOS27 #SiriAI 用起来挺顺手,蛮不错的
Signed o1x
#iOS27 好看
❤🔥1
Signed o1x
Showing the 12 most recent of 12 posts we hold for @o1xinsight. 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.
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
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.
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 17 September 2026 — this entry's latest reading, not the date you are reading this.
“o1xhack ☁️ 远上天台” (@o1xinsight), 2,104 subscribers as measured 17 September 2026. Telegram Register, tgregister.com/channel/o1xinsight.
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.