🚀 v2026.8.1 更新日志 #更新 新增 - 优化前端加载流畅度 - (商业版)注册时支持邮件验证码 修复 - 自定义模板未按预期加载 - (后端)二步认证未按预期关闭 - (后端)更改地区在部分情况下失败 程序升级方法请参阅 “程序升级”。对于分离部署的用户,需同时更新前后端。
Channel
SideCloud Official Channel
@sidecloud
On this record: Growth · Engagement · Posts · Citations · Cite this entry
137subscribers
+1 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
Register entry
| Telegram ID | -1002269558117 |
|---|---|
| Type | Channel |
| Username | @sidecloud |
| Created | Between 1 September 2024 and 31 March 2025— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 August 2026 |
| Last confirmed live | 15 August 2026 |
| Measurements held | 3 |
| Confirmed unchanged | 1 time, most recently 15 August 2026 |
| On Telegram | t.me/sidecloud |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 15 Aug 2026, 20:54 | 137 | +1 |
| 8 Aug 2026, 23:45 | 136 | no change |
| 7 Aug 2026, 14:47 | 136 | first reading |
Engagement
20 posts held, back to 24 February 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 1 pageof Telegram’s post history, 20 posts per page.
- ERR · 30 days
- 20.1%
- avg views ÷ 137 subscribers
- Avg views / post
- 27.5
- 2 posts measured
- Reaction rate
- —
- this channel exposes no reaction counts
- Posts in window
- 2
- of 20 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.
| Window | Rolling 30 days · latest post in window 8 August 2026 |
|---|---|
| Posts held | 20 (24 February 2026 – 8 August 2026) |
| Views total | 55 |
| Reactions total | — |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 8 Aug 2026, 23:45 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.
Recent posts
我们已完成对后端“更改地区失败”问题的修复。 本次仅需更新后端,更新方法请见教程
🚀 v2026.7.2 更新日志 #更新 新增 - 批量添加账号时支持填写前端备注 - 代理 URL 提取后支持用户名密码认证 - 前端备注支持 HTML 格式 - 支持显示和记录账号 iCloud 邮箱 修复 - (商业版)账号停用期间暂停计费,恢复后按停用前剩余有效期继续计算 程序升级方法请参阅 “程序升级”。对于分离部署的用户,需同时更新前后端。
今日上午,邮局服务器域名过滤规则错误过滤了 `qq.com`,导致向 QQ 邮箱发件出现异常。影响时间为北京时间 08:00 至 10:10。 域名过滤规则用于排除临时邮箱及风险域名,以保障发件安全。本次问题由上游规则污染引起,同时我们此前未对常见邮箱域名配置白名单,导致 `qq.com` 被误拦截。 目前我们已完成规则生成逻辑和优先级调整,确保常见邮箱域名优先放行,避免此类问题再次发生。 作为补偿,独享用户将获得 3 天服务时长补偿,共享用户将获得 1 天服务时长补偿。 给大家带来的不便,深表歉意。
🚀 v2026.7.1 更新日志 #更新 新增 - 分享页选择账号支持一键全选 - 账号支持复制新建 优化 - 优化代理池任务成功率UI样式 - 后端优化风控处理,提升任务成功率
由于苹果页面结构发生变动,程序出现了“地区检测失败”的问题。 目前我们已完成修复,请所有用户执行一次后端更新,以确保程序正常运行。 本次仅需更新后端,更新方法请见教程
🚀 v2026.6.2 更新日志 #更新 新增 - 新增代理池任务执行成功率展示,便于实时了解任务运行情况。 - 增强参数校验机制,进一步提升程序运行的安全性与稳定性。 修复 - 修复后端任务部分异常未及时推送至前端的问题,确保检测时间及状态信息能够正确更新。 程序升级方法请参阅 “程序升级”。对于分离部署的用户,需同时更新前后端。
🚀 v2026.6.1 更新日志 #更新 新增 - 邮件解锁支持系统级设置 - 账号API支持搜索功能 - 优化代理并发槽位控制,支持设置并发数量 - 全站自定义footer - 限流时按照重试时间 修复 - 因连接问题造成任务运行失败时,不再显示账号异常 - 修复前端账号页消息字段在窄屏上显示不正常 - 邮件解锁有概率不正常执行 程序升级方法请参阅 “程序升级”。对于分离部署的用户,需同时更新前后端。
🚀 v2026.5.1 更新日志 #更新 新增 - 分享页列表支持按分享页代码搜索 - 账号相关 API 返回前端备注字段 - 出租账号被禁用后自动为用户更换账号(商业版) 修复 - 执行更换地区后,地区在前端显示错误 - 任务日志中 IP 记录错误 程序升级方法请参阅 “程序升级”。
🚀 v2026.4.1 更新日志 #更新 新增 1. 移除代理临时禁用开关,改为代理冷却时间 程序升级方法请参阅 “程序升级”。
版本号命名规则更新公告 为进一步规范版本管理、提升版本信息的可读性与可追溯性,现对版本号命名规则进行说明与统一。 当前版本号采用如下格式: YYYY.M.N 其中: YYYY:表示年份,例如 2026 M:表示月份,例如 4(即4月) N:表示当月发布的第 N 个版本,例如 1 表示该月第一个版本 示例说明: 2026.4.1 表示:2026年4月发布的第1个版本 2026.4.2 表示:2026年4月发布的第2个版本
🚀 v4.2.5 更新日志 #更新 新增 1. 支持BEPusdt支付网关 2. 管理面板支持批量操作账号 3. 优化账号标签选择样式 4. 管理面板显示用户账号数量 5. 新增Admin API,可用于重启任务。更多操作待后续补充。 6. 后端新增资源缓存,可节省50%以上流量。 修复 1. 使用非授权域名访问分享页时,验证码无法正常加载 2. 修改地区功能无法正常使用 程序升级方法请参阅 “程序升级”。对于分离部署的用户,需同时更新前后端。
Showing the 12 most recent of 20 posts we hold for @sidecloud. 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
Citation-graph rank — 495,619 of 1,481,346entries 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.
Forward network
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.
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 15 August 2026 — this entry's latest reading, not the date you are reading this.
“SideCloud Official Channel” (@sidecloud), 137 subscribers as measured 15 August 2026. Telegram Register, tgregister.com/channel/sidecloud.
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.