Photo, posted without a caption
👍5❤3🔥1🥰1

Channel
@ae86_dao
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Posts edited after publishing · Citations · Handles named that no longer answer · Telegram's recommendations · Cite this entry
25,526subscribers
+2,808 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 10,000–31,623.
| Telegram ID | -1001594628751 |
|---|---|
| Type | Channel |
| Username | @ae86_dao |
| Description | 📱刀刀源 https://xiangfeidexiaohuo.github.io 🕹交流群 @ae86_daodao |
| Created | Between 1 August 2021 and 28 February 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 17 September 2026 |
| Measurements held | 34 |
| Confirmed unchanged | 1 time, most recently 17 September 2026 |
| On Telegram | t.me/ae86_dao |
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 10 September 2026 and assigned it the closest of 31 fixed categories, at 94% 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, 19:17 | 25,526 | +129 |
| 15 Sept 2026, 19:16 | 25,397 | +116 |
| 13 Sept 2026, 23:21 | 25,281 | +115 |
| 12 Sept 2026, 06:15 | 25,166 | +76 |
| 9 Sept 2026, 20:54 | 25,090 | +141 |
| 6 Sept 2026, 12:21 | 24,949 | +93 |
| 4 Sept 2026, 07:00 | 24,856 | +55 |
| 2 Sept 2026, 22:15 | 24,801 | +43 |
| 1 Sept 2026, 17:43 | 24,758 | +61 |
| 31 Aug 2026, 17:25 | 24,697 | +28 |
| 30 Aug 2026, 18:06 | 24,669 | +50 |
| 29 Aug 2026, 19:37 | 24,619 | +53 |
| 28 Aug 2026, 17:13 | 24,566 | +30 |
| 27 Aug 2026, 18:43 | 24,536 | +52 |
| 26 Aug 2026, 17:28 | 24,484 | +50 |
| 25 Aug 2026, 16:03 | 24,434 | +80 |
| 24 Aug 2026, 12:42 | 24,354 | +93 |
| 22 Aug 2026, 22:13 | 24,261 | +88 |
| 21 Aug 2026, 08:34 | 24,173 | +37 |
| 20 Aug 2026, 09:48 | 24,136 | first reading |
125 posts held, back to 2 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 63 pages of Telegram’s post history, 20 posts per page.
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 28 of 33 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 25 September 2026 |
|---|---|
| Posts held | 125 (2 August 2026 – 25 September 2026) |
| Views total | 142,396 |
| Reactions total | 100 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 27 Sept 2026, 10:54 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.
Lifetime counters from Telegram’s own channel header, read 27 September 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.
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.
316 reactions across 89 posts, in 11 distinct kinds. The most used accounts for 74.4% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 235 | 74.4% | |
| 👍 | 62 | 19.6% | |
| 🔥 | 5 | 1.58% | |
| 🥰 | 4 | 1.27% | |
| 🤣 | 3 | 0.949% | |
| 👎 | 2 | 0.633% | |
| 🎉 | 1 | 0.316% | |
| 👏 | 1 | 0.316% | |
| 👻 | 1 | 0.316% | |
| 💯 | 1 | 0.316% | |
| 😍 | 1 | 0.316% |
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 104 of the 125 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 316 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 125 most recent posts we hold, published 2 August 2026 to 25 September 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.
Photo, posted without a caption
👍5❤3🔥1🥰1
🈷 多巴胺3 ➡ opa334开发的多巴胺越狱工具,无根rootless。 ⏺ A14 - A17 / M1 - M2:iOS 15.0 - 17.3.1 ⏺ A8 - A13:iOS 15.0 - 18.7.1 / 26.0 - 26.0.1 🔔 一些越狱源,点击查看! 🔄 更新: 向 frida 暴露一个 API,使其能够通过 hookd 进行内存 hook,修复了在 iOS 26+ 上使用 frida 时发生崩溃的问题(该修复已合入上游 frida-gum,但 frida 端的稳定版本仍在等待中)(由 @ devnoname120 贡献) 修复了在 iOS 17+ 上,若用户空间重启前已挂载开发者磁盘映像,则用户空间重启后 Xcode 调试失效的问题 #越狱 #多巴胺3 #rootless 📱 Dopamine3
❤1
☄️ Relaxin - 白名单 By 真皮 🔗 Relaxin 官网 📱 Relaxin 开源 ⏺ A12/A13:iOS16.5–18.7.1, 26.0–26.0.1 😀 A14–A17、M1-M2:iOS16.5–17.3.1 ✔️ RootHide 越狱,屏蔽越狱检测更友好! 🔔 一些越狱源,点击查看! 💎 白名单:越狱后默认插件不生效,安装真皮源内 RootHide Inject Manager 插件,勾选插件生效的App/进程。 🔄 更新: Relaxin真皮白名单 🚗 #秋名山 #越狱 #Relaxin #ios17 #白名单
☄️ Relaxin 越狱(官方版) 🔗 Relaxin 官网 📱 Relaxin 开源 😀 A12/A13:iOS16.5–18.7.1, 26.0–26.0.1 ⏺ A14–A17、M1-M2:iOS16.5–17.3.1 ✔️ RootHide 越狱,屏蔽越狱检测更友好! 🔔 一些越狱源,点击查看! 🔄 更新: Relaxin v0.5.4(2026-09-24) - 将 Relaxin 内置的 RootHide Manager 替换为 Umbra 2.0。 - 新增 Irisin 4.4.1 作为可选的软件包管理器,首次设置时可选择,越狱后重新安装时也可选择。 - 新增自定义 URL Scheme 替换功能,同时继续对排除的 App 隐藏仅限越狱环境使用的链接。 - 在 iOS 和 iPadOS 16 上进一步隐藏越狱痕迹,避免被排除的 App 检测到。 - 提升 A12 设备的越狱成功率。 - 修复部分基于 PP…
❤6
Umbra (https://apt.owngoal.dev/ 源内有)替换了原本的 RootHide App Umbra 2.0 是适用于 iOS 15 及更新版本的 RootHide 管理 App,提供黑名单、环境检查、var 清理、服务端口设置及自定义规则。URL Scheme 替换页面需要 Relaxin 0.5.4 或更新版本。 #越狱源 #越狱
❤2
Relaxin隐根越狱—测试:真皮白名单
❤2
Relaxin隐根越狱—测试: - 用 Umbra (https://apt.owngoal.dev/ 源内有)替换了原本的 RootHide App,全新界面更多功能 - iOS 16 上隐藏更多越狱痕迹 - 提升 A12 设备的越狱稳定性 - 增强 iOS 17 上,越狱守护进程的问题诊断能力 - 内存访问模式由 PTE-only 改回 Full physrw,但引入了全新的预取缓解方案
🔄 ❗️❗️ 整理的越狱源 🔔 源不一定多,够用就好,按需添加! 📌 OwnGoal源(乌龙工作室) https://apt.owngoal.dev/ 📌 82Flex(乌龙工作室) https://apt.82flex.com/ 📌 刀刀源 (汉化、自用) https://xiangfeidexiaohuo.github.io/ 📌 电话助手源 http://apt.htv123.com/ 📌 真皮源(Hello系列插件) https://rootless.002599.xyz/ 📌 赵楠源 https://invalidunit.github.io/repo/ 📌 季伯之家(各种定制插件) https://sini921.github.io/ 📌 INITNIL源(Netskao大佬) https://jailrepo.initnil.com/ 📌 来了老弟源(FT、ST等) https://lail…
❤10👍3🎉1🔥1🥰1
底部上滑手势:新增震动反馈,新增返回上一层(支持微信、QQ等常见APP)
❤1👍1
最近恶意软件猖獗,各位务必小心,不要安装来历不明的巨魔软件或者越狱插件!
👍1
Photo, posted without a caption
❤2
🔄 rootless转roothide越狱,遇到的坑? ⏺ 如图,无根越狱转隐根越狱,在无根越狱状态下没清干净,导致dopamine文件夹还残留,怎么办?直接删! ⏺ 在隐根默认源内安装Filza越狱版,不要去其他源/Filza官方源去转无根的Filza;直接进入 /private/preboot/ 目录下,删除残留的 dopamine-XXXX 文件夹即可。 ⏺ 然后清除越狱,可能你点了移除越狱,桌面还会看到 sileo/roothide 等越狱APP的图标/或者白图标,再点一次移除越狱,然后进入巨魔的设置——重建图标换成,应该就消失了。 🚗 #秋名山 #越狱残留 #转隐根 #越狱技巧 #科普
❤5
Showing the 12 most recent of 125 posts we hold for @ae86_dao. 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.
@ae86_dao edited 3 posts after it first published — the same permalink now carries different wording than the one this register originally read, caught because our own crawl held a copy of the earlier text.
An edit is not deception. Typo fixes, price updates and corrections look exactly like this too — this register can tell you the wording changed and when, not why. How this is measured.
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.
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.
@ae86_dao named 3 handles that resolve to nothing today. That is a fact about the reference, not necessarily a fact about the handle’s history — see the two groups below.
Most of these may never have existed as a live channel at all. A handle a channel names can be a typo, an aspirational name nobody registered, or a channel that was already gone before this one ever mentioned it. Unless a row below is marked evidenced, all we know is that it references a handle that is not a live channel today — not that anything “died”. How this is measured.
References a handle that is not a live channel — we have no record it ever was one.
Telegram’s own answer, not this register’s. When this register asks Telegram’s API what is similar to this channel, this is the list it returns, in the exact order Telegram returns it — never re-sorted by subscribers or by anything else this register measures. The relationship, and the order, are Telegram’s; we record them and date them, and make no claim of our own about which of these channels actually resemble this one.
Read from Telegram’s recommendation API, most recently 14 September 2026. Telegram holds a list like this for a small and growing share of the register — how this is measured, and why most channel pages show nothing here.
The reverse of the list above, and a different kind of signal. This does not require this channel to have ever been asked about directly — each row below is a channel we DID ask Telegram about, whose Telegram-generated list happened to include this one. A channel can appear here with an empty list above it, because being named by someone else’s query is independent of having been queried itself.
This channel appears in 6 seed channels' Telegram-generated recommendation lists in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.
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.
“刀刀源 | iOS | 越狱” (@ae86_dao), 25,526 subscribers as measured 17 September 2026. Telegram Register, tgregister.com/channel/ae86_dao.
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.