Telegram RegisterThe public register of Telegram

Channel

arrio的杂物堆

@arrio_pod

On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry

9subscribers

+0 since we began measuring on 6 August 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1002079346419
TypeChannel
Username@arrio_pod
Description有空再写~
CreatedBetween 1 November 2023 and 31 May 2024— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded12 August 2026
Last confirmed live12 August 2026
Measurements held2
On Telegramt.me/arrio_pod

Growth

96 August 2026 — 9 subscribers12 August 2026 — 9 subscribers6 August 202612 August 2026
2 measurements spanning 6 days. Dots are measurements; the straight line between them is drawn to join them, not to claim we know the path taken in between — snapshots are recorded only when a count changes, so gaps mean “no change observed”, never “interpolated”. The vertical axis spans 8–10 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
12 Aug 2026, 10:499no change
6 Aug 2026, 16:139first reading

Engagement

20 posts held, back to 8 May 2026the 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
63.9%
avg views ÷ 9 subscribers
Avg views / post
5.8
4 posts measured
Reaction rate
this channel exposes no reaction counts
Posts in window
4
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.

What these figures were computed from
WindowRolling 30 days · latest post in window 3 August 2026
Posts held20 (8 May 20263 August 2026)
Views total23
Reactions total
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken12 Aug 2026, 10:49 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.

What this channel posts

Photos
150
Videos
3
Links
229

Lifetime counters from Telegram’s own channel header, read 12 August 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.

Reaction mix

3 reactions across 3 posts, in 2 distinct kinds. The most used accounts for 66.7% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
👍266.7%
133.3%

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 3 of the 20 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 3reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 20 most recent posts we hold, published 8 May 2026 to 3 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.

Recent posts

3 Aug 2026, 03:47 UTC5 viewsread 12 August 2026
Forwarded from @rynif

https://x.com/AkasakaRentsuki/status/2083563594613215497

29 Jul 2026, 11:55 UTC6 viewsread 12 August 2026
Forwarded from @prdm_thoughts

书接上文。AI对公安和Staatssicherheit工作真正的影响是什么呢。 AI真正的大问题之一,它是回音壁(echo chamber),哪怕你通过提示词让AI跟你展开精神分析和自我批评,按目前训练的风格他就是会align到人类,会刻意去迎合你的,而显然,越垃圾的AI,它就越迎合你。遑论更多使用AI(豆包)的人根本意识不到这一点,他觉得这是个助手,可能有点像给领导开车的司机或者大秘的角色,搁那聊,给自己聊进去了。对于ego稍微大点的人(尤其是各类领导),这种激化放大个人意见巩固自信的效应会更加增强。 那对于本身精神状态就异乎常人的用户,比如本来就玉玉的小孩,比如反人类人格有杀心的用户,AI的道德围栏的优先级是远小于遵从用户的优先级的,最后确实可能导致异常情况会被放大。 再比如在国内企业从事AI safety工作的读者应该知道,今年有司也重点排查了情感陪伴类的AI,懂的都懂。并不是说对AI产生情感陪伴依赖是错误的,但是我们整个

29 Jul 2026, 11:49 UTC4 viewsread 12 August 2026
Forwarded from @prdm_thoughts

A\的一项丰功伟绩是把AI safety、AI security和AI for security三件事情混为一谈,然后再把这个混杂的概念当成excuse。然后这种坏习惯传染到了一整个学术圈。 safety是对你使用过程中保持稳态的担保,你正常开着AI不会给你文件全删了是safety,AI不去帮你主动下单海量切糕导致家破人亡是safety。 security则是一定围绕攻防展开讨论的(保安说是),基础设施被日了模型被偷了agent被提示词注入了这叫ai security,而你拿ai去给fastjson一秒三棍出0day,这是ai for security。 但在A\那儿这几个词是混为一谈的,包括但不限于滥用red team这个概念,只要逼模型输出unwanted output都叫red team,嚯嚯嚯,红队是这么好当的哦。 所以Amodei一开始就想给大家卖的恐慌是AI for state security,嗯吹CBRN。但一个

26 Jul 2026, 09:50 UTC8 viewsread 12 August 2026

知乎内容已发布到 Telegraph: https://telegra.ph/说一下你们为什么渐渐不玩游戏了-07-26

10 Jul 2026, 13:51 UTC11 viewsread 12 August 2026
Forwarded from @zhihu_bazaar

为什么“旧金山”的译名流传了下来,但“新金山”(墨尔本)则没有? | 原文

3 Jul 2026, 04:31 UTC12 viewsread 12 August 2026
Forwarded from @hacker_news_zh

现实拥有惊人数量的细节 (2017) 原文:https://johnsalvatier.org/blog/2017/reality-has-a-surprising-amount-of-detail 阅读时间:8 分钟 分数:182

1 Jul 2026, 05:34 UTC10 viewsread 12 August 2026
Forwarded from @var_log_ciel

https://soaked.in/2026/06/deng/ 文章分享

17 Jun 2026, 18:50 UTC12 viewsread 12 August 2026

知乎内容已发布到 Telegraph: https://telegra.ph/如何评价新番躲在超市后门吸烟的二人-06-17

16 Jun 2026, 06:46 UTC9 views1 reactionsread 12 August 2026
Forwarded from @laozhoubuluo_opcenter

闲鱼码 千问壳 支付宝付款:用平台信任拼出一条诈骗链 ▎Source

1

10 Jun 2026, 09:35 UTC12 views1 reactionsread 12 August 2026
Forwarded from @ilharperPhoto

bryanwangxin/2064309590414836085 苹果的发布会视频中,但凡有说到 Siri 的地方,都会切掉音频中 3k、4k、5k、6kHz 频率部分,以防观看视频时附近的苹果设备激活 Siri。

👍1

1 Jun 2026, 11:52 UTC17 views1 reactionsread 12 August 2026

#剪切板 今天是儿童节,为什么要哭呢,​这不是你梦寐以求的长大​吗?​

👍1

31 May 2026, 06:07 UTC16 viewsread 12 August 2026
Forwarded from @rvalue_dailyPhoto

:但为什么我周围到处都是会全世界东西的人(

Showing the 12 most recent of 20 posts we hold for @arrio_pod. 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 — 631,872 of 1,169,250entries 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.

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.

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 12 August 2026 — this entry's latest reading, not the date you are reading this.

“arrio的杂物堆” (@arrio_pod), 9 subscribers as measured 12 August 2026. Telegram Register, tgregister.com/channel/arrio_pod.

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.