⚡️ Swiftgram 12.9.2 已在 App Store 上架! 包含 Telegram 最新更新,带来富文本编辑器、社区、群组限时消息等更多功能

Channel
SG / Swiftgram
@SwiftgramZH
On this record: Topic · Growth · Engagement · Posts · Citations · Cite this entry
1,334subscribers
-27 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
Register entry
| Telegram ID | -1003416951268 |
|---|---|
| Type | Channel |
| Username | @SwiftgramZH |
| Created | 17 January 2026 — measured — dated from the channel’s first post |
| First recorded | 6 August 2026 |
| Last confirmed live | 18 September 2026 |
| Measurements held | 13 |
| Confirmed unchanged | 1 time, most recently 18 September 2026 |
| On Telegram | t.me/SwiftgramZH |
Topic
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 18 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.
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 18 Sept 2026, 19:58 | 1,334 | -1 |
| 14 Sept 2026, 21:20 | 1,335 | -5 |
| 11 Sept 2026, 03:15 | 1,340 | -9 |
| 2 Sept 2026, 05:28 | 1,349 | -1 |
| 30 Aug 2026, 08:08 | 1,350 | -2 |
| 27 Aug 2026, 14:45 | 1,352 | -1 |
| 24 Aug 2026, 22:23 | 1,353 | -2 |
| 21 Aug 2026, 17:36 | 1,355 | +1 |
| 18 Aug 2026, 19:56 | 1,354 | -2 |
| 16 Aug 2026, 02:16 | 1,356 | -4 |
| 6 Aug 2026, 19:50 | 1,360 | -1 |
| 6 Aug 2026, 08:00 | 1,361 | no change |
| 6 Aug 2026, 02:18 | 1,361 | first reading |
Engagement
14 posts held, back to 17 January 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 14 posts for this entry, the most recent from 3 August 2026. An engagement rate over an empty window would be a number about nothing.
Recent posts
我的名字出现在了 Telegram 官方应用 里 🤯 新的 Apple Watch 应用基于我的 TDLibKit 封装构建。在过去 5 年里,我一直默默维护这个库,让任何人都能为 Apple 平台打造优秀的 Telegram 客户端。 感谢 Telegram 团队的信任。很高兴能够为你们赋能,并为 Telegram 生态系统的未来贡献力量。 TDLib 是开启一个新 Telegram 客户端项目的最佳方式。如今,通过 TDLibKit,你可以创建 iOS、macOS、watchOS、tvOS 和 visionOS 应用。
⌚️ Swiftgram 12.8 已在 App Store 上架,我们也回归 Apple Watch 了! watchOS 应用现在已经独立运行,无需把手机带在身边也能查看消息。需要 watchOS 26+。 我对 Telegram 新版 Watch 应用做了- 些小改进: • 聊天预览空间更大 - 缩小了头像尺寸,让小屏机型上的体验更好。 • 群聊中加入头像 - 有时候我只记得别人的头像。 同时包含 Telegram 最新功能,例如机器人的富文本、群组 AI Guardian,以及更多内容。
🆕 Telegram Watch Beta 需要最新的 watchOS 您可以使用 Swiftgram 扫描二维码登录
新测试版 12.7 已经过 Apple 审核了,4500 个名额,先到先得,想用就自己快点下。 下载地址:beta.swiftgram.app 有问题直接在评论区说
Swiftgram 12.5 已在 App Store 上线! 包含最新的 Telegram 功能,例如:成员标签、在私聊中禁用转发、GIF 编辑、日期格式化等。 👉 支持开发者继续开发
beta.swiftgram.app 12.5
Telegram 正在尝试 Progressive Web Apps iOS 源代码提交 8c54db6 显示,未来可能会为 Web Apps(Telegram Mini Apps)提供实验性的 PWA 支持。虽然 TMA 已经非常强大,但以下是 PWA 的核心特性: • 可在离线或网络较差时运行 • 由于缓存机制,启动速度更快 • 更好地支持系统 API,例如相机、麦克风、相册等 • 可能在后台运行(当 Telegram 客户端处于活动状态时) • 可以作为图标添加到主屏幕 截至目前,该提交已被回滚,但 PWA 可能带来的应用场景包括: • 离线 2FA 身份验证器 • 离线笔记 • 后台同步的实时事件(例如体育赛事) 欢迎分享你的看法:哪些应用可以从 PWA 中受益 👇
认识 Swiftgram Pro 满载 Pro 功能 🚀 ⌨️ 格式面板: 只需单击即可节省时间格式化消息。 🚫 消息过滤器: 减少 SPAM、促销和令人烦恼的消息的可见性。 ⚡️ 独特的应用图标: 自定义 Swiftgram 在主屏幕上的外观。 🔐 账号备份: 即使在重新安装后也可以登录到没有代码的帐户。使用设备上的密钥链来安全存储。 🔕 禁用 @提及和回复: 隐藏或静音不重要的通知。 在 App Store 上下载 Swiftgram 获取 Pro - tg://sg/pro
在 App Store 上下载 Swiftgram 获取 Pro - tg://sg/pro
⚡️ 欢迎使用 Swiftgram!高级 Telegram iOS 客户端 📲 下载 • 解锁频道 • 实时智能翻译 • 无限多账号支持 • 50+ 项个性化定制 • 真正开源 • 完整的消息隐私保护 💬 讨论群:@swiftgram_zh 👤 作者:Sergey @Kylmakalle
Channel photo updated
Showing the 12 most recent of 14 posts we hold for @SwiftgramZH. 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.
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 18 September 2026 — this entry's latest reading, not the date you are reading this.
“SG / Swiftgram” (@SwiftgramZH), 1,334 subscribers as measured 18 September 2026. Telegram Register, tgregister.com/channel/SwiftgramZH.
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.