Sticker, posted without a caption
👍13
Signed 晚风

Channel
@MapleAutumn
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Polls · Citations · Cite this entry
8,556subscribers
+7,944 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
| Telegram ID | -1002068078215 |
|---|---|
| Type | Channel |
| Username | @MapleAutumn |
| Description | 欢迎各位来到MapleAutumn🍁的小窝! Maple交流频道 Maple detector / MapleSU 『时光流转,愿你能与珍爱之人再度重逢』 交流群 @MapleAHouse |
| Created | Between 1 November 2023 and 31 May 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 6 August 2026 |
| Last confirmed live | 17 November 2026 |
| Measurements held | 24 |
| Confirmed unchanged | 1 time, most recently 17 November 2026 |
| On Telegram | t.me/MapleAutumn |
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 18 September 2026 and assigned it the closest of 31 fixed categories, at 43% 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 |
|---|---|---|
| 17 Nov 2026, 03:35 | 8,556 | +1,484 |
| 11 Nov 2026, 19:31 | 7,072 | +978 |
| 7 Nov 2026, 14:55 | 6,094 | +757 |
| 4 Nov 2026, 10:19 | 5,337 | +256 |
| 1 Nov 2026, 18:48 | 5,081 | +442 |
| 30 Oct 2026, 02:49 | 4,639 | +341 |
| 27 Oct 2026, 11:14 | 4,298 | +288 |
| 24 Oct 2026, 18:47 | 4,010 | +272 |
| 21 Oct 2026, 10:21 | 3,738 | +207 |
| 18 Oct 2026, 12:36 | 3,531 | +367 |
| 15 Oct 2026, 16:06 | 3,164 | +227 |
| 12 Oct 2026, 13:05 | 2,937 | +551 |
| 5 Oct 2026, 13:56 | 2,386 | +772 |
| 28 Sept 2026, 02:35 | 1,614 | +164 |
| 18 Sept 2026, 21:40 | 1,450 | +116 |
| 14 Sept 2026, 02:42 | 1,334 | +101 |
| 10 Sept 2026, 15:20 | 1,233 | +134 |
| 5 Sept 2026, 15:18 | 1,099 | +42 |
| 1 Sept 2026, 18:55 | 1,057 | +21 |
| 29 Aug 2026, 21:55 | 1,036 | first reading |
39 posts held, back to 22 July 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 10 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 17 November 2026 |
|---|---|
| Posts held | 39 (22 July 2026 – 17 November 2026) |
| Views total | 152,088 |
| Reactions total | 787 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 17 Nov 2026, 05:56 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 17 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 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.
820 reactions across 30 posts, in 11 distinct kinds. The most used accounts for 78.7% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 👍 | 645 | 78.7% | |
| ❤ | 138 | 16.8% | |
| 🤩 | 8 | 0.976% | |
| 🔥 | 7 | 0.854% | |
| 👎 | 6 | 0.732% | |
| 👏 | 6 | 0.732% | |
| 👾 | 3 | 0.366% | |
| 🥰 | 3 | 0.366% | |
| ⚡ | 2 | 0.244% | |
| 🍌 | 1 | 0.122% | |
| 🖕 | 1 | 0.122% |
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 30 of the 39 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 820 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 39 most recent posts we hold, published 22 July 2026 to 17 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: 7 of 19 posts held from the last 30 days (36.8%) 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).
Sticker, posted without a caption
👍13
Signed 晚风
感觉能撂倒一大批人
👍21
Signed 晚风
#Maple_Detect 📣预计在Maple检测某个版本加一批侧信道检测 🔗顺手分析了一下 在三角洲中看到了一批还没有人注意有意思的侧信道检测 或许是你的三方与协议原因
👍23
Signed MapleAutumn
Sticker, posted without a caption
👍41❤7
Signed MapleAutumn
😪来自抖音 By.SeedDance 是大肥鱼喵
👍45❤9🔥1
Signed MapleAutumn
MilkSU_0.2.3.apk 1.修复 KPM 集成状态: 恢复缺失的整合记录后及时刷新界面,改善旧版 Android boot 头及不同 boot 分区路径的兼容性。 2.修复覆盖更新后 Root 会话失效: 自动重连失败或已退出的 Shell 会话,并实时刷新原生层管理状态。 3.改善启动稳定性: 完善原生库不可用、版本信息缺失及系统 API 差异的异常处理。 4.新增 x86_64 管理器构建: APK 同时包含 arm64-v8a 和 x86_64 原生组件。 本次仅更新管理器与用户空间组件,内核补丁保持 32802,KPM 引擎未改动。已运行 32802 内核补丁的用户无需重新安装补丁。
👍51❤15
Signed 喻安
📣 #MapleSU_Beta ⭐About test 在此特别感谢各位在内测期间的积极测试与反馈 以上为部分内测用户反馈图 我们仍在持续优化 修复问题与提升无痕性中 MapleSU_Ultra Feature: 全新底层架构:在内核层直接实现 SU 授权,灵活可控。 零痕迹无检测点:坚持 0 挂载、0 SELinux 策略篡改,从根源上拒绝所有侧信道检测,全程不留痕迹。 极简一键刷入:告别繁琐的修补流程,支持KSU等分支面具一键迁移刷入,开箱即用。 预计支持内核版本:5.10-6.18 设备支持:全机型越狱模式/解锁 与KSU不同的实现方式 不动Selinux策略 不挂载 从根本上解决检测 🔗我们预计于本周末至下周开启公测 敬请期待. ⭐Code is coming. 解决一切侧信道检测点!避免修改Selinux引起的各种问题
👍51❤26🤩4
Signed MapleAutumn
Sticker, posted without a caption
👍32❤3
Signed MapleAutumn
仍然TEE不可信的设备说明Soter压根就没被请求..下个版本帮你们手动拉起预热试试吧
👍46❤4
Signed MapleAutumn
⭐TEESimulator-RS_Maple 6.0.32 KSU/APatch及其分支兼容版本 最佳的TEE模拟模块 解决骁龙设备TEE不可信问题 解决Soter(非屏蔽) 解决已知一切TEE探测问题 对齐原生AOSP TEE行为 修复上游实现的所有BUG 内置WebUI管理功能 新增补丁日期自动同步 无需各种增强模块 6.0.32更新日志: - 修复了Soter兼容在部分安卓17上不可用的问题 - WebUI新增了明确的完整日志导出 - 新增了Keybox.xml不存在时的提示 - 修复了部分设备Target无法更新的问题 改为定时更新 - 修复WebUI始终显示Keybox不存在的问题 By.MapleAutumn🍁
👍35❤12🔥2
Signed MapleAutumn
⭐TEESimulator-MapleSU KSU/APatch及其分支兼容版本 🔗相关源码已在Git开源 欢迎各位提交Issue并指出问题 对TEE模块想尝试的 最新版已在仓库发布 可进仓库安装 解决骁龙设备TEE不可信问题 解决Soter(非屏蔽) 解决已知一切TEE探测问题 修复上游实现的所有BUG 内置WebUI管理功能 新增补丁日期自动同步 无需各种增强模块 https://github.com/FengQiuFQ/TEESimulator-MapleSU
👍23❤5👏3⚡2🍌1
Signed MapleAutumn
TEE模块目前暂时考虑仅在MapleSU_Ultra工作模式内进行内置 KSU暂未适配 反馈部分机型失败 暂缓发出 已开源
👍22🔥2❤1
Signed MapleAutumn
Showing the 12 most recent of 39 posts we hold for @MapleAutumn. 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.
The poll we hold for this entry, as Telegram rendered it when we read the post. A poll’s figures keep moving after that, so each one is dated.
是否加强检测?
Shares as published. No per-option vote count is published by Telegram, so none is shown.
Percentages only — there are no per-option vote counts here, because Telegram publishes none. The public post preview gives each option’s share and a single voter total, and nothing else. Multiplying one by the other would produce a per-option tally that looks measured and is not: the shares are rounded to whole numbers before we ever see them. We print what was published and leave the column that does not exist empty.
The shares need not add up to 100. Rounding alone puts many polls at 99 or 101. A poll that allows more than one answer per voter runs well past 100 by design, and several here do. The bars are drawn against a fixed 100% track at each option’s own percentage rather than normalised to the total, so a poll that exceeds it shows that it does instead of being quietly rescaled.
Read from the 39 most recent posts we hold, published 22 July 2026 to 17 November 2026. Telegram labels each poll by kind — an anonymous poll, a quiz, a closed set of final results — and that label is reproduced rather than paraphrased.
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.
Named by 8 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.
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 17 November 2026 — this entry's latest reading, not the date you are reading this.
“Mapleの小窝” (@MapleAutumn), 8,556 subscribers as measured 17 November 2026. Telegram Register, tgregister.com/channel/MapleAutumn.
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.