Telegram RegisterThe public register of Telegram
Telegram profile photo for 𝘼𝙣𝙙𝙧𝙤𝙞𝙙-𝘾𝙖𝙢𝙎𝙬𝙖𝙥

Channel

𝘼𝙣𝙙𝙧𝙤𝙞𝙙-𝘾𝙖𝙢𝙎𝙬𝙖𝙥

@CamSwap

On this record: Topic · Growth · Engagement · Reactions · Stars · Posts · Citations · Cite this entry

1,444subscribers

+144 since we began measuring on 25 August 2026

Risers and fallers across the register · movement among entries of 1,000–3,162.

Register entry

Telegram ID-1003736689392
TypeChannel
Username@CamSwap
CreatedBetween 1 February 2026 and 21 March 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded25 August 2026
Last confirmed live19 September 2026
Measurements held8
Confirmed unchanged1 time, most recently 19 September 2026
On Telegramt.me/CamSwap

Topic

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 17 September 2026 and assigned it the closest of 31 fixed categories, at 89% 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

1,3001,4441,37225 August 2026 — 1,300 subscribers26 August 2026 — 1,310 subscribers28 August 2026 — 1,344 subscribers1 September 2026 — 1,364 subscribers5 September 2026 — 1,383 subscribers10 September 2026 — 1,409 subscribers14 September 2026 — 1,423 subscribers19 September 2026 — 1,444 subscribers25 August 202619 September 2026
8 measurements spanning 24 days, net +144. Dots are measurements; the straight line between them is drawn to join them, not to claim we know the path taken in between — snapshots are recorded only when a count changes, so gaps mean “no change observed”, never “interpolated”. The vertical axis spans 1,278–1,466 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
19 Sept 2026, 00:211,444+21
14 Sept 2026, 07:411,423+14
10 Sept 2026, 07:361,409+26
5 Sept 2026, 07:211,383+19
1 Sept 2026, 01:271,364+20
28 Aug 2026, 16:341,344+34
26 Aug 2026, 02:541,310+10
25 Aug 2026, 14:301,300first reading

Engagement

16 posts held, back to 21 March 2026the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 1 page of Telegram’s post history, 20 posts per page.

ERR · 30 days
19.8%
avg views ÷ 1,444 subscribers
Avg views / post
286
4 posts measured
Reaction rate
1.66%
reactions ÷ views · ER floor
Posts in window
4
of 16 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.

What these figures were computed from
WindowRolling 30 days · latest post in window 24 August 2026
Posts held16 (21 March 202624 August 2026)
Views total1,144
Reactions total19
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken25 Aug 2026, 14:30 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.

Reaction mix

131 reactions across 15 posts, in 7 distinct kinds. The most used accounts for 77.9% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
10277.9%
😢118.40%
👍86.11%
👎43.05%
🤯32.29%
🔥21.53%
😍10.763%

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 15 of the 16 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 131 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 16 most recent posts we hold, published 21 March 2026 to 24 August 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 Stars

Stars received
2
across the posts below
Posts paid on
1
of 15 we hold a reading for · 7%
Most on one post
2
single highest reading

A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @CamSwap. Telegram publishes the count on the public post preview alongside ordinary reactions, and this register reads it there. It is the only figure on this site that measures money moving rather than attention.

Stars are not reactions, and the two are never added. They are rendered in the same strip on Telegram and counted in the same shape, but one is a tap and the other is a purchase. The reaction totals and the engagement rate elsewhere on this page exclude every figure in this section, and no rate here is computed against a reaction count.

This is not revenue, and we publish no currency figure. What a Star costs a reader and what it pays a channel are different numbers, Telegram takes a share we cannot observe, and the terms have changed. Converting a Star count into money would be an estimate dressed as a measurement, so the count is where we stop.

Counted over the 16 most recent posts we hold for this entry, published 21 March 2026 to 24 August 2026. Star counts above 1,000 reach us in Telegram’s short form and carry the same three-significant-figure rounding as everything else on this page.

Recent posts

24 Aug 2026, 10:36 UTC256 views2 reactionsread 25 August 2026
File

-Fixed an issue where the log export function failed.

2

24 Aug 2026, 09:53 UTC278 views5 reactionsread 25 August 2026
File

Apologies everyone—while testing the root mode functionality, I discovered quite a few limitations. I likely need more time to look into this, so I don't recommend using it for now. If you have any good ideas, feel free to share them with me. Respect.

👍5

24 Aug 2026, 05:20 UTC309 views8 reactionsread 25 August 2026
File

app-arm64-v8a-debug.apk informal version: 1.adds root mode (suitable for scenarios where the old version of CS cannot be used in some applications.This mode is subject to Android version limitations.) 2.Log output function (su) 3.Some optimizations Thank @Camera168888 Sample provided

8

2 Apr 2026, 15:13 UTC≈2,950 views18 reactionsread 25 August 2026

Just as I fixed a bug and was about to test it on LINE, they banned my account for no reason. (Probably an IP leak.) Looks like LINE users will have to wait a little longer.😅😅

😢117

2 Apr 2026, 01:50 UTCviews —

𝘼𝙣𝙙𝙧𝙤𝙞𝙙-𝘾𝙖𝙢𝙎𝙬𝙖𝙥 pinned «关于如何在issue提交日志: 1.打开LSP框架日志页面 2.右上角点击菜单并点击清空日志 3.复现bug(打开目标App相机) 4.在LSP日志页面右上角菜单点击导出日志 5.在issue详细描述问题并且上传日志zip How to submit logs in an issue: 1. Open the LSP framework log page. 2. Click the menu in the top right corner and select Clear Logs. 3. Reproduce…»

2 Apr 2026, 01:47 UTC≈2,920 views14 reactionsread 25 August 2026

如果你对模块改进有好的想法,欢迎提交PR❤️

12🔥2

2 Apr 2026, 01:44 UTC≈2,900 views2 reactions2 Starsread 25 August 2026

关于如何在issue提交日志: 1.打开LSP框架日志页面 2.右上角点击菜单并点击清空日志 3.复现bug(打开目标App相机) 4.在LSP日志页面右上角菜单点击导出日志 5.在issue详细描述问题并且上传日志zip How to submit logs in an issue: 1. Open the LSP framework log page. 2. Click the menu in the top right corner and select Clear Logs. 3. Reproduce the bug (open the target App's camera). 4. Click the menu in the top right corner of the LSP log page and select Export Logs. 5. Describe the issue in detail in

2

2 Apr 2026, 01:35 UTC≈2,730 views8 reactionsread 25 August 2026

新增悬浮窗功能 修复在 Lsp2.0 上hook失效的问题 修复读取 toast 配置失败的问题 Added floating window feature Fixed the issue where hook fails on Lsp2.0 Fixed the issue where toast configuration reading fails

8

2 Apr 2026, 01:18 UTC≈2,680 views15 reactionsread 25 August 2026
File

File, posted without a caption

15

31 Mar 2026, 09:51 UTC≈2,080 views3 reactionsread 25 August 2026
Forwarded from @LSPosedFile

自 v1.9.2 以来的主要更新: 新增 - 支持 Android 8.1 至 Android 17 Beta 3 - 新增完整的 libxposed API 101 支持 - 新增 miuix 版本管理器并默认启用 - 新增可按应用配置的还原内联钩子功能 - 新增对 libxposed 相关类启用 API 调用保护 - 新增安全模式 - 新增 action.sh 支持,可从 action.sh 打开管理器 - 重构 dex2oat 包装器,支持在 Android 12+ 重新优化系统框架 - 新增 16K page size 支持 - 支持注入系统自定义 resolver 的进程 - 支持重置作用域请求设置 - 支持将日志转发至守护进程 改进 - 大幅度增强对被注入的应用的隐藏能力 - 适配新版 Android 上的反射限制与部分系统行为变化 - 改进软件包与模块解析逻辑 - 优化管理器与服务之间的通信方式,加快启动速度

👍3

26 Mar 2026, 07:56 UTC≈2,820 views12 reactionsread 25 August 2026
File

File, posted without a caption

10👎2

Showing the 12 most recent of 16 posts we hold for @CamSwap. 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.

Stars beside a post are paid reactions — Telegram Stars, bought with money and spent on that post. They are a different unit from reactions and are never added to them, here or anywhere else on this page.

Forward network

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 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.

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.

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 19 September 2026 — this entry's latest reading, not the date you are reading this.

“𝘼𝙣𝙙𝙧𝙤𝙞𝙙-𝘾𝙖𝙢𝙎𝙬𝙖𝙥” (@CamSwap), 1,444 subscribers as measured 19 September 2026. Telegram Register, tgregister.com/channel/CamSwap.

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.