Telegram RegisterThe public register of Telegram

Channel

整点猫咪Channel

@GetMoeCats

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

4,273subscribers

+0 since we began measuring on 9 August 2026

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

Register entry

Telegram ID-1001785776596
TypeChannel
Username@GetMoeCats
CreatedBetween 1 December 2021 and 31 March 2023— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded9 August 2026
Last confirmed live10 August 2026
Measurements held2
Confirmed unchanged1 time, most recently 10 August 2026
On Telegramt.me/GetMoeCats

Growth

4,2739 Aug 2026, 17:31 — 4,273 subscribers10 Aug 2026, 02:12 — 4,273 subscribers9 Aug 2026, 17:3110 Aug 2026, 02:12
2 measurements taken within a single day. 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 4,269–4,277 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
10 Aug 2026, 02:124,273no change
9 Aug 2026, 17:314,273first reading

Engagement

16 posts held, back to 11 September 2025the 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
28.8%
avg views ÷ 4,273 subscribers
Avg views / post
1,230
4 posts measured
Reaction rate
0.387%
reactions ÷ views · ER floor
Posts in window
4
of 16 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. It is computed over the 2 of 4 measured posts that carry a reaction reading, and over those same posts' views.

What these figures were computed from
WindowRolling 30 days · latest post in window 3 August 2026
Posts held16 (11 September 20253 August 2026)
Views total4,920
Reactions total8
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken9 Aug 2026, 17:31 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.

Reaction mix

87 reactions across 13 posts, in 8 distinct kinds. The most used accounts for 35.6% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
3135.6%
👎1618.4%
👍1213.8%
🤡1112.6%
🤮910.3%
😁55.75%
🔥22.30%
👏11.15%

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

Measured over the 16 most recent posts we hold, published 11 September 2025 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, 09:17 UTC515 views6 reactionsread 9 August 2026
Forwarded from @GetSomeFriesChannel

 iRingo: 🌤 WeatherKit v3.2.0 已发布 Created by @V_Clyne & @WordlessEcho & @001 & @Larry052210 Available in 🎈Loon(推荐), 🐿️Egern(推荐), 📈Surge(😁), 🏂Stash, 🚀Shadowrocket(仅 Rewrite 版), 🌀Quantumult X(仅本地版) Only for iOS 18, macOS 15, watchOS 11 or later What's New? 1. 云函数版可以同时在 workers 与 pages 部署了; 2. 新的 Rewrite 版(云函数版)提供 endpoint 设置,用户可根据需求进行切换; 3. 对天气预警数据的填补及页面修复,QWeather 第三方的天气预警页面现在被苹果官方页面接管; 4. 为了此项目的长期发展,实现了 flatbuffer

6

31 Jul 2026, 06:12 UTC795 viewsread 9 August 2026
Forwarded from @ibilibili

Loon的插件即将迎来一波大更新 新的复写语法 https://nsloon.app/docs/Rewrite/rewrite_v2 复写生成器 https://nsloon.app/rewrite-builder/

27 Jul 2026, 11:21 UTC≈1,550 views2 reactionsread 9 August 2026
Forwarded from @inaisiPhoto

😀 英国giffgaff开始关闭境外大门 这是一封来自 giffgaff(英国移动运营商,运行在 O2 网络上)的正式通知邮件。内容大意是:经过对你账户使用情况的审查,我们决定断开你的服务,因为你的使用模式显示出在英国以外的长期或永久使用,不符合我们的服务条款。 😀 建议使用giffgaff的尽量转移注册的各种服务号码 😀 你也可以联系客服进行退款 😀 为什么会发生这种情况? 😔 giffgaff 的服务条款和公平使用政策(Fair Usage Policy)明确规定: • 服务主要面向英国境内使用。 • 漫游(尤其是欧盟及指定地区)仅限于短期旅行(如假期、短途出行)。 • 如果你在任意 4 个月内境外使用达到 63 天或以上,且无法证明主要居住地/使用地在英国,就可能被视为不公平使用。 • 他们保留随时收取额外费用、暂停或直接断开服务的权利。 #资讯 #giffgaff

👍2

15 Jul 2026, 00:05 UTC≈2,060 viewsread 9 August 2026

原来的 surge.tel 域名停用了。新域名: mycats.club

16 Apr 2026, 22:32 UTC≈5,590 views2 reactionsread 9 August 2026

Telegram已经正式发布中文语言本地化,可在客户端直接选择。

1🤮1

16 Apr 2026, 11:58 UTC≈5,000 views22 reactionsread 9 August 2026
Forwarded from @SurgeTestFlightFeed

关于 Surge iOS 版本的功能订阅更新 我们了解到部分用户对近期 Surge iOS 的订阅功能更新不够频繁表示失望,因此对该问题进行说明和解决。 Surge iOS 自发布起已超过了十年,我们曾经的很多想法都已经被一个个的实现,因此,对于现在 Surge iOS 来说,想出一个新的功能并不容易。同时,为了保证用户体验,一些小型的新功能,也不会放入到订阅限制中。 对于我们的研发精力来说,其实有大量的精力放在了原有功能的改进与优化上,比如说最近更新加入的 X25519 + ML-KEM-768 后量子(混合)密钥交换支持,就要求我们从原本的 OpenSSL 实现切换至 BoringSSL,这涉及到大量的重构和测试。或是像去年跟随 Surge Mac v6 同步更新的最新 Surge VIF 引擎实现。这些都耗费了我们大量的研发精力,但是并没有纳入到订阅更新点中。 当然,由于 Surge iOS 的功能订阅,同时具备时

👎164🔥1🤮1

14 Apr 2026, 05:15 UTC≈3,280 views12 reactionsread 9 August 2026
Forwarded from @SurgeTestFlightFeed

关于 VLESS 协议的说明 我们长期收到用户关于支持 VLESS 代理协议的请求。鉴于围绕该协议存在较多争议,我们过去倾向于避免公开回应,以免引发不必要的讨论与争端。然而,持续的沉默本身也被部分解读为一种态度,甚至产生了一些误解与猜测。基于这一现实情况,我们决定对相关问题进行一次正式说明。 (由于 vless / vision / xtls 等名称本身缺乏统一且明确的定义,下文将以「VLESS」作为整个协议族的统称。) 加密代理协议社区始终保持着高度活跃。从早期的 Shadowsocks,到后来的 Trojan、ShadowTLS、TUIC、Hysteria、AnyTLS 等项目,不同开发者持续提出新的设计思路,并在开放讨论与相互借鉴中推动技术演进。许多项目均由开发者无偿投入时间与精力完成,对整个生态产生了积极影响。 因此,当新的项目具备成熟度与稳定性时,我们通常乐于进行支持与适配。尽管 Surge 本身并未直接参与开

6🤮5👏1

16 Feb 2026, 03:50 UTC≈3,210 views3 reactionsread 9 August 2026
Forwarded from @SukkaChannel

https://blog.skk.moe/post/to-kill-a-parrot-detecting-xtls-vless-reality-server/

2🤮1

1 Jan 2026, 01:19 UTC≈4,490 views9 reactionsread 9 August 2026

祝大家2026年健康快乐

😁52🔥1🤮1

30 Dec 2025, 01:18 UTC≈3,940 views3 reactionsread 9 August 2026
Forwarded from @zhetengsha

TeleBox: kitt 插件实现自动延迟删除消息 1. 安装 .tpm i kitt 2. 配置 .kitt add 自动延迟删除消息 return ['-1001771725356'].includes(msg.chatId.toString()) && ['/report'].includes(msg.text) setTimeout(async () => { try { await msg.delete() } catch (e) {}; }, 15 * 1000); 在 -1001771725356 的对话中延迟 15 秒删除 /report 其中对话 ID 匹配逻辑也已换成使用对话的 title 或者 username, 类似这样: [`折腾啥`].includes(msg.chat.title) [`zhetengsha_group`].includes(msg.chat.username

3

3 Nov 2025, 00:04 UTC≈4,110 views1 reactionsread 9 August 2026
Forwarded from @GetSomeFriesChannel

近日有网友发现 BiliBili 的视频(格式)广告内容也来自一些特殊的官方工作账号 此类账号具有以下特征: 1. 英文数字账号 2. 0 级小号 3. 投稿视频数量几千到几十万不等 4. 用户主页不显示任何投稿内容和动态 通过将这些官方广告工作账号加入黑名单即可屏蔽大量视频(格式)广告,缓解开屏广告/视频广告,切后台广告等 目前已知主要的广告工作账号列表如下: https://space.bilibili.com/1055149070 https://space.bilibili.com/1148923121 https://space.bilibili.com/1152997930 https://space.bilibili.com/1188004959 https://space.bilibili.com/1208114979 https://space.bilibili.com/1227735707 https:/

1

30 Oct 2025, 06:44 UTC≈3,210 views4 reactionsread 9 August 2026
Forwarded from @GetSomeFriesChannel

▶ YouTube “加载字幕时错误”的解决方案 问题成因: 只要 app 端字幕的 url 携带 tlang(翻译语言)参数,就会返回 429 错误,此问题是全球性的,至少已经持续了三个月而未被 Google 修复,这导致自动翻译功能在全球 YouTube app 都不可用。 YouTube web/TV 等不受影响。 解决方法: 将 [字幕] 启用类型(Type) 从 官方字幕(合成器) (Official) 改为 翻译字幕(翻译器) (Translate) 即可 (即不使用 YouTube 原生提供的翻译字幕) 延伸阅读: https://www.reddit.com/r/youtube/comments/1meu9kx/auto_translated_subtitles_no_longer_work/ https://www.reddit.com/r/youtube/comments/1n0kvr6/anyone

2👍2

Showing the 12 most recent of 16 posts we hold for @GetMoeCats. 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 — 565,485 of 1,160,990entries 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

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

“整点猫咪Channel” (@GetMoeCats), 4,273 subscribers as measured 10 August 2026. Telegram Register, tgregister.com/channel/GetMoeCats.

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.