Photo, posted without a caption
🤓4
Signed ☁️𝐄𝐥𝐯𝐢𝐧 𝐒𝐭𝐚𝐫𝐫𝐲☁️

Channel
@acgdaily
On this record: Topic · Observations · Channels linked by matching posts · Growth · Engagement · What this channel posts · Reactions · Stars · Posts · Citations · Handles named that no longer answer · Telegram's recommendations · Cite this entry
17,363subscribers
+1,267 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 10,000–31,623.
| Telegram ID | -1001494646462 |
|---|---|
| Type | Channel |
| Username | @acgdaily |
| Description | 梗图/沙雕/新闻/锐评/废物大赏/二次元 有啥发啥 内容不保真 请自行鉴定 尽情品味 祝各位群友吃瓜愉快 转发请保留来源 公告栏 https://t.me/acgdaily/6801 入群指南 https://t.me/acgdaily/33934 |
| Created | 26 June 2020 — measured — cross-checked against a third-party dataset (ext.tg_channel) |
| First recorded | 6 August 2026 |
| Last confirmed live | 15 November 2026 |
| Measurements held | 66 |
| Confirmed unchanged | 1 time, most recently 15 November 2026 |
| On Telegram | t.me/acgdaily |
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 10 September 2026 and assigned it the closest of 31 fixed categories, at 85% 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.
These are measurements, not verdicts. Each one below states something we counted, alongside the evidence it was counted from, so you can check it rather than take it. None of them is graded: every observation this register holds is recorded at severity 0, because the precision of the detectors behind them has not been measured yet, and a rating we cannot support is worse than none. Read each as a fact about the data, not as a judgement about the channel. How we measure.
Posts published here appear in near-verbatim form on 7 other registered channels. This entry also forms a group of 2 channels linked by matching posts. The matching is on the text itself, not on Telegram’s forward marker, so it finds a copy whether or not it was labelled as one.
| Posted first | Then | Overlap | Gap |
|---|---|---|---|
| @zaihuapd/4308510 Aug 2026, 03:11 UTC | @acgdaily/55863 · this entry10 Aug 2026, 03:12 UTC | 1.00 | 72 seconds |
| @zaihuapd/4328220 Aug 2026, 00:53 UTC | @acgdaily/56453 · this entry20 Aug 2026, 06:19 UTC | 1.00 | 5.4 hours |
| @zaihuapd/4333122 Aug 2026, 15:40 UTC | @acgdaily/56574 · this entry22 Aug 2026, 15:59 UTC | 1.00 | 19 minutes |
| @zaihuapd/4344927 Aug 2026, 05:40 UTC | @acgdaily/56796 · this entry27 Aug 2026, 05:41 UTC | 1.00 | under a minute |
| @zaihuapd/448582 Nov 2026, 15:12 UTC | @acgdaily/60187 · this entry2 Nov 2026, 18:06 UTC | 1.00 | 2.9 hours |
| @zaihuapd/449285 Nov 2026, 03:04 UTC | @acgdaily/60246 · this entry5 Nov 2026, 03:19 UTC | 1.00 | 15 minutes |
| Channel | Matching posts | Text overlap | Typical gap | Published first |
|---|---|---|---|---|
| @zaihuapd | 43 (8/8 hand-verifiable sample passed) | 1.00 | 23 minutes | @zaihuapd (43–0) |
| @GodlyNews1 | 9 (8/8 hand-verifiable sample passed) | 1.00 | 22 minutes | @GodlyNews1 (9–0) |
| @bakaPD | 13 (8/8 hand-verifiable sample passed) | 1.00 | 31 minutes | @bakaPD (8–5) |
| @xhqcankao | 27 (8/8 hand-verifiable sample passed) | 1.00 | 10 minutes | @xhqcankao (27–0) |
| @DNSPODT | 12 (7/8 hand-verifiable sample passed) | 1.00 | 10 minutes | @DNSPODT (12–0) |
| @CE_Observe | 11 (8/8 hand-verifiable sample passed) | 1.00 | 5 minutes | @CE_Observe (11–0) |
| @abcthoughts | 7 (7/7 hand-verifiable sample passed) | 1.00 | 12 minutes | @abcthoughts (5–2) |
Text overlap is the Jaccard coefficient over the set of distinct three-word phrases in the two bodies: 1.00 is identical wording, and the threshold for counting a pair at all is 0.70. Candidates are generated by simhash LSH (4 x 16-bit bands, exact Hamming <= 3) verified against the bodies with Jaccard over the SET of distinct 3-word shingles. Published first counts which side of each matching pair carries the earlier timestamp — in this corpus, which is the limitation directly below.
What this cannot establish
MEASURED, DOMINANT ERROR SOURCE: a post ingested before 2026-08-06 may have carried a forward header that was not recorded. A 45-pair hand-check against live t.me pages found 14 (31%) where the live page shows a forward header naming the other channel and the database has none, plus 4 more (9%) naming a third party. The text match itself was wrong 0 times out of 45. Read attribution_capture.items_in_trusted_window before treating the unattributed count as a claim.
Telegram lets a channel forward a post with a header naming the source, and we only began reliably recording that header on 2026-08-06. 65 of the 65 matches recorded here fall after that date and carried no header when we read them. The rest predate reliable capture and are not evidence either way.
“Published first” means first in this corpus. We hold 308 comparable posts for this entry, running 6 August 2026 to 15 November 2026. A channel we have read one page deep will look younger than a neighbour we have read in full, and the order would flip with no change in the underlying facts.
The detector’s own notes on this observation, as it recorded them. Names in this_style are fields of the underlying evidence record, which the plain-English paragraphs above read out for this entry.
Of the group of 2 channels, the one whose matching posts we hold earliest is @acgdaily — which is this entry. That is a statement about our reading window, not a claim of authorship.
Recorded under the keys clone_copy · clone_mutual, last confirmed 16 November 2026. An observation that a later pass no longer finds is cleared, and a cleared observation is removed from this page rather than being shown struck through — we do not keep publishing a claim we have withdrawn. Dispute an observation.
This channel is in a group of 2 registered channels linked by matching posts. Links are found by comparing text fingerprints across every channel on the register.
Which channel, if either, published first is deliberately not shown in this list. “First” could only mean first in our own crawl, which depends on how deep we happened to reach into each channel’s history, not on when the content was actually first posted. Our one hand-check read 45 of the highest-confidence flagged pairs against the live Telegram pages. In 18 of them the live page showed a “Forwarded from” credit that our database had no record of, so reading that pair as an unattributed copy was wrong; the check did not measure who published first. This list is ordered by subscriber count, the same as every other listing on this site, never by which channel we think came first. Near-verbatim matching has several ordinary explanations besides copying — a channel mirroring itself, an unattributed repost, or two channels independently repeating the same wire story — and this measurement cannot tell those apart. How this is measured.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 15 Nov 2026, 00:58 | 17,363 | +34 |
| 12 Nov 2026, 01:41 | 17,329 | +20 |
| 10 Nov 2026, 04:08 | 17,309 | +12 |
| 8 Nov 2026, 15:56 | 17,297 | +24 |
| 7 Nov 2026, 09:58 | 17,273 | +23 |
| 6 Nov 2026, 09:18 | 17,250 | +19 |
| 5 Nov 2026, 12:26 | 17,231 | +12 |
| 4 Nov 2026, 11:36 | 17,219 | +9 |
| 3 Nov 2026, 10:39 | 17,210 | +9 |
| 2 Nov 2026, 08:46 | 17,201 | +14 |
| 1 Nov 2026, 06:08 | 17,187 | +9 |
| 31 Oct 2026, 09:35 | 17,178 | +12 |
| 30 Oct 2026, 10:07 | 17,166 | +10 |
| 29 Oct 2026, 11:38 | 17,156 | +8 |
| 28 Oct 2026, 07:40 | 17,148 | +14 |
| 27 Oct 2026, 09:16 | 17,134 | +19 |
| 26 Oct 2026, 10:56 | 17,115 | +14 |
| 25 Oct 2026, 09:34 | 17,101 | +15 |
| 24 Oct 2026, 06:40 | 17,086 | +13 |
| 23 Oct 2026, 10:06 | 17,073 | first reading |
1,100 posts held, back to 6 August 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 79 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. It is computed over the 290 of 359 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 16 November 2026 |
|---|---|
| Posts held | 1,100 (6 August 2026 – 16 November 2026) |
| Views total | 210,357 |
| Reactions total | 4,026 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 16 Nov 2026, 05:39 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 16 November 2026 — not the date at the top of this page, which is when the subscriber count was last read. A count marked ≈ was rounded by Telegram before we ever saw it — t.me prints these counters in full below 1,000 and to three significant figures above, so ≈142,000 means somewhere between 141,500 and 142,499.
Measured directly from 24 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.
10,290 reactions across 731 posts, in 44 distinct kinds. The most used accounts for 35.7% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 😁 | 3,672 | 35.7% | |
| 🤣 | 1,119 | 10.9% | |
| 👍 | 1,048 | 10.2% | |
| 🤡 | 739 | 7.18% | |
| 🥰 | 524 | 5.09% | |
| 😭 | 352 | 3.42% | |
| 🤯 | 349 | 3.39% | |
| ❤ | 268 | 2.60% | |
| 🌚 | 239 | 2.32% | |
| 🖕 | 215 | 2.09% | |
| 😱 | 202 | 1.96% | |
| 🔥 | 191 | 1.86% | |
| 😇 | 170 | 1.65% | |
| 😢 | 154 | 1.50% | |
| 😨 | 147 | 1.43% | |
| 😡 | 102 | 0.991% | |
| 🐳 | 98 | 0.952% | |
| 💊 | 97 | 0.943% | |
| 🤔 | 73 | 0.709% | |
| ⚡ | 71 | 0.69% | |
| 24 further kinds | 460 | 4.47% |
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 752 of the 1,000 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 10,290 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 1,000 most recent posts we hold (the sample is capped at 1,000), published 9 August 2026 to 16 November 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.
A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @acgdaily. 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 1,000 most recent posts we hold for this entry (the sample is capped at 1,000), published 9 August 2026 to 16 November 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.
Telegram’s own ‘edited’ marker: 17 of 359 posts held from the last 30 days (4.74%) 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).
Photo, posted without a caption
🤓4
Signed ☁️𝐄𝐥𝐯𝐢𝐧 𝐒𝐭𝐚𝐫𝐫𝐲☁️
无法接受黄仁勋离开,英伟达机器人研究工程师宣布辞职 11 月 16 日,英伟达机器人研究工程师 Darrell Dai 昨日发布公开信称已决定辞职。其表示,「作为英伟达的一名机器人工程师,我眼中的黄仁勋,远不止是公司的首席执行官。我敬佩他愿意为尚不明朗的未来投入资源。早在深度学习热潮到来之前,他就坚定地押注 CUDA,并在人工智能成为所有人的优先事项之前,就为英伟达布局了这一领域。这些决策帮助构建了支撑当今人工智能的基础设施。」 关于离职原因,Darrell Dai 称「我并不掌握与指控有关的全部事实,也无法对调查结果预先作出判断。我对黄仁勋的敬佩,并不意味着他可以免受审视。我难以接受的是,在得到有助于我理解的解释之前,就不得不接受他离开的事实。这对我来说,意味着我们的方向、我们的文化,以及那些实际开展工作的人,都将面临怎样的变化,目前仍不清楚。」 信源 动察 Beating 频道 · 动察 Beating 交流群
👍8😇7
Signed ☁️𝐄𝐥𝐯𝐢𝐧 𝐒𝐭𝐚𝐫𝐫𝐲☁️
DeepSeek算力吃紧:长对话、单次输入、每日使用量开始全面受限,疑似酝酿付费套餐 DeepSeek 开始限制免费聊天服务。多名用户发现,DeepSeek App 和网页端不再支持超过 7 天未互动的长对话。单次输入上限缩短至约 4 万字,每日对话也开始设置额度,用完后会提示「因服务器繁忙,使用额度已达上限」。 前两天就有开发者发现,DeepSeek 网页前端新增了一整套额度管理代码。它能每隔 5 分钟同步各模型的剩余额度,并在额度耗尽后显示提醒。代码还出现了名为「Coding Plan」的套餐,引发了 DeepSeek 即将推出个人付费订阅的猜测。 DeepSeek 刚在 11 月 13 日开放了联网搜索、文件读取、语音等应用 API,还开源了支持导入历史对话的演示客户端。受到影响的用户可以导出原有聊天记录,再通过这个客户端导入并继续对话,API 调用按实际用量付费。 目前,DeepSeek 尚未公布具体的每日使用额…
👍2
Signed ☁️𝐄𝐥𝐯𝐢𝐧 𝐒𝐭𝐚𝐫𝐫𝐲☁️
Photo, posted without a caption
😁11🎉2🤡2
Signed ☁️𝐄𝐥𝐯𝐢𝐧 𝐒𝐭𝐚𝐫𝐫𝐲☁️
File, posted without a caption
Signed ☁️𝐄𝐥𝐯𝐢𝐧 𝐒𝐭𝐚𝐫𝐫𝐲☁️
墙内还是老套路,没有新意地开始删帖、并买水军洗地了。 另外,新成语来临:占三退一,意思是占了三米退了一米。
😁11
黄仁勋被曝想重掌英伟达:硅谷大佬帮忙游说,近17万人撑腰 据《金融时报》报道,黄仁勋已和身边人谈过回去继续当 CEO 的事。一名盟友透露,他们正召集硅谷高管,准备成立一个专门推动黄仁勋复职的「战情室」,游说英伟达董事会,还打算争取白宫支持。 这名人士说:「除了那些前沿 AI 实验室,科技圈里有头有脸的人都喜欢黄仁勋。」他还透露,黄仁勋本人也支持这场复职行动。不过,黄仁勋尚未亲自公开表态。 支持者发起的 Stand with Jensen 联署网站也越来越热闹,签名已经飙升至 16.7 万份。其中约 8200 人自称英伟达现任员工,接近公司员工总数的五分之一。 马斯克、Epic Games CEO Tim Sweeney 等科技圈人物也公开支持黄仁勋回归。联署信要求董事会先恢复黄仁勋的职务,等独立调查查清事实后再作决定,并向员工和股东解释为何让这位执掌公司 33 年的创始人离开。 不过,英伟达董事会面临的压力不止来自硅谷…
😁10🤡2❤1
Signed ☁️𝐄𝐥𝐯𝐢𝐧 𝐒𝐭𝐚𝐫𝐫𝐲☁️
Balaji:黄仁勋只需公开表态希望复任英伟达CEO,整个AI行业都将支持其回归 11 月 16 日,前 Coinbase 首席技术官、天使投资人 Balaji Srinivasan 发文声援黄仁勋,称只要黄仁勋公开表示希望重新担任英伟达 CEO,相关人事变动就会迅速启动。他认为,英伟达及全球 AI 产业仍高度依赖黄仁勋,所谓针对他的「董事会政变」缺乏正当性,反对其回归的董事可能被迫辞职或通过法律程序被罢免。 Balaji 还援引英伟达公司章程称,持有至少 15% 投票权并持续满一年的股东,可以要求召开特别股东大会,推动罢免现任董事并选举新董事会。他同时呼吁特朗普介入,认为将黄仁勋排除在英伟达之外不利于美国维持 AI 领域的领先地位。 Balaji 将针对黄仁勋的间谍指控称为虚假叙事,并表示科技行业大多数人士仍支持黄仁勋回归。上述内容为 Balaji 的个人观点,其关于董事会罢免程序及相关指控的说法尚待核实。 信源 动…
😁14🥰2🤡1
Signed ☁️𝐄𝐥𝐯𝐢𝐧 𝐒𝐭𝐚𝐫𝐫𝐲☁️
Qwen4-Max正式发布:主干规模不变,激活参数减少25%,任务成本下降62% 继上周开放预览版后,阿里正式发布新一代旗舰模型 Qwen4-Max,公布完整技术架构、评测成绩及 API 定价。 Qwen4-Max 延续上一代 2.4 万亿参数的主干规模,额外引入 3280 亿 N-gram Embedding 参数。通过重新设计注意力机制、残差连接和词组嵌入层,每次生成 Token 激活的主干参数从约 950 亿降至 710 亿,减少约 25%。模型支持原生视觉理解和 100 万 Token 上下文。 官方评测显示,Qwen4-Max 在专业工作基准 Work360 上获得 52.69 分,上一代为 47.74 分。这套阿里自建的评测覆盖金融、法律、制造业等专业任务。在 Terminal-Bench 4.0 编程测试中,新模型的 Token 消耗比上一代减少约 48% 至 49%。Work360 的平均单任务成本则从 4…
👍4
Signed ☁️𝐄𝐥𝐯𝐢𝐧 𝐒𝐭𝐚𝐫𝐫𝐲☁️
deepseek客户端文档输入限制为10k Token 暂时降级为梁西匹
😁27
Signed ☁️𝐄𝐥𝐯𝐢𝐧 𝐒𝐭𝐚𝐫𝐫𝐲☁️
Photo, posted without a caption
😁9
黄仁勋正考虑重返英伟达担任CEO。黄仁勋在硅谷的盟友正在向英伟达董事会施压,要求恢复他的职务。他们表示,正在组建一个由硅谷企业高管组成的“战情室”,以游说推动黄仁勋重返公司,并将努力争取白宫方面的支持。 来源:外汇交易员
👍12🤓7
Signed ☁️𝐄𝐥𝐯𝐢𝐧 𝐒𝐭𝐚𝐫𝐫𝐲☁️
Showing the 12 most recent of 1,100 posts we hold for @acgdaily. 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.
Republishes
Channels on the register whose posts this channel has forwarded.
Republishes 85 registered channels. The 48 listed are the ones this channel has forwarded most; the rest are counted here but not each listed.
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 5 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.
Names
Channels on the register whose handles appear in this channel's posts.
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.
@acgdaily named 4 handles that resolve to nothing today. That is a fact about the reference, not necessarily a fact about the handle’s history — see the two groups below.
Most of these may never have existed as a live channel at all. A handle a channel names can be a typo, an aspirational name nobody registered, or a channel that was already gone before this one ever mentioned it. Unless a row below is marked evidenced, all we know is that it references a handle that is not a live channel today — not that anything “died”. How this is measured.
We ourselves saw each of these resolve to a real page at some point before it went vacant — a genuine, evidenced change, not an inference from absence.
References a handle that is not a live channel — we have no record it ever was one.
The reverse of the list above, and a different kind of signal. This does not require this channel to have ever been asked about directly — each row below is a channel we DID ask Telegram about, whose Telegram-generated list happened to include this one. A channel can appear here with an empty list above it, because being named by someone else’s query is independent of having been queried itself.
This channel appears in 42 seed channels' Telegram-generated recommendation lists in total, of which the 24 where it ranks highest are shown above. Each is Telegram’s list for THAT channel, not this one — see how this is measured.
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 November 2026 — this entry's latest reading, not the date you are reading this.
“2.5次元日常 🍉” (@acgdaily), 17,363 subscribers as measured 15 November 2026. Telegram Register, tgregister.com/channel/acgdaily.
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.