https://github.com/chavyleung/scripts/pull/531
❤1
Signed Senku

Channel
@chavyscripts
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
10,103subscribers
-167 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 10,000–31,623.
| Telegram ID | -1001405837783 |
|---|---|
| Type | Channel |
| Username | @chavyscripts |
| Created | Between 1 March 2019 and 31 October 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 6 August 2026 |
| Last confirmed live | 10 November 2026 |
| Measurements held | 53 |
| Confirmed unchanged | 1 time, most recently 10 November 2026 |
| On Telegram | t.me/chavyscripts |
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 91% 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 |
|---|---|---|
| 10 Nov 2026, 23:39 | 10,103 | -1 |
| 9 Nov 2026, 09:09 | 10,104 | -1 |
| 7 Nov 2026, 20:54 | 10,105 | -2 |
| 6 Nov 2026, 21:34 | 10,107 | -2 |
| 4 Nov 2026, 22:01 | 10,109 | -4 |
| 3 Nov 2026, 19:57 | 10,113 | -1 |
| 2 Nov 2026, 22:26 | 10,114 | -4 |
| 1 Nov 2026, 19:31 | 10,118 | -3 |
| 31 Oct 2026, 17:20 | 10,121 | -3 |
| 30 Oct 2026, 17:46 | 10,124 | +1 |
| 29 Oct 2026, 21:01 | 10,123 | -2 |
| 27 Oct 2026, 23:31 | 10,125 | -3 |
| 26 Oct 2026, 21:31 | 10,128 | -4 |
| 25 Oct 2026, 23:39 | 10,132 | -6 |
| 25 Oct 2026, 00:09 | 10,138 | -2 |
| 24 Oct 2026, 01:19 | 10,140 | -1 |
| 21 Oct 2026, 23:58 | 10,141 | -4 |
| 20 Oct 2026, 17:06 | 10,145 | -3 |
| 19 Oct 2026, 14:20 | 10,148 | -5 |
| 18 Oct 2026, 12:16 | 10,153 | first reading |
18 posts held, back to 21 April 2024 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 54 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 20 October 2026 |
|---|---|
| Posts held | 18 (21 April 2024 – 20 October 2026) |
| Views total | 2,260 |
| Reactions total | 1 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 11 Nov 2026, 10:44 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 3 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.
244 reactions across 16 posts, in 4 distinct kinds. The most used accounts for 53.3% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 130 | 53.3% | |
| 👍 | 95 | 38.9% | |
| 🎉 | 17 | 6.97% | |
| 🤔 | 2 | 0.82% |
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 17 of the 18 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 244 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 18 most recent posts we hold, published 21 April 2024 to 20 October 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 1 post 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).
https://github.com/chavyleung/scripts/pull/531
❤1
Signed Senku
#Relay 1.0.1(build 13) What's New! - 支持纯JSON内容导入订阅(无需订阅 URL,某种程度上也算是匿名订阅) - 结合skill和纯JSON内容内容订阅解决部分用户订阅加载失败及数据问题(部分开发者的订阅格式是非标准写法,Relay 客户端无法做到全部完全兼容) - 一些 UI 细节调整 - 新增意见反馈入口,携带日志发送邮件,快速帮助开发者定位问题 下一个版本将支持: - 自定义壁纸 - 其他 UI 细节调整 #skill - 专门用于创建、检查和修复标准 BoxJS 订阅 JSON,避免因为字段缺失、类型错误或非标准格式,导致 Relay 用户的数据无法正常加载 - 特别适合 BoxJS 订阅作者、脚本开发者以及 Relay 兼容性排查
❤4
Signed Senku
macOS 新建文件夹
❤6
Signed Senku
Video, posted without a caption
👍4❤3
Signed Senku
全新 UI
👍24❤15
Signed Senku
让 AI 写了个 Scritable 的脚本看看 Claude 使用量 地址: https://github.com/gideonsenku/Scriptable/blob/master/ClaudeUsage/claude-usage.js
Signed Senku
同程旅行脚本 /** * * hostname = app.17u.cn * * # Surge * http-request ^https:\/\/app\.17u\.cn\/welfarecenter\/index\/signIndex script-path=https://raw.githubusercontent.com/chavyleung/scripts/master/tongcheng-trip/tongcheng-trip.js, tag=同程旅行 * cron "5 12 * * *" script-path=https://raw.githubusercontent.com/chavyleung/scripts/master/tongcheng-trip/tongcheng-trip.js, timeout=300, tag=同程旅行-签到 * * # QuanX * ^https:\…
❤2👍2🎉1
Signed Senku
https://github.com/chavyleung/scripts/commit/1d691675451bf0416f4e7619c61b2ea057a9fbbd #Scripts 尝试修复智行火车签到
Signed Senku
Jetbrains 全家桶免费一年 活动网址: https://www.jetbrains.com/store/redeem/ 兑换码:DataGrip2025
❤24
Signed Senku
#release 0.19.21 - 修复部分用户订阅超过20导致更新失败 fix(boxjs): 订阅并发控制
❤2
Signed Senku
#书籍推荐 问就是在如何解决内耗 https://www.dev-life.site/
👍7❤1
Signed Senku
#PayPal 刚刚发现 PayPal 偷偷地把 币种兑换 从 通过银行兑换 改成 通过PayPal兑换 这会导致自动付款时多收一笔费用 有用 MasterCard 绑定 PayPal 自动付款的同学尽快检查处理一下
❤13👍2🤔2
Signed Chavy
Showing the 12 most recent of 18 posts we hold for @chavyscripts. 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.
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 9 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 10 November 2026 — this entry's latest reading, not the date you are reading this.
“Chavy Scripts” (@chavyscripts), 10,103 subscribers as measured 10 November 2026. Telegram Register, tgregister.com/channel/chavyscripts.
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.