Telegram RegisterThe public register of Telegram

Channel

庭说 TingTalk

@tingtalk

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

8,525subscribers

-16 since we began measuring on 6 August 2026

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

Register entry

Telegram ID-1001463754213
TypeChannel
Username@tingtalk
Created12 February 2019measured — cross-checked against a third-party dataset (ext.tg_channel)
First recorded6 August 2026
Last confirmed live13 August 2026
Measurements held4
Confirmed unchanged1 time, most recently 13 August 2026
On Telegramt.me/tingtalk

Growth

8,5258,5418,5336 August 2026 — 8,541 subscribers7 August 2026 — 8,541 subscribers10 August 2026 — 8,535 subscribers13 August 2026 — 8,525 subscribers6 August 202613 August 2026
4 measurements spanning 7 days, net -16. 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,523–8,543 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
13 Aug 2026, 12:178,525-10
10 Aug 2026, 10:448,535-6
7 Aug 2026, 03:478,541no change
6 Aug 2026, 15:468,541first reading

Engagement

20 posts held, back to 30 May 2022the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 13 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 20 posts for this entry, the most recent from 18 January 2026. An engagement rate over an empty window would be a number about nothing.

Reaction mix

781 reactions across 20 posts, in 3 distinct kinds. The most used accounts for 97.8% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
👍76497.8%
🤔121.54%
👎50.64%

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 20 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 781reactions 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 30 May 2022 to 18 January 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

18 Jan 2026, 14:57 UTC≈6,080 views37 reactionsread 12 August 2026

读者朋友们,好久不见! 最近动了做 #近视手术 的念头,主要是鼻梁太敏感,一戴 #眼镜 就非常不适。于是 2026 年 1 月 1 日特地跑了一趟广州 AMASS 做了免费的全套检查,本想一劳永逸,结果却被劝退。 核心阻碍在于我的暗瞳直径偏大,手术风险主要在夜间: - 生理数据:报告显示我暗光下瞳孔为:右眼 7.54 mm / 左眼 7.23 mm(一般人通常在 6.0 - 6.5 mm)。 - 技术瓶颈:全飞秒(SMILE)的标准切削光区通常仅 6.5mm 左右。 - 物理后果:一旦在晚上加班或开车,瞳孔散大超过了切削区,光线从边缘进入,视野中就会出现严重的 #眩光(光圈或星芒)。 考虑到这会导致夜间开车可能会看不清交通信号灯,安全隐患太大,只能作罢。 刚好看到这个 视频,详细解释了其中的原理,想做手术的朋友建议先看看。

👍32🤔4👎1

25 Dec 2024, 03:44 UTC≈18,900 views58 reactionsread 12 August 2026
Photo

这是一份非常全面的 #网络安全 检查清单,一共有 258 个项目,每一项都有详细的解释,涵盖密码安全、浏览安全、移动设备安全等方面的内容。在当前环境下,#信息泄露 可能会导致重大的损失,因此,确保我们在连接互联网的时候,我们尽可能地保护自己的 #隐私、提高数字生活的安全性。 https://ipcheck.ing/#/securitychecklist by 阿禅(Jason Ng)

👍58

2 Nov 2024, 03:13 UTC≈17,200 views104 reactionsread 12 August 2026
Photo

虽然博客 tingtalk.me 都被中国大陆封禁 5 年半了,但每年还是会照常续费,留个念想:万一工作不忙了,就有空写文章了。

👍100🤔3👎1

18 Dec 2023, 03:17 UTC≈31,200 views59 reactionsread 12 August 2026
Photo

在局域网内,例如同一个 Wi-Fi 下,如何快速把文件从 iPhone 手机 #无线传输 到 Windows 电脑,我用 LocalSend:免费、开源、跨平台。 iOS 设备通过 LANDrop 把图片共享到附近的设备时,部分文件总是传输失败。

👍59

29 Oct 2023, 05:01 UTC≈33,800 views37 reactionsread 12 August 2026
Photo

如何在 #谷歌搜索 #图片 的时候,调出更多的图片格式? 在关键词后加入 filetype:PNG png 可以换成 JPG、GIF、BMP、SVG、WEBP、ICO、RAW 等 来源:超级搜索技术,普通人变强的唯一外挂 | 全套宝藏实操秘技_哔哩哔哩_bilibili @TingTalk: 更多 #搜索技巧,参阅 tingtalk.me/search-tips 庭说的公众号从这篇文章开始就被盯上了,过几个月后,也就是 2020 年 4 月 8 日就被永久封号了。

👍37

18 Oct 2023, 15:15 UTC≈25,600 views38 reactionsread 12 August 2026
Photo

近期,在电脑上看 #油管 #视频 的时候,会收到「#YouTube 不允许使用 #广告拦截器」的警告。怎么办? 以 uBlock Origin 扩展程序为例: 1. 打开 youtube.com 2. 点击 uBlock Origin 扩展程序的图标,即可关闭 #广告 拦截功能。仅对 YouTube 有效,其它网站 uBlock Origin 依然可以拦截广告。 3. 安装这个 去除 YouTube 广告的脚本,轻量且高效,也能丝滑的去除界面广告和视频广告,包括 6 秒广告。 来源:群友的推荐。 @TingTalk:更多 #脚本,请参阅 tingtalk.me/userscripts

👍38

26 Sept 2023, 14:22 UTC≈21,500 views29 reactionsread 12 August 2026
Photo

万字详拆芯片:人类算力 被锁死了吗? 最近,我好奇 #芯片 是怎么制造出来的?原理是什么?看了芯片工程师三圈的视频(哔哩哔哩 | YouTube)和新石器公园的的视频(哔哩哔哩)后,理解了基本概念。 今日,看了青工所的科普视频 万字详拆芯片:人类 #算力 被锁死了吗?(哔哩哔哩 | YouTube)后,思绪更明朗了。 @TingTalk:大学的时候,老师教过 MOSFET(金属氧化物半导体场效应管),那时我在睡觉,悔不当初呀。

👍29

21 Jun 2023, 15:23 UTC≈27,700 views45 reactionsread 12 August 2026
Photo

🏥 #医保 怎么用最省钱?by #柴知道 1. 医保卡挂号(不要用身份证) 2. 小病不去大医院 哔哩哔哩 | YouTube 📄 视频文字稿 🫱 补充内容: 各地医保报销政策 什么是医保报销目录 医疗保险和生育保险 @TingTalk:社会保险(包含医保)+ 商业保险,共同转移未来不可控的风险。

👍45

26 Apr 2023, 14:16 UTC≈26,000 views32 reactionsread 12 August 2026
Photo

🔒 如何去配置一套安全且便利的账号 #密码 库 本教程将以安全性为最优先前提,以便利性为辅,给予你一套管理的方案且会推荐你账号 #密码管理 的相关工具。 访问 #博客,阅读原文:YougeWath 作者的 Telegram 频道:@WathYougeWash @TingTalk:欢迎 #投稿

👍32

26 Jan 2023, 15:16 UTC≈31,800 views52 reactionsread 12 August 2026
Photo

Telegram 此号码已被封禁,快速解封的方法,解除「This phone number is banned」 提醒 方法一:发 Email 到 recover@telegram.org 方法二:通过「支持」渠道申诉 https://telegram.org/support 方法二全网没多少人用,或者是用了的人没有进行分享。博主「大V鱼塘」经过多个账号测试,比方法一见效快,12 小时不到, Telegram 就解封了。 详情见博客:https://www.dvyt.com/81.html 消息来源:A 姐 #TelegramTips

👍52

19 Nov 2022, 15:09 UTC≈28,600 views27 reactionsread 12 August 2026

摄影世界入门 by FView 爱否 时长 36 分钟:YouTube | 哔哩哔哩 聊一点 #摄影 方面的入门知识以做铺垫。说深了,普通消费者可能会云里雾里,说浅了,又会被专家极客们所耻笑,这回也是试着挑战一下这个度。不过了解我们的朋友都知道:和技术细节比起来,FView 更重视的是消费观点和理念的传播,本期你会听到关于 #单反、微单选哪个?器材党和技术流谁更占理?直出与后期 PS 哪个更重要?穷屌丝有没机会逆袭……等很多独到的消费观点。 @TingTalk:虽然是 2015 年 8 月 11 日的教学视频了,但经典不过时。

👍27

13 Nov 2022, 14:00 UTC≈26,300 views40 reactionsread 12 August 2026
File

中国居民膳食指南(2022)含书签扫描版 扫描版 PDF 来自网络,目录(书签、大纲)由 cereal•killer 手动添加。 #膳食 #膳食指南 #中国居民膳食指南

👍40

Showing the 12 most recent of 20 posts we hold for @tingtalk. 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 — 369,914 of 1,183,361entries 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.

Republishes

Channels on the register whose posts this channel has forwarded.

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 4 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.

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

“庭说 TingTalk” (@tingtalk), 8,525 subscribers as measured 13 August 2026. Telegram Register, tgregister.com/channel/tingtalk.

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.