🟢最新v1.8.5版本 针对快速清理进行优化 排除了系统缓存的相关服务文件 以及plist、db数据库等文件的清理 防止出现应用丢失权限等异常状态
❤51👎20👾8

Channel
@iosxcode
On this record: Topic · Growth · Engagement · Reactions · Posts · Citations · Cite this entry
3,975subscribers
+161 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
| Telegram ID | -1002730986217 |
|---|---|
| Type | Channel |
| Username | @iosxcode |
| Created | 12 July 2025 — measured — dated from the channel’s first post |
| First recorded | 7 August 2026 |
| Last confirmed live | 15 September 2026 |
| Measurements held | 14 |
| Confirmed unchanged | 1 time, most recently 15 September 2026 |
| On Telegram | t.me/iosxcode |
Software piracy — 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 14 September 2026 and assigned it the closest of 31 fixed categories, at 92% 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 |
|---|---|---|
| 15 Sept 2026, 00:40 | 3,975 | +10 |
| 11 Sept 2026, 02:15 | 3,965 | +14 |
| 6 Sept 2026, 13:41 | 3,951 | +18 |
| 1 Sept 2026, 19:54 | 3,933 | +15 |
| 29 Aug 2026, 23:17 | 3,918 | +19 |
| 26 Aug 2026, 18:47 | 3,899 | +17 |
| 24 Aug 2026, 00:54 | 3,882 | +18 |
| 20 Aug 2026, 10:06 | 3,864 | +3 |
| 17 Aug 2026, 18:08 | 3,861 | +15 |
| 14 Aug 2026, 03:58 | 3,846 | +14 |
| 11 Aug 2026, 04:57 | 3,832 | +16 |
| 7 Aug 2026, 23:21 | 3,816 | +2 |
| 7 Aug 2026, 19:02 | 3,814 | no change |
| 7 Aug 2026, 18:53 | 3,814 | first reading |
13 posts held, back to 12 July 2025 — the reader has reached the start of this channel’s public history, so this is the full archive Telegram still exposes. 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 13 posts for this entry, the most recent from 2 April 2026. An engagement rate over an empty window would be a number about nothing.
393 reactions across 11 posts, in 9 distinct kinds. The most used accounts for 45.5% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 179 | 45.5% | |
| 🤡 | 77 | 19.6% | |
| 👍 | 73 | 18.6% | |
| 👎 | 21 | 5.34% | |
| 😱 | 11 | 2.80% | |
| 🤮 | 11 | 2.80% | |
| 👾 | 8 | 2.04% | |
| 😁 | 7 | 1.78% | |
| 🔥 | 6 | 1.53% |
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 12 of the 13 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 393 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 13 most recent posts we hold, published 12 July 2025 to 2 April 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.
🟢最新v1.8.5版本 针对快速清理进行优化 排除了系统缓存的相关服务文件 以及plist、db数据库等文件的清理 防止出现应用丢失权限等异常状态
❤51👎20👾8
🟢最新v1.8.4版本 该版本未新增功能 只解决近期频道反馈的问题 ✅版本更新日志: 解决管理Hook页面启动应用出现黑屏情况、一键粘贴增加弹窗防止误触、解决应用降级选择国家列表自动回弹、APP Store切换账号友好名称显示覆盖增强等频道反馈上来的问题
❤11👍7👎1
🟢Deb提取 v3.2版本 ⚡更新日志: 修复v3.1版本,已下载页面点击重打包deb后分享至sileo等越狱商店无法识别问题
🟢Deb提取 v3.1版本 全网功能最全、最好用的deb工具 可巨魔、可自签,支持iOS15+设备 ⚡更新日志: 1、修复v3.0版本deb打包完成后没保存在已下载页面 2、dylib在打包成deb文件时,可以修改dylib的名字 3、在设置页面也添加了deb打包入口,方便你们快速进入该页面
❤3
🟢Deb提取 v3.0版本 可巨魔、可自签,支持iOS15+ ⚡更新日志: 解决已知BUG 优化性能、提升流畅度 新增Dylib一键打包成deb文件
👍6
🟢最新v1.8.3版本 ✅版本更新日志: 1、清理页面新增清理记录,所有被清理的文件一目了然 2、一键粘贴仅对官方应用生效 3、拖壳-主进程修复[排除了Framework进程连带拖壳情况] 4、个别系统差异化功能增加了说明
❤8👍2
🟢最新v1.8.2版本 ✅版本更新日志: 1、修复环境检测 2、优化APP工具页面菜单操作 3、新增隔空投送修复 4、优化一些隐患性功能BUG
❤6👍2
🟢最新v1.8.1版本已推送 ✅版本更新日志: 1、修复类结果遗漏 2、分析页面、分析记录、分析对话添加管理Hook快捷入口,方便快捷跳转 3、管理Hook的Hook列表自动去重 4、屏蔽系统OTA功能现在全系统都有效
👍4❤2
🟢最新v1.8.0版本已推送 ✅版本更新日志: 新增和平绿盾守护 有Bug反馈丢聊天频道即可
🔥5❤4
⚡Fuck工具箱即将发布 每天抽空写一点即将开发完成 第一个版本即将发布完全免费
❤57👍18🤮11🔥1
🟢Fuck-AI逆向 项目已立项 开发需要一定时间,敬请期待!
🤡77👍34❤10😱10
目前唯一在用的发布频道点击前往 目前唯一在用的讨论频道点击前往
❤27😁7😱1
Showing the 12 most recent of 13 posts we hold for @iosxcode. 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.
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.
Names
Channels on the register whose handles appear in this channel's posts.
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 15 September 2026 — this entry's latest reading, not the date you are reading this.
“iOS逆向” (@iosxcode), 3,975 subscribers as measured 15 September 2026. Telegram Register, tgregister.com/channel/iosxcode.
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.