Telegram RegisterThe public register of Telegram
Telegram profile photo for 呆呆的进化

Channel

呆呆的进化

@slowStudy

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

2,229subscribers

-27 since we began measuring on 7 August 2026

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

Register entry

Telegram ID-1001698153136
TypeChannel
Username@slowStudy
CreatedBetween 1 December 2021 and 30 April 2023— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live27 August 2026
Measurements held8
Confirmed unchanged1 time, most recently 27 August 2026
On Telegramt.me/slowStudy

Growth

2,2272,2562,241.57 August 2026 — 2,256 subscribers8 August 2026 — 2,256 subscribers11 August 2026 — 2,248 subscribers14 August 2026 — 2,246 subscribers17 August 2026 — 2,237 subscribers21 August 2026 — 2,232 subscribers24 August 2026 — 2,227 subscribers27 August 2026 — 2,229 subscribers2,2297 August 202627 August 2026
8 measurements spanning 20 days, net -27. 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 2,223–2,260 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
27 Aug 2026, 22:452,229+2
24 Aug 2026, 19:362,227-5
21 Aug 2026, 02:472,232-5
17 Aug 2026, 22:382,237-9
14 Aug 2026, 19:242,246-2
11 Aug 2026, 16:072,248-8
8 Aug 2026, 11:032,256no change
7 Aug 2026, 14:192,256first reading

Engagement

20 posts held, back to 2 December 2024the 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.

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

Reaction mix

13 reactions across 9 posts, in 2 distinct kinds. The most used accounts for 61.5% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
👍861.5%
538.5%

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 11 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 13reactions 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 2 December 2024 to 26 December 2025, 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

26 Dec 2025, 06:55 UTC≈1,690 views3 reactionsread 7 August 2026

🎄 圣诞特别版 🎄 2025年12月25日,万家灯火,圣诞狂欢。 而我,盯着 App Store Connect 的转圈圈... "仍有截屏在上传中" "你必须上传 iPad 截屏" "已有较新的构建版本" 一关又一关,一坑又一坑。 为了客户的一句"尽快上线", 昨天的圣诞夜,我选择与苹果审核共度。 ——— iOS 开发 & 上架一条龙服务 ✅ 从 0 到 1 App 开发 ✅ App Store 上架全流程 ✅ 踩坑经验,少走弯路 📮 咨询:@SenpTBot ——— "你负责 idea,我负责让它上架。"

👍3

24 Dec 2025, 02:31 UTC≈1,530 viewsread 7 August 2026

📢 新功能上线:Telegram 账号换绑 如您的 Telegram 账号因故无法使用,现可通过换绑功能将新账号绑定至原有账户,自动继承积分和会员权益。 使用方式: 私聊机器人发送 /rebind 或「换绑」 支持两种场景: • 用新 TG 发起:输入旧账号用户名 + 藏楼密码 • 用旧 TG 发起:输入新 TG 的 ID + 藏楼密码 前提条件: • 账户已设置藏楼密码 • 新 TG 未绑定其他账号 如未设置密码,可访问藏楼 @AhuskyBot 自助设置。 由 @AhuskyBot 提供支持

22 Dec 2025, 06:37 UTC≈1,300 viewsread 7 August 2026

📦 积分系统优化更新 ✅ 消费顺序优化 新获得的积分优先消费,老积分保留 ✅ 性能优化 百万级数据查询提速 ✅ 运营积分调整 群内 /int 命令支持手动增减用户积分 生效日期:2025-12-22,由 @AhuskyBot 提供支持

21 Dec 2025, 03:09 UTC≈1,110 viewsread 7 August 2026

📢 新功能上线:邀请积分 邀请好友入群,好友发言后即可获得积分奖励! • 每成功邀请1人:+5积分 • 每日上限:10人 群内发送 /invite 获取你的专属邀请链接 发送 /invite_stats 查看邀请统计 由 @AhuskyBot 提供支持

20 Dec 2025, 09:44 UTC≈1,070 viewsread 7 August 2026

🔔 群喵 Bot @qunmiaoBot 功能更新 - 频道订阅验证系统 【新功能】频道订阅验证 为群组管理员提供强大的频道订阅验证机制,要求新成员关注指定频道后才能在群组发言。 核心特性: • 智能验证机制:支持新成员加入、入群申请批准等多种加入场景 • 一键验证按钮:被限制用户可通过 Inline Button 即时验证,无需发送命令 • 灵活处罚策略:支持临时禁言(自定义时长)或踢出群组 • 性能优化:Redis 缓存 + 监控列表机制,对群组消息流零影响 • 循环检测:未订阅用户解禁后发言将再次被限制 技术亮点: ✓ 高性能:监控列表过滤(O(1)),限流机制(10分钟/次) ✓ 高可用:Telegram 自动解禁机制,Bot 无需常驻任务 ✓ 用户友好:Markdown 用户提及、@username 频道链接 配置方式: /setup → 🔐 入群验证 → 📺 频道订阅验证 适用场景: • 推广品牌频道,增加

10 Dec 2025, 08:14 UTC≈1,130 views1 reactionsread 7 August 2026

🗺 新功能上线:附近老师搜索 在群里发送「地点名 + 附近老师」,即可查找附近的老师。 📍 使用示例: 高新区附近老师 春熙路附近老师 天府软件园附近老师 🎯 功能特点: 无需定位授权 无需打开地图 无需复杂操作 实时状态 - 🟢可约 🔴休息 一目了然 💡 小贴士: 地名越具体,定位越精准。比如「世豪广场附近老师」比「武侯区附近老师」更准确。 优雅、轻量 在群里说一句话,就够了 😁 ——— 由 @AhuskyBot 提供服务

1

6 Dec 2025, 15:31 UTC≈1,530 views1 reactionsread 7 August 2026

嗨,各位老朋友~ 2022 年 1 月 9 日,呆呆兽诞生了。 一晃快 4 年,陪大家签到、水群、抽奖、竞拍…… 还记得吗? • 最早只有签到和发言积分 • 后来加了 LBS 定位找老师(全网唯一!) • 再后来有了竞拍、抽奖、定时消息 • 去年还上线了比赛竞猜 • 上个月刚支持了视频消息…… 随着功能越堆越多,呆呆兽也越来越「胖」了 🐢 所以我们花了大半年时间,把系统重构了一遍。 现在,正式推出 —— 新系统机器人矩阵: 🐱 群喵 @qunmiaoBot (喵~) 群管专家|自动回复、定时消息、进群欢迎、权限管理 → 继续免费 🐕 呆呆兽v2 @AhuskyBot (一个/哈士奇/Bot) 服务专家|签到打卡、积分管理、会员查询 → 呆呆兽的传承,专注服务 🎰 抽奖机器人 活动利器|即将上线 一只呆呆兽,拆成了专业矩阵。 各司其职,响应更快、更稳定。 ——— ⚠️ 老系统停运通知 呆呆兽老系统 @KeDu

1

14 Jan 2025, 14:23 UTC≈7,950 views2 reactionsread 7 August 2026
Photo

抽奖活动新增支持图文视频消息

1👍1

25 Dec 2024, 08:10 UTC≈8,240 viewsread 7 August 2026
Photo

抽奖新增发言数条件限制+人满开奖类型

24 Dec 2024, 16:05 UTC≈7,240 views0 reactionsread 7 August 2026
Photo

新增自动回复警告多次自定义处理

23 Dec 2024, 16:22 UTC≈5,380 views1 reactionsread 7 August 2026
Photo

自动回复新增发言频率匹配触发

👍1

22 Dec 2024, 16:28 UTC≈4,650 views0 reactionsread 7 August 2026
Photo

新增当月发言活跃统计榜内容变量

Showing the 12 most recent of 20 posts we hold for @slowStudy. 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.

Mentions

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.

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

“呆呆的进化” (@slowStudy), 2,229 subscribers as measured 27 August 2026. Telegram Register, tgregister.com/channel/slowStudy.

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.