Channel
@saveweb
On this record: Growth · Engagement · Reactions · Posts · Polls · Citations · Cite this entry
1,450subscribers
+6 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
| Telegram ID | -1001172185382 |
|---|---|
| Type | Channel |
| Username | @saveweb |
| Created | Between 1 March 2018 and 30 June 2021— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 6 August 2026 |
| Last confirmed live | 13 August 2026 |
| Measurements held | 3 |
| Confirmed unchanged | 2 times, most recently 13 August 2026 |
| On Telegram | t.me/saveweb |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 11 Aug 2026, 00:35 | 1,450 | +5 |
| 7 Aug 2026, 15:30 | 1,445 | +1 |
| 6 Aug 2026, 21:47 | 1,444 | first reading |
18 posts held, back to 4 May 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 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. It is computed over the 2 of 3 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 4 August 2026 |
|---|---|
| Posts held | 18 (4 May 2026 – 4 August 2026) |
| Views total | 1,971 |
| Reactions total | 75 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 6 Aug 2026, 21:47 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.
202 reactions across 12 posts, in 13 distinct kinds. The most used accounts for 47.5% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 6141199163309692841 | 96 | 47.5% | |
| ❤ | 35 | 17.3% | |
| 🎉 | 20 | 9.90% | |
| 😢 | 20 | 9.90% | |
| custom 5174753142851502719 | 7 | 3.47% | |
| 😭 | 6 | 2.97% | |
| 😁 | 5 | 2.48% | |
| 🤯 | 4 | 1.98% | |
| 🤩 | 3 | 1.49% | |
| 🥰 | 3 | 1.49% | |
| 🔥 | 1 | 0.495% | |
| 😱 | 1 | 0.495% | |
| 🥴 | 1 | 0.495% |
Custom emoji. 2 of the rows above are Telegram custom emoji, which the public preview renders as an element carrying only a numeric id — no character, and no image we can reach. The id is printed as-is rather than substituted with a look-alike glyph, because a stand-in would be our invention showing where a measurement should be. The counts beside them areTelegram’s.
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 12 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 202reactions 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 4 May 2026 to 4 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.
https://wikikeeper.saveweb.org/ WikiKeeper 已重新上线。 之前，我们会给目标站点每次 Mediawiki 版本以及 Extensions 变动变动打快照。这个快照机制没有好好优化，导致 227414 个 fandom wikis 每次全站变动会产生 227414 * 220 条记录，最终让数据库大小膨胀到了100+GiB，于是我们临时关了 wikikeeper。 现在数据库大小已优化到 2.5GiB。并且添加了一些新功能： - 可以筛选查看独立 wiki 或者特定的 wiki farm。（fandom 太多了） - Extensions 的总统计默认排除了 wiki farm 的 wikis。 - Stats History 加了 Images 与 Users 的计数，并且加了 <iframe> 便于各位 wiki 站长炫耀自己的 wiki 。
Photo, posted without a caption
custom 614119916330969284145😁5custom 51747531428515027192❤1🥴1
在没人注意到的角落，“永远的” 2010 年网上世博会 www.expo.cn 关站了。不过据说上海世博会博物馆的展厅内仍有本地版，不过据说本地版与在线版有差异，本地版可能缺少一些数据。 关闭理由是 flash 太老了。（当然这个理由咱不认可，你看隔壁 http://www.expo2005.or.jp 不还在线吗）
😢20😱1
https://github.com/saveweb/unwarc 搓了一个新的 WARC Reader 库。
❤2
https://www.nlc.cn/web/yejiefuwu/newtsgj/NLCNetInfoResourcePreservationProtection/index.html 如果大家想知道我们的国家图书馆做 web archive 有多菜，看看这个数据量吧，存这么多年也还是 300TB 出头，不知道在吃什么干饭。看不下去了。 (for English readers: Telegram's auto translation failed to grasp that the post was intended to mock the library)
❤7
无语了，知乎在最近两小时内给我们发了 381 封 spam 。 嗯嗯，知乎你真是太棒了。
custom 614119916330969284139🤯4🤩3
STWP 02026 第 26 周周报 - 修了 gowarc 创建的 zstd frame 不包含 frame_content_size 的问题 https://github.com/internetarchive/gowarc/issues/202 - 向 IIPC 提交了一份利用 zstd 多 frame 以及 zstd seek table skippable frame 的“可加快 zstd warc 遍历 records 时的速度、并支持并行读取多个 records、并且还可稍微提高压缩率、还能便于重放系统按需重放大文件的指定 range 而不用加载并缓存整个 record”的扩展提案。更牛逼的是，此扩展提案甚至是向后兼容的，不会破坏任何现有的 zstd warc parser。https://github.com/iipc/warc-specifications/issues/118 🎉🎉🎉🎉
custom 614119916330969284112❤1
STWP 02026 第 25 周周报 c2026-5: B 站早期(2009-)的很多视频托管在第三方网站上。例如，目前已知有大约 10 万视频曾托管于新浪，且目前新浪的存储桶上仍然有大部分这些视频。 虽然 bilibili 后来将这些第三方源迁移到了自家，但时过境迁，很多视频现在在 bilibili 上也消失了。 新浪云将于今年9月左右关停，这批视频有丢失风险，我们正在开展存档。 熟悉新浪旧 api 以及 bilibili 旧视频的朋友可前往 https://t.me/saveweb_projects/208 讨论。
❤9
未来20年内，SSD 的单位存储价格会降低到比 HDD 还便宜吗？
Shares as published. No per-option vote count is published by Telegram, so none is shown.
STWP 02026 第 24 周周报 - “上架”了一个 12c32g 1Gbps对等的“家里云”。 - 更新了内部的基础设施和服务。 - 另购置了两个 LTO5 驱动器，还未安装。
https://blog.save-web.org/blog/2026/06/15/stwp-02026-05-meetup/
❤1
今天是国际档案日。
❤14🔥1
Showing the 12 most recent of 18 posts we hold for @saveweb. 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.
The poll we hold for this entry, as Telegram rendered it when we read the post. A poll’s figures keep moving after that, so each one is dated.
未来20年内，SSD 的单位存储价格会降低到比 HDD 还便宜吗？
Shares as published. No per-option vote count is published by Telegram, so none is shown.
Percentages only — there are no per-option vote counts here, because Telegram publishes none.The public post preview gives each option’s share and a single voter total, and nothing else. Multiplying one by the other would produce a per-option tally that looks measured and is not: the shares are rounded to whole numbers before we ever see them. We print what was published and leave the column that does not exist empty.
The shares need not add up to 100.Rounding alone puts many polls at 99 or 101. A poll that allows more than one answer per voter runs well past 100 by design, and several here do. The bars are drawn against a fixed 100% track at each option’s own percentage rather than normalised to the total, so a poll that exceeds it shows that it does instead of being quietly rescaled.
Read from the 18 most recent posts we hold, published 4 May 2026 to 4 August 2026. Telegram labels each poll by kind — an anonymous poll, a quiz, a closed set of final results — and that label is reproduced rather than paraphrased.
Citation-graph rank — 499,663 of 1,336,469entries 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.
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.
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 August 2026 — this entry's latest reading, not the date you are reading this.
“Save The Web Project” (@saveweb), 1,450 subscribers as measured 11 August 2026. Telegram Register, tgregister.com/channel/saveweb.
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.