版本号:3.26.08011308 更新内容: * 优化工作流文件 #阅读 #Legado #阅读Sigma #beta
👏14

Channel
@readsigma
On this record: Growth · Engagement · Reactions · Posts · Citations · Cite this entry
1,747subscribers
+32 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
| Telegram ID | -1003460752608 |
|---|---|
| Type | Channel |
| Username | @readsigma |
| Created | Between 1 November 2025 and 16 March 2026— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 13 August 2026 |
| Measurements held | 4 |
| Confirmed unchanged | 1 time, most recently 13 August 2026 |
| On Telegram | t.me/readsigma |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 13 Aug 2026, 12:29 | 1,747 | +10 |
| 10 Aug 2026, 20:42 | 1,737 | +20 |
| 7 Aug 2026, 23:53 | 1,717 | +2 |
| 7 Aug 2026, 10:47 | 1,715 | first reading |
18 posts held, back to 16 March 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 2 pagesof 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 1 August 2026 |
|---|---|
| Posts held | 18 (16 March 2026 – 1 August 2026) |
| Views total | 3,070 |
| Reactions total | 16 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 7 Aug 2026, 17:41 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.
85 reactions across 14 posts, in 4 distinct kinds. The most used accounts for 63.5% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 54 | 63.5% | |
| 👍 | 16 | 18.8% | |
| 👏 | 14 | 16.5% | |
| 👎 | 1 | 1.18% |
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 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 85reactions 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 16 March 2026 to 1 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.
版本号:3.26.08011308 更新内容: * 优化工作流文件 #阅读 #Legado #阅读Sigma #beta
👏14
版本号:3.26.07240951 更新内容: * [优化]:上个pr代码可读性 #阅读 #Legado #阅读Sigma #beta
❤2
版本号:3.26.07152326 更新内容: * [修复]:口令导入识别处理的一种意外情况 #阅读 #Legado #阅读Sigma #beta
❤3
版本号:3.26.07152258 更新内容: **2026/07/15** - 新增导出链接为口令、自动识别口令导入 #阅读 #Legado #阅读Sigma #beta #plus
❤2
版本号:3.26.07152204 更新内容: * [优化]:口令识别导入时机 #阅读 #Legado #阅读Sigma #beta
版本号:3.26.07141221 更新内容: * [功能]:源导入导出支持口令分享 #阅读 #Legado #阅读Sigma #beta
👍6
版本号:3.26.07131406 更新内容: * [优化]:优化恢复备份入口(删除阅读2.0数据恢复入口) #阅读 #Legado #阅读Sigma #beta
❤5
版本号:3.26.07122232 更新内容: * [修复]:剔除 librtmp-jni.so 以支持 16KB 页面对齐 (#442) #阅读 #Legado #阅读Sigma #beta
👍7
【助眠游戏-爱丽丝疯狂回归-哔哩哔哩直播】 https://b23.tv/b9SVabG 养病玩游戏的日子
❤1
版本号:3.26.07042345 更新内容: 2026/07/04 - 链接规则支持head类型 - 回调事件支持详情页点击标签 - 详情页简介图片支持执行js,支持长按查看 - 优化web端加载段评图片 - 详情页简介支持用web渲染 - 调整新用户预加载和搜索线程的默认值 - 其余优化与修复 详细介绍 #阅读 #Legado #阅读Sigma #beta #plus
❤18👍3
版本号:3.26.07041844 更新内容: * [优化]:更新内置订阅源 * [优化]:调整默认预下载设置值为2 * [优化]:调整默认搜索线程设置值为32 #阅读 #Legado #阅读Sigma #beta
❤6
版本号:3.26.07031556 更新内容: * [调整]:更新仓库readme * [优化]:同步原版最后的优化 #阅读 #Legado #阅读Sigma #beta
❤14
Showing the 12 most recent of 18 posts we hold for @readsigma. 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.
Citation-graph rank — 996,537 of 1,478,351entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
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.
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 13 August 2026 — this entry's latest reading, not the date you are reading this.
“阅读Sigma” (@readsigma), 1,747 subscribers as measured 13 August 2026. Telegram Register, tgregister.com/channel/readsigma.
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.