96221b69-alpha 31000 https://github.com/LSPosed/Magisk/commits/8b98ae6b8c9aa45f4722eaa9917416e484e6279f

Channel
Magisk alpha
@magiskalpha
On this record: Topic · Growth · Engagement · What this channel posts · Posts · Citations · Telegram's recommendations · Cite this entry
65,503subscribers
+271 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 31,623–100,000.
Register entry
| Telegram ID | -1001303307491 |
|---|---|
| Type | Channel |
| Username | @magiskalpha |
| Created | Between 1 March 2018 and 31 July 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 6 August 2026 |
| Last confirmed live | 7 September 2026 |
| Measurements held | 27 |
| Confirmed unchanged | 1 time, most recently 7 September 2026 |
| On Telegram | t.me/magiskalpha |
Topic
Technology — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-UD-Q6_K_XL, prompt version 1) read this channel’s own recent posts on 20 August 2026 and assigned it the closest of 31 fixed categories, at 96% 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 |
|---|---|---|
| 7 Sept 2026, 13:02 | 65,503 | +23 |
| 4 Sept 2026, 19:01 | 65,480 | +29 |
| 3 Sept 2026, 01:44 | 65,451 | -11 |
| 2 Sept 2026, 01:37 | 65,462 | +9 |
| 1 Sept 2026, 03:48 | 65,453 | +4 |
| 31 Aug 2026, 03:26 | 65,449 | +3 |
| 30 Aug 2026, 02:06 | 65,446 | +5 |
| 29 Aug 2026, 00:04 | 65,441 | -1 |
| 27 Aug 2026, 21:53 | 65,442 | +22 |
| 27 Aug 2026, 00:04 | 65,420 | +6 |
| 25 Aug 2026, 22:07 | 65,414 | -6 |
| 24 Aug 2026, 23:37 | 65,420 | +1 |
| 23 Aug 2026, 08:04 | 65,419 | +52 |
| 21 Aug 2026, 17:29 | 65,367 | +18 |
| 20 Aug 2026, 13:21 | 65,349 | +12 |
| 19 Aug 2026, 09:48 | 65,337 | +25 |
| 17 Aug 2026, 09:54 | 65,312 | +23 |
| 15 Aug 2026, 17:08 | 65,289 | +14 |
| 14 Aug 2026, 06:05 | 65,275 | -6 |
| 13 Aug 2026, 02:03 | 65,281 | first reading |
Engagement
21 posts held, back to 7 July 2025 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 71 pages of Telegram’s post history, 20 posts per page.
- ERR · 30 days
- 21.7%
- avg views ÷ 65,503 subscribers
- Avg views / post
- 14,200
- 1 post measured
- Reaction rate
- —
- this channel exposes no reaction counts
- Posts in window
- 1
- of 21 held
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 September 2026 |
|---|---|
| Posts held | 21 (7 July 2025 – 5 September 2026) |
| Views total | 14,200 |
| Reactions total | — |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 9 Sept 2026, 20:06 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.
What this channel posts
- Photos
- 22
- Links
- 89
Lifetime counters from Telegram’s own channel header, read 9 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.
Recent posts
无法规避的Magisk识别方案已经公开:https://github.com/eltavine/Duck-Detector-Refactoring/pull/22 检测方法说明和概念验证app:https://github.com/LSPosed/DirtySepolicy
e8a58776-alpha 30700 https://github.com/LSPosed/Magisk/commits/76dbeef1beabe45ba60262ccd70f12206eb21679
看来攻击者想把这个频道也屏蔽掉,但由于消息是转发消息,所以只有这一条死掉了,连原消息都正常。从这条消息的统计报告看,其它频道转发的都存活。 攻击者在大量举报上传了apk的频道,建议从私有频道转发避免公开频道被完全屏蔽。
ccb264f3-alpha 30600 这条转发消息被屏蔽了,但原消息正常,请进群下载:https://t.me/c/1414270883/143996
https://pki.consumer.huawei.com/ca/ 发现华为公示了根证书,但是没有发现 RootDeviceAttestationCa 的实际使用样本,可能仅鸿蒙设备使用 (没有计划开发鸿蒙版本或者苹果版本的密钥认证
Posted without readable text
c3db2e36-alpha 30400 https://github.com/LSPosed/Magisk/commits/ab751a4d70ccbe267c098db8670eaa9836dd51a1
Magisk v30.3 的su坏了,部分设备上不能工作,更新通道已经撤回推送,安装v30.4。 https://github.com/topjohnwu/Magisk/issues/9373
f16e93c7-alpha 30300 https://github.com/LSPosed/Magisk/commits/f893a39eb7a2af649fe94e17fe1c5281c0f1b41d
Pixel 设备的官方 Root 方法 Android允许解锁设备获得Root权限,这是官方Root方法,至少对 Pixel 设备有效。 需要在RamDisk中加入3个文件: /force_debuggable 空文件,这是开关; /adb_debug.prop,设置需要的属性,例如: ro.adb.secure=0 ro.debuggable=1 ro.force.debuggable=1 /userdebug_plat_sepolicy.cil,设置需要的SELinux政策。 开机时,init会检查开关然后读取并加载属性和政策,开机后可以使用adb root获得root权限。 你可以使用MagiskBoot工具重新打包RamDisk,不过SELinux政策需要自行编写。
为密钥认证引入新的根证书 此更改增强了敏感应用程序认证流程的安全性和可靠性。已为 Android 密钥认证生成了新的根密钥。新的根密钥是 ECDSA P-384 密钥,未来计划使用 ML-DSA(后量子数字签名算法)密钥。 使用 RKP 的设备将于 2026 年 2 月开始接收以此新证书为根的证书。到 2026 年 4 月 10 日,使用 RKP 的设备将只使用新的根证书。
Showing the 12 most recent of 21 posts we hold for @magiskalpha. 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.
Forward network
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
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.
Mentions
Named by 10 registered channels — 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.
@duck_detector · 14,2285 postsCharlieOS || Marble
@CharlieOS_Marble · 2054 postsGeekOS || Updates
@GeekOS_Updates · 7231 postGinkgo Development
@GinkgoDevelopment · 301 post零七八碎
@lingqibasui42 · 51 postMagisk Lite
@MagiskLite · 2,0401 post𝕬𝖙𝖑𝖆𝖓𝖙𝖊𝖆𝖓'𝖘 𝕯𝖚𝖒𝖕 & 𝕲𝖚𝖎𝖉𝖊𝖘 🇵🇸
@native_atlantean · 2691 postOnePlus | Склад
@oneplus_rep · 4011 postBackup
@rmx1911indo · 5011 postULTRA的DP合集
@ultra_dp · 9351 post
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.
Channels Telegram recommends alongside this 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.
@LSPosed · 192,028#1
@real5ec1cff · 36,054#2
@nullptr_dev · 18,892#3
@cemiuiler_canary · 18,199#4
@VoyagerMIUIUpdate · 20,972#5
@InstallerX · 8,652#6
@cemiuiler_release · 26,483#7
@akashaProxy · 1,729#8
@QAuxiliary_CI · 19,477#9
@Pillboard · 3,506#10
@AdClose · 12,146#11
@NPatch · 18,901#12
@microblock_pub · 15,184#13
@xiayinlily · 2,859#14
@c001apk · 6,720#15
@MlgmXyysd_bibilailai · 21,575#16
@waenhancher · 35,544#17
@PixelProps · 14,176#18
@reveny1 · 7,442#19
@PifNEXT · 6,701#20
@huskydg · 4,153#21
@GappsLeaks · 21,335#22
@Sakion_Team · 1,945#23
@PeterSpaceXiaomi · 2,533#24
@ctsfixes · 2,429#25
@android_dumps · 5,646#26
@pzqqt_c · 3,928#27
@libchecker_ci · 3,467#28
@rezygisk · 3,720#29
@magiskmodules22 · 12,831#30
@WSTprojects · 28,266#31
@databackupchannel · 2,253#32
@loopprojects · 9,725#33
@xpl_ex · 3,068#34
@DrDsProjects · 9,305#35
@rootart · 849#36
@MishaalAndroidNews · 11,855#37
@rem01schannel · 10,803#38
@xiaomichinacloud · 533 (as read 21 August 2026)#39
@PUINewsroom · 13,826#40
Read from Telegram’s recommendation API, most recently 21 August 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.
Appears in Telegram’s recommendations for other channels
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.
@LSPosed · 192,028
Telegram ranks this channel #4 of 57 here — alongside 56 others — read 17 August 2026
@real5ec1cff · 36,054
Telegram ranks this channel #7 of 51 here — alongside 50 others — read 2 September 2026
@HideMyApplist · 40,874
Telegram ranks this channel #8 of 24 here — alongside 23 others — read 30 August 2026
This channel appears in 3 seed channels' Telegram-generated recommendation lists in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.
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 7 September 2026 — this entry's latest reading, not the date you are reading this.
“Magisk alpha” (@magiskalpha), 65,503 subscribers as measured 7 September 2026. Telegram Register, tgregister.com/channel/magiskalpha.
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.