或许是全网第一个支持 TF 在线砸壳的 Bot? 现已上线 限时开放至 11 月 8 日 23:59 TF 接口风控比较严 滥用成本可能会翻几倍 所以不会作为公益功能长期开放 稳定完善后开放赞助使用,仅限 TF 原有 App Store 砸壳功能仍公益开放 https://t.me/IPADumpBot
❤5

Channel
@vita_app
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Posts recorded as deleted · Citations · Cite this entry
11,107subscribers
+1,075 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 10,000–31,623.
| Telegram ID | -1002268269750 |
|---|---|
| Type | Channel |
| Username | @vita_app |
| Description | 分享个人自用应用、插件。 完全免费 群聊@vitaqun |
| Created | Between 1 September 2024 and 31 March 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 6 November 2026 |
| Measurements held | 60 |
| Confirmed unchanged | 1 time, most recently 6 November 2026 |
| On Telegram | t.me/vita_app |
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 11 September 2026 and assigned it the closest of 31 fixed categories, at 98% 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 the other topics.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 6 Nov 2026, 14:40 | 11,107 | +10 |
| 5 Nov 2026, 18:11 | 11,097 | +16 |
| 4 Nov 2026, 16:07 | 11,081 | +11 |
| 3 Nov 2026, 15:15 | 11,070 | +7 |
| 2 Nov 2026, 18:09 | 11,063 | +10 |
| 1 Nov 2026, 21:15 | 11,053 | +5 |
| 31 Oct 2026, 22:28 | 11,048 | +2 |
| 30 Oct 2026, 19:49 | 11,046 | +16 |
| 29 Oct 2026, 21:01 | 11,030 | +17 |
| 28 Oct 2026, 21:50 | 11,013 | +6 |
| 28 Oct 2026, 00:16 | 11,007 | +14 |
| 27 Oct 2026, 02:20 | 10,993 | +28 |
| 25 Oct 2026, 22:46 | 10,965 | +31 |
| 23 Oct 2026, 21:46 | 10,934 | +6 |
| 22 Oct 2026, 23:55 | 10,928 | +7 |
| 21 Oct 2026, 20:31 | 10,921 | +13 |
| 20 Oct 2026, 18:26 | 10,908 | +10 |
| 19 Oct 2026, 15:40 | 10,898 | +10 |
| 18 Oct 2026, 12:20 | 10,888 | +9 |
| 17 Oct 2026, 11:06 | 10,879 | first reading |
25 posts held, back to 15 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 47 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.
| Window | Rolling 30 days · latest post in window 5 November 2026 |
|---|---|
| Posts held | 25 (15 January 2026 – 5 November 2026) |
| Views total | 32,040 |
| Reactions total | 46 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 7 Nov 2026, 08:31 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 7 November 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 2 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.
254 reactions across 21 posts, in 8 distinct kinds. The most used accounts for 61.4% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 156 | 61.4% | |
| 👍 | 65 | 25.6% | |
| 😭 | 19 | 7.48% | |
| 🤡 | 6 | 2.36% | |
| 💩 | 4 | 1.57% | |
| 👎 | 2 | 0.787% | |
| 😁 | 1 | 0.394% | |
| 🤔 | 1 | 0.394% |
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 21 of the 25 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 254 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 25 most recent posts we hold, published 15 January 2026 to 5 November 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.
Telegram’s own ‘edited’ marker: 3 of 6 posts held from the last 30 days (50.0%) carried it when this register last read them. The marker says a post was changed after publishing, not what it said before — this register holds the earlier wording only where an edit fell between two of its own reads (see the edit ledger and how it is measured).
或许是全网第一个支持 TF 在线砸壳的 Bot? 现已上线 限时开放至 11 月 8 日 23:59 TF 接口风控比较严 滥用成本可能会翻几倍 所以不会作为公益功能长期开放 稳定完善后开放赞助使用,仅限 TF 原有 App Store 砸壳功能仍公益开放 https://t.me/IPADumpBot
❤5
联想小新 x MacOS 🤔 GPU 已驱动
❤5🤡2
理论上可以把 vesper 的操作功能独立出来做一个 iOS agent🤔但是 jailbreak Only 已经劝退了大多数人了,隔壁 Android 无障碍+shizuku 实现的还挺火的
👍3
Yuki 0.1-2 优化性能 #Yuki
❤5👍3
最近 oai 大善人的 token 用不完, vibe 了个 iOS 逆向平台,整合 FLEX、Frida、IDA Pro、Theos,支持 AI 通过 SSH 连接越狱设备,分析 App、动态 Hook、编写和部署 Logos Tweak。 目前还在完善中,具体完善程度看 oai 善不善,欢迎 pr star。 https://github.com/Wtrwx/vesper
❤3👍2
iOS27.0.1 越狱好像快来了 距离我的 flag 仅过了刚刚一周 理论上现在所有 18p/pm 都是这个版本。感兴趣的可以先搞一台了。我觉得漏洞迟早会公布的。
👍15❤3
难以想象DYYY早期大多数工作还是用copilot和网页版ChatGPT辅助开发的,跟现在的codex和cc比简直过的就是原始人的日子。现在我主力机已经换小米挺久了,iOS新版没法越狱没有玩的兴趣,而且要考研忙的焦头烂额,感觉还不一定考得上,前期学习效率太低了,等iOS新版出越狱了就回来更新插件。 其实你们如果要自己用的话完全可以classdump出来丢给dsv4flash让它来适配新版本,我觉得不会有什么问题 翻译一下就是不更新,想玩的自己用AI搞,普通用户用其他插件,至于Yuki反正也没混淆,丢给ds应该可以直接出源码,逻辑很简单的,而且其实我iOS设备一直装的抖音 37.5 也能正常用,这软件好像没什么更新的必要。
👍13❤2😭2
过年了 一觉睡醒 dopamine3.0 出来了 但是我选择等一手 roothide 没注意,频道怎么不更新了还破 万了,到底进来了多少人机
❤19
Vita's App pinned a photo
据传7月31日后要下架流量卡互联网渠道,现在联通出了一些套餐不错的卡,有需要可以在我这开 贵州联通 29元 280g流量 100分钟通话 送会员 29元390G+100分钟 都是四年套餐 之后可能可以续 建议开贵州的 原套餐29元80g100分钟就算不能续也不会涨价,办办卡家人们,好像快竞合了,客服 vx 加不上可以直接 tg 私聊我 #广告
❤12👍1
https://github.com/yujincheng08/BiliRoaming 考虑到近期存在的种种风险,以及目前我的 DYYY 分支事实上已经长期处于近似无人维护的状态,所以已将仓库改为 archived,有需要可以尽早 fork 或者 clone,未来可能会删除所有源代码。
😭17👍7❤2👎2
LibrePods HyperOS3 适配版 优化了模拟 Apple 设备 HyperOS 上的表现,减少断连,并且支持与 MacOS 自动切换 欢迎小米用户反馈 测试环境 HyperOS 3.0.304.0 最新蓝牙 MacOS15.6.1 https://github.com/Wtrwx/librepods/actions/runs/28511927673
❤3
Showing the 12 most recent of 25 posts we hold for @vita_app. 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.
We recorded 2 posts on @vita_app as deleted — posts this register held that were missing from the channel’s public page on two separate reads, taken from different network addresses at least an hour apart.
A deletion is not wrongdoing. This register can see that a post it held is no longer on the channel’s public page, and when — not why. Expired ad placements, reposts, rotating links and corrections all look the same. This is a count of recorded detections, not an exact total: it misses deletions we could not see, because only a post we held and later re-read inside the page can be seen to go, and it may include a small number of wrong records. 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.
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 6 November 2026 — this entry's latest reading, not the date you are reading this.
“Vita's App” (@vita_app), 11,107 subscribers as measured 6 November 2026. Telegram Register, tgregister.com/channel/vita_app.
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.