Telegram RegisterThe public register of Telegram

Channel

柑橘味猫窝 — Citrus Channel

@HachimiCat

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

5,452subscribers

-8 since we began measuring on 8 August 2026

Risers and fallers across the register · movement among entries of 3,162–10,000.

Register entry

Telegram ID-1001773672813
TypeChannel
Username@HachimiCat
Description一个隐私保护相关的频道,集互联网资讯、政治新闻和一些有价值的东西于一身。 👥讨论组: @HachimiNeko 请在进入群组之前确保手机号码已隐藏!
CreatedBetween 1 December 2021 and 31 March 2023— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded8 August 2026
Last confirmed live11 August 2026
Measurements held3
Confirmed unchanged1 time, most recently 11 August 2026
On Telegramt.me/HachimiCat

Growth

5,4525,4605,4568 August 2026 — 5,460 subscribers8 August 2026 — 5,460 subscribers11 August 2026 — 5,452 subscribers8 August 202611 August 2026
3 measurements spanning 4 days, net -8. 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 5,451–5,461 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
11 Aug 2026, 12:135,452-8
8 Aug 2026, 08:505,460no change
8 Aug 2026, 00:055,460first reading

Engagement

13 posts held, back to 20 February 2026the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 6 pagesof Telegram’s post history, 20 posts per page.

Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 13 posts for this entry, the most recent from 17 April 2026. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Photos
234
Videos
15
Links
128

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

173 reactions across 8 posts, in 3 distinct kinds. The most used accounts for 57.8% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
10057.8%
👍7241.6%
🌭10.578%

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

Measured over the 13 most recent posts we hold, published 20 February 2026 to 17 April 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

17 Apr 2026, 08:11 UTC≈2,670 views26 reactionsread 12 August 2026
Photo

Telegram突然官方支持中文了,以后不需要第三方中文包了

22👍4

15 Apr 2026, 09:59 UTC≈2,600 views8 reactionsread 12 August 2026

为此,我向Telegram写了一份建议: 关于改进 Secret Chat 功能的建议:跨设备同步与安全备份 亲爱的 Telegram 团队, 作为一名长期支持 Telegram 的忠实用户,我一直非常欣赏你们在产品功能和创新上的努力。 最近,我关注到了 Pavel Durov 在 X(原 Twitter)上对 WhatsApp 端到端加密(E2EE)和云备份缺陷的深刻批评。Pavel 提到,WhatsApp 所谓“默认端到端加密”在绝大多数用户使用明文云备份的情况下形同虚设,这一点我完全赞同。 然而,这场讨论也引来了 MEGA 等其他隐私保护倡导者的审视,并暴露出 Telegram 在 Secret Chat(加密聊天) 功能设计上的一个现实痛点。正如 MEGA 所指出的,虽然 Telegram 拥有顶级的加密技术,但由于 Secret Chat 缺乏跨设备同步能力,且在更换设备时会导致记录永久丢失,这种略显僵化的体

8

15 Apr 2026, 09:59 UTC≈2,390 viewsread 12 August 2026
Photo

Telegram CEO Pavel Durov 炮轰 WhatsApp 的默认端到端加密: WhatsApp 声称的“默认端到端加密”是一个巨大的消费者骗局:WhatsApp 上约 95% 的私人消息最终以明文形式备份在 Apple/Google 服务器上——并非端到端加密。备份加密是可选的,很少有人启用它——更不用说使用强密码了。 即使你使用强密码加密了你的 WhatsApp 备份,你的消息仍然会出现在未加密的云备份中——因为与你发信息的联系人中,有 90% 以上都没有开启备份加密。再加上 WhatsApp 会存储并泄露你的聊天对象信息,情况非常严峻。 Apple 和 Google 每年向第三方披露已备份的 WhatsApp 消息达数千次。与此同时,Telegram 在其 12 年多的历史中,从未泄露过用户消息的任何一个字节。 对此,加密云端储存提供商 MEGA 回复: 他说得没错,但是……如果说 WhatsApp 的

21 Mar 2026, 09:58 UTC≈2,400 views8 reactionsread 12 August 2026

目前最全的Telegram入门教程,需要的宝子赶紧收藏 https://x.com/CitrusHachimi/status/2035286160927597035

👍71

18 Mar 2026, 07:53 UTC≈2,740 views20 reactionsread 12 August 2026

🚨 紧急呼吁:Telegram 私密聊天(Secret Chat)存在严重“吞消息” Bug,需要大家的火力支援! 🚨 频道的朋友们,如果你平时经常使用 Telegram 的端到端加密“私密聊天”功能,请务必注意,目前它存在两个极其坑人的底层同步 Bug: 🐛 Bug 详情还原(触发条件尚不明确): 1. 幽灵卡顿与“时间戳篡改” 当你发送 A 和 B 两条消息时,屏幕显示单勾(已发出/排队中),但对方其实根本没收到。如果过了半小时你再发送消息 C,系统会突然把 A、B、C 顺畅地打包发给对方。最离谱的是,系统会自动把 A 和 B 的发送时间强行篡改成跟 C 一样! 2. 隐形的“已取消”黑洞(单机自嗨) 当你发起私密聊天并连发好几天消息,你这边的界面看起来一切正常,没有任何报错。但其实因为底层的“握手失败”,对方那边的聊天室早就显示“已取消(Canceled)”,根本一条消息都没收到。系统完全不给你任何提示,让你对着空

20

12 Mar 2026, 16:56 UTC≈2,160 viewsread 12 August 2026
Photo

本频道开启了直接私信功能,点击下方按钮即可私信(不欢迎广告骚扰)

9 Mar 2026, 14:35 UTCviews —

柑橘味猫窝 — Citrus Channel pinned «又给Telegram提了一份建议,请大家 点击此处 进入页面点赞支持一下 高危地区用户正在“裸奔”,强烈要求强制开启两步验证! 致 Telegram 安全团队: 我提交这份建议,是为了呼吁官方重视一个极其致命的安全漏洞:在专制国家,由于缺乏强制的两步验证(2FA),大量 Telegram 用户的账号正处于极度危险的“裸奔”状态。 1. 致命弱点:政府拦截短信简直易如反掌 在中国(+86)、俄罗斯(+7)、伊朗(+98)等缺乏言论自由的国家,政府对底层电信运营商拥有绝对的控制权。对于这些国家机器来说,通过…»

9 Mar 2026, 13:27 UTC≈2,430 views30 reactionsread 12 August 2026

又给Telegram提了一份建议,请大家 点击此处 进入页面点赞支持一下 高危地区用户正在“裸奔”,强烈要求强制开启两步验证! 致 Telegram 安全团队: 我提交这份建议,是为了呼吁官方重视一个极其致命的安全漏洞:在专制国家,由于缺乏强制的两步验证(2FA),大量 Telegram 用户的账号正处于极度危险的“裸奔”状态。 1. 致命弱点:政府拦截短信简直易如反掌 在中国(+86)、俄罗斯(+7)、伊朗(+98)等缺乏言论自由的国家,政府对底层电信运营商拥有绝对的控制权。对于这些国家机器来说,通过 SS7 漏洞或直接下令运营商配合来拦截用户的“短信验证码”,没有任何技术门槛。 2. 现状:Telegram 的默认机制让用户暴露在枪口下 目前,用户只需通过短信验证码即可注册并登录 Telegram。官方在注册环节根本没有任何关于“两步验证(云密码)”的强制要求或强烈安全提示。这导致绝大部分缺乏极客安全意识的普通用户

👍30

9 Mar 2026, 09:51 UTCviews —

柑橘味猫窝 — Citrus Channel pinned «给Telegram提了一份建议,请大家 点击此处 进入页面点赞支持一下 强烈建议增加“用户主动发短信”验证,打破 +86 注册死局 致 Telegram 团队: 针对目前向特定地区(特别是中国 +86)用户收取的“强制短信验证码费用”,我发现了一个致命的支付 Bug,并在此提出一个能让 Telegram “零成本”解决问题的替代方案。 1. 核心问题:支付网关是个死胡同 目前,+86 用户被迫支付约 1.50 美元才能接收验证码。但荒谬的是,支付界面被死板地限制为只能输入 16 位数字的卡号。绝大多数中国公民只持有…»

8 Mar 2026, 14:49 UTC≈2,450 views45 reactionsread 12 August 2026

给Telegram提了一份建议,请大家 点击此处 进入页面点赞支持一下 强烈建议增加“用户主动发短信”验证,打破 +86 注册死局 致 Telegram 团队: 针对目前向特定地区(特别是中国 +86)用户收取的“强制短信验证码费用”,我发现了一个致命的支付 Bug,并在此提出一个能让 Telegram “零成本”解决问题的替代方案。 1. 核心问题:支付网关是个死胡同 目前,+86 用户被迫支付约 1.50 美元才能接收验证码。但荒谬的是,支付界面被死板地限制为只能输入 16 位数字的卡号。绝大多数中国公民只持有 19 位卡号的中国银联卡。这个限制导致中国用户在物理层面上根本无法完成支付,直接卡死在注册环节。 2. 负面影响:无意中成为了审查制度的帮凶 通过设置一道中国主流银行卡无法支付的“门槛”,Telegram 正在极大地拉高中国人的翻墙使用成本。这直接把那些拼命寻找安全、无审查平台的普通老百姓拒之门外。这种疏漏

33👍11🌭1

20 Feb 2026, 12:51 UTC≈3,320 views16 reactionsread 12 August 2026
Photo

其他国家有过这样的钓鱼案例

16

Showing the 12 most recent of 13 posts we hold for @HachimiCat. 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 — 402,670 of 1,189,255entries 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.

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

“柑橘味猫窝 — Citrus Channel” (@HachimiCat), 5,452 subscribers as measured 11 August 2026. Telegram Register, tgregister.com/channel/HachimiCat.

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.