Telegram RegisterThe public register of Telegram
Telegram profile photo for 李老师不是你老师

Channel

李老师不是你老师

@whyyoutouzhele

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

792subscribers

-5 since we began measuring on 7 August 2026

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

Register entry

Telegram ID-1001766856165
TypeChannel
Username@whyyoutouzhele
CreatedBetween 1 December 2021 and 31 March 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live18 September 2026
Measurements held7
Confirmed unchanged1 time, most recently 18 September 2026
On Telegramt.me/whyyoutouzhele

Topic

Other / unclassifiable — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-FP8, prompt version 1) read this channel’s own recent posts on 20 September 2026 and assigned it the closest of 31 fixed categories, at 68% confidence. This is a model’s judgement about what the channel is likely to be about, not a fact this register measured the way a subscriber count or a view count is measured — it can be revised on a later pass, and it carries no weight anywhere else on this page. How this classification works, and why it has no browse page of its own yet.

Growth

789798793.57 August 2026 — 797 subscribers7 August 2026 — 797 subscribers7 August 2026 — 798 subscribers24 August 2026 — 796 subscribers31 August 2026 — 792 subscribers10 September 2026 — 789 subscribers18 September 2026 — 792 subscribers7927 August 202618 September 2026
7 measurements spanning 42 days, net -5. 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 788–799 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
18 Sept 2026, 07:37792+3
10 Sept 2026, 09:55789-3
31 Aug 2026, 18:15792-4
24 Aug 2026, 15:28796-2
7 Aug 2026, 23:02798+1
7 Aug 2026, 09:17797no change
7 Aug 2026, 08:57797first reading

Engagement

9 posts held, back to 31 March 2023 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 1 page of 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 9 posts for this entry, the most recent from 18 July 2024. An engagement rate over an empty window would be a number about nothing.

Reaction mix

90 reactions across 8 posts, in 6 distinct kinds. The most used accounts for 47.8% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
👍4347.8%
❤3336.7%
💩910.0%
🖕22.22%
😁22.22%
👏11.11%

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

Measured over the 9 most recent posts we hold, published 31 March 2023 to 18 July 2024, 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 Jul 2024, 11:32 UTC≈11,000 views29 reactionsread 7 August 2026
Photo

红军是如何筹款的 | 光明网《 文摘报 》2015年03月21日 05 版.   去白区筹款,首先要“一网散开,精密调查”。各部队划定区域后,就派出侦查员化装深入到乡镇,打听情况。调查的时候要找到贫苦勇敢的工农分子,从问路、聊天等方式入手。不能直接问:“这里有土豪没有?姓甚名谁?”而是通过侧面闲聊去侦察判断。或帮着他做事,在谈家常话中去探关于土豪的情况。   摸清情况后,就“迅速捉人,适当待遇”。“人是活宝,捉到人筹款就容易了。”捉人的方法要注意运用便衣队,化装各色土民,暗藏手枪分途出发。特别注意趁黑夜半夜、雨夜雪夜,以及拂晓黄昏三个时候。对于已捉到的人“要适当待遇,分别人的轻重普通。轻的可以放回办款,重的必须收押分别筹款(即“来了好多款才放,某人最重的要最后放”)。   催款的时候,要软硬兼施,“做好做歹,雷厉风行”。抓了土豪和家属,催款的方式要多种多样。比如派个战士在土豪身边磨马刀,装着要杀人;派个战士提着洋油桶,装着要烧…

👍14❤12😁2👏1

18 Jul 2024, 11:12 UTC≈7,960 views7 reactionsread 7 August 2026
Forwarded from @getoutforchinaPhoto

安逸

❤7

23 Feb 2024, 06:21 UTC≈9,730 views4 reactionsread 7 August 2026

广州沥心沙大桥“断裂” 一位四代居住于岛上、经营饭店的村民向记者表示,他几乎每天都要驾车经过沥心沙大桥“出岛”购买食材,曾多次见到桥面出现移位、塌陷等情况。“疫情前就有了,(村里)讨论过很多次,一撞到肯定出事的,(发生事故)不意外。”这位村民续称,至事发前,沥心沙大桥的桥面问题一直没有完全改善。另有一位岛内村民亦向记者表示,对沥心沙大桥出事“不意外”,自几年前大桥维修过后村里很多人都担心大桥的安全性。 经济观察报 https://archive.md/rgJa0

👍3❤1

11 Oct 2023, 14:03 UTC≈12,900 views20 reactionsread 7 August 2026
Photo

在小红书上,做广告的舆情监测机构展示了他们如何监控关于“北极鲶鱼”的舆情信息 https://twitter.com/whyyoutouzhele/status/1712060003685712118

👍9💩8❤3

18 Sept 2023, 11:25 UTC≈12,800 views10 reactionsread 7 August 2026
Photo

自媒体时代,政府是如何做好宣传工作的? 针对《治安管理处罚法》的讨论,所有表达过反对意见的大V被全部统计成表格“拉清单”,下发全国各地网警部门,要求组织动员体制内人员前往它们的评论区进行控评(如图4)。 也就是说,你在热门社会话题下方所看到的很多正向评论,其实是全国晶哥一起努力的结果。 https://twitter.com/whyyoutouzhele/status/1703727643642724659 https://t.me/whyyoutouzhele/40

❤5👍5

19 Aug 2023, 06:00 UTC≈9,130 views0 reactionsread 7 August 2026
Photo

管窥一下网评员的工作。 iOS 大雁网评 Beijing Wiseweb Technology Co.,Ltd App Store Description 此APP与本公司(即网智天元)的拉萨市网评管理平台相结合,实现对网络评论员管理、考核、统计报表、信息检索、知识积累、协同工作的一体化平台。 此版APP包含如下功能: 日常任务:可对日常任务接收,查看详情,任务响应等。APP支持对接收的任务按列表显示,提供任务的实时查询功能,包含任务的状态,发布时间及详情信息,并可对任务进行响应。 历史任务:支持对已完成的历史任务查询功能,可根据时间多维度的查询。 任务发布:支持任务添加、派发、任务要求描述,任务接收单位设置等,可根据时间、任务状态等进行多维度的查询。 个人中心:帮助客户管理个人账号、密码,进行个人信息维护,系统设置等,并于管理平台保持一致。 Source: https://archive.md/MDE8w

6 Jul 2023, 01:36 UTC≈6,960 views5 reactionsread 7 August 2026

更新投稿邮箱: [email protected] https://twitter.com/WhyYouTouZheLe 注册新邮箱不要用自己常用ID,防止社工。 Proton Mail 目前注册不需要验证手机号。 ---------------- 前情提要: “由于推特限制了所有的第三方应用 导致目前我的手机和电脑都已经无法继续保存【私信】里的视频。 目前向大家求助是否还有可以保存【私信】内视频的第三方应用,任何系统的都可以。” https://twitter.com/whyyoutouzhele/status/1676035435728891904 ------- “很多朋友私信说Hotmail投稿不安全 这样,你们在私信里提议哪个邮箱安全,我去用点赞最高的那个” https://twitter.com/whyyoutouzhele/status/1676048572523896833

❤5

11 May 2023, 12:06 UTC≈5,850 views3 reactionsread 7 August 2026
Photo

Vivo和iQOO手机已经将国家反诈中心接入其OriginOS浏览器中。 有用户在手机浏览器-设置-安全中心中发现证实了这一点。 下午5:59 · 2023年5月11日 https://twitter.com/whyyoutouzhele/status/1656599829001166848 ⚠️ 已接入反诈的不仅限于这两家国产手机

🖕2💩1

31 Mar 2023, 03:22 UTC≈5,150 views12 reactionsread 7 August 2026
Photo

Blogger 编程随想 阮晓寰 2021年5月10日被捕,23年2月10日在上海二中院以煽颠罪判刑7年。 他的妻子(贝姓)受访说,被捕当日中午丈夫正在书房工作,她听见敲门声以为是送水,叫他去应门,遂被武力带走,有一边的眼镜都敲碎了;之后七八名警察进屋搜查,一直到第二天凌晨。 本案因 “涉及国家秘密” 不公开开庭审理,贝仅能获知 “案情非常严重” “在境外平台发表七百余篇文章”。时隔近两年,直至23年2月宣判时才再度见到阮一面,见他大为消瘦,头发几乎全白。法院要求她承诺不公开判决书,她未同意。 贝女士介绍,她与阮晓寰在华东理工大学化工系同窗相识。阮痴迷于信息技术,肄业进入网络安全行业,在启明星辰工作时曾任北京奥运会网安总工;2012年辞去全职,专注开源研发。 她说,丈夫被捕但案情成谜,她为弄清情况才学会 “翻墙”;有一天在网咖里看到 “编程随想” 失踪的报道,失踪时间和博文总数与阮案相符,编程随想一度停更四个月也恰好是阮卧…

👍12

Showing the 9 most recent of 9 posts we hold for @whyyoutouzhele. 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.

Forward network

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

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

“李老师不是你老师” (@whyyoutouzhele), 792 subscribers as measured 18 September 2026. Telegram Register, tgregister.com/channel/whyyoutouzhele.

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.