Photo, posted without a caption
👍17❤4😐4🦄1

Channel
@FolkPatch
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Posts recorded as deleted · Citations · Cite this entry
12,163subscribers
+2,560 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 10,000–31,623.
| Telegram ID | -1003417958683 |
|---|---|
| Type | Channel |
| Username | @FolkPatch |
| Description | Root access to the kernel can be achieved simply by patching the Boot partition for reflashing. This solution is based on a non-parallel extended branch of APatch, with a primary focus on UI/UX design |
| Created | Between 1 November 2025 and 30 April 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 6 August 2026 |
| Last confirmed live | 11 November 2026 |
| Measurements held | 59 |
| Confirmed unchanged | 1 time, most recently 11 November 2026 |
| On Telegram | t.me/FolkPatch |
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 11 September 2026 and assigned it the closest of 31 fixed categories, at 95% 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 |
|---|---|---|
| 11 Nov 2026, 06:41 | 12,163 | +26 |
| 9 Nov 2026, 13:59 | 12,137 | +64 |
| 8 Nov 2026, 04:00 | 12,073 | +47 |
| 6 Nov 2026, 22:10 | 12,026 | -2 |
| 5 Nov 2026, 20:56 | 12,028 | +24 |
| 4 Nov 2026, 21:37 | 12,004 | +8 |
| 3 Nov 2026, 21:06 | 11,996 | +30 |
| 2 Nov 2026, 19:31 | 11,966 | +17 |
| 1 Nov 2026, 19:30 | 11,949 | +10 |
| 31 Oct 2026, 22:55 | 11,939 | +35 |
| 31 Oct 2026, 00:28 | 11,904 | +20 |
| 30 Oct 2026, 01:09 | 11,884 | +18 |
| 29 Oct 2026, 04:09 | 11,866 | +20 |
| 28 Oct 2026, 03:26 | 11,846 | +11 |
| 27 Oct 2026, 04:28 | 11,835 | +21 |
| 26 Oct 2026, 05:55 | 11,814 | +16 |
| 25 Oct 2026, 08:05 | 11,798 | +33 |
| 24 Oct 2026, 05:07 | 11,765 | +7 |
| 23 Oct 2026, 05:19 | 11,758 | +16 |
| 22 Oct 2026, 01:50 | 11,742 | first reading |
63 posts held, back to 31 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 57 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 10 November 2026 |
|---|---|
| Posts held | 63 (31 July 2026 – 10 November 2026) |
| Views total | 112,570 |
| Reactions total | 599 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 11 Nov 2026, 08:49 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 11 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.
1,499 reactions across 63 posts, in 16 distinct kinds. The most used accounts for 53.8% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 👍 | 806 | 53.8% | |
| ❤ | 530 | 35.4% | |
| 🔥 | 42 | 2.80% | |
| 👏 | 33 | 2.20% | |
| 😱 | 20 | 1.33% | |
| 🥰 | 19 | 1.27% | |
| 😐 | 11 | 0.734% | |
| 🤔 | 10 | 0.667% | |
| 👀 | 7 | 0.467% | |
| 😍 | 7 | 0.467% | |
| 🥴 | 5 | 0.334% | |
| 🏆 | 3 | 0.2% | |
| 🌭 | 2 | 0.133% | |
| 🤷♂ | 2 | 0.133% | |
| 🤨 | 1 | 0.067% | |
| 🦄 | 1 | 0.067% |
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 63 of the 63 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 1,499 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 63 most recent posts we hold, published 31 July 2026 to 10 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: 0 of 24 posts held from the last 30 days (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).
Photo, posted without a caption
👍17❤4😐4🦄1
已原生适配SuSFS 2.4!! Natively adapted to SuSFS 2.4!!
👍12❤3🔥1
修复 Linux 7.3 及更新内核的 ARM64 系统调用参数跟踪,首个系统调用参数改为从 orig_x0 读取。 修复大于 4 KiB 页大小的 x64 系统中 preinit runner 的 ELF 布局,避免 PID 1 无法加载内置 runner。 重构 selinux_hide 的上下文处理:优先使用当前策略解析一次 setprocattr 输入,仅在需要时回退到备份策略。 修正空白及仅包含换行符的安全上下文处理。 Fix ARM64 syscall argument tracing on Linux 7.3 and newer kernels, reading the first syscall argument from orig_x0. Fix the ELF layout of the preinit runner on x64 systems with page sizes larger than 4 K…
👍11❤4
1.修复模块排序的一些小问题 2.同步上游的SElinux相关的修改 1. Fixed some minor issues with module sorting 2. Synchronized upstream SELinux-related modifications
👍17❤7👏1
1.优化了部分性能和动画 2.ksud添加所有权和部分优化的判断 3.模块和超级用户页面的排序功能改进 1. Optimized some performance and animations 2. Added ownership and partial optimization checks to ksud 3. Improved the sorting function on the modules and superuser pages
❤12👍10
这是非常关键的一次更新,具体更新日志请看https://github.com/LyraVoid/FinaSU/releases/tag/v1.4.2 This is a very important update. For the detailed changelog, please see https://github.com/LyraVoid/FinaSU/releases/tag/v1.4.2
👍18❤3🤔2🥰1😱1
File, posted without a caption
👍44❤5👀2🔥2👏1😱1
每天陪伴你的虚拟形象在此时此刻有了能触碰的感觉,这是神圣一样的感觉,加上这转场动画,简直丝滑,从哪里来就回到哪里去 我们对80%的组件进行了重写,KernelPatch也同步了新的妈妈的味道,这就是FolkPatch 115404---它回来了 The virtual avatar that’s been with you every day now feels like something you can reach out and touch in this very moment—it’s a truly divine feeling. And that transition animation? It’s absolutely buttery smooth. What comes from there goes right back there. We’ve rewritten 80% of the component…
👍25❤8😱3👏1🥰1
FolkPatch has launched a full UI overhaul, which will directly leverage the development experience from FinaSU to upgrade to the latest m3e component library and rewrite all components. FolkPatch 已开始UI全面重构,这次会从FinaSU的开发经验直接升级到最新的m3e组件库并对全部组件重写
👍36🔥7❤4
1.A/B槽位内核版本信息查看 2.适配新的外部Zygisk提供者 3.壁纸模式下的UI优化 1. View kernel version information for A/B slots 2. Adapt to new external Zygisk providers 3. UI optimization in wallpaper mode
👍15❤7
1.修复最新的SElinux检测点 2.Built-In添加新的构建检查ase.apk 1. Fix the latest SELinux checkpoints 2. Add new build checks to Built-In
👍10❤5🤔1
1.添加了挂载点卸载的功能 2.NoMount优化重试和启动逻辑 3.添加更友好的PATH处理 4.SUSFS状态优化 5.修复部分小问题 1. Added mount point unmount functionality 2. NoMount optimized retry and startup logic 3. Added more friendly PATH handling 4. SUSFS status optimization 5. Fixed some minor issues
👍7❤4
Showing the 12 most recent of 63 posts we hold for @FolkPatch. 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 4 posts on @FolkPatch 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.
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 3 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 11 November 2026 — this entry's latest reading, not the date you are reading this.
“FolkPatch” (@FolkPatch), 12,163 subscribers as measured 11 November 2026. Telegram Register, tgregister.com/channel/FolkPatch.
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.