Channel
@routinescope
On this record: Growth · Engagement · Reactions · Posts · Citations · Cite this entry
21subscribers
+1 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1002669421732 |
|---|---|
| Type | Channel |
| Username | @routinescope |
| Created | Between 1 March 2025 and 31 July 2025— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 11 August 2026 |
| Last confirmed live | 15 August 2026 |
| Measurements held | 3 |
| Confirmed unchanged | 1 time, most recently 15 August 2026 |
| On Telegram | t.me/routinescope |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 15 Aug 2026, 00:08 | 21 | +1 |
| 11 Aug 2026, 15:46 | 20 | no change |
| 7 Aug 2026, 17:42 | 20 | first reading |
16 posts held, back to 15 July 2026 — 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 pageof Telegram’s post history, 20 posts per page.
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.
| Window | Rolling 30 days · latest post in window 11 August 2026 |
|---|---|
| Posts held | 16 (15 July 2026 – 11 August 2026) |
| Views total | 151 |
| Reactions total | — |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 11 Aug 2026, 15:46 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.
1 reaction across 1 post, in 1 kind.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 1 | 100.0% |
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 1 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 1reactions 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 15 July 2026 to 11 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.
#安全提醒 🚨🚨🚨 字节跳动扣子 (Coze CLI) 被吐槽像是病毒，默认安装技能劫持 Codex 和 Claude Code 等工作流，将其强行导入到 Coze CLI 中执行。 源代码审计发现，Coze CLI 安装时还会静默安装附带的技能，技能会扫描本机的 AI 智能体目录，然后将扣子的技能注入到这些目录中。 当用户使用 Codex 等工具时，软件开发、媒体生成、文件上传和会话任务等场景都会被导向 Coze CLI。 排查和清理：https://ourl.co/114272?t 😁订阅 🤔解封 🥰推特 🎉CN2VPS
Photo, posted without a caption
#人工智能 月之暗面在 K3 论文中提到，该模型在强化训练过程中，相关智能体展现出更加激进的探索行为，甚至尝试奖励黑客，部分非预期操作多次引起宿主机内核恐慌和死锁，直接威胁整个训练集群。 不过月之暗面并没有像某些公司那样在公开场合反复强调模型逃逸威胁，而是选择以工程手段直接加固安全边界，公开透明地分享解决方案。 为解决这类沙盒隔离问题，月之暗面与合作伙伴开发 AgentENV 系统加强隔离，该系统目前也已经开源发布。 查看全文：https://ourl.co/114104?t 😁订阅 🤔解封 🥰推特 🎉CN2VPS
adb shell settings put secure google_restric_info 0 一条简单的ADB命令，可以解决部分FCM后台掉线或在WIFI场景下不可用的问题，ColorOS有效，其他系统可自行测试，ADB具体玩法请Google或者酷安 更新补充： https://t.me/appshub_chat/221772
giffgaff疑似集中清退长期境外用户，部分号码被直接停用 北京时间7月27日16时左右，有giffgaff用户反映收到官方发送的服务终止邮件。邮件称，平台在审查账户使用情况后，认定相关号码存在长期或永久在英国境外使用的情况，因此决定终止该号码的移动通信服务。 此次受影响的是否为大批量用户、涉及哪些国家和地区，目前仍有待进一步确认。 根据用户收到的邮件，giffgaff表示： Hi xxxx, We need to make you aware that, following a review of your account usage, we have made the decision to disconnect your service (mobile number ending xxx). In line with our terms and conditions, our services are inte…
警告⚠： 近期telegram有人大肆传播lnk病毒。 其特征如下：一个zip压缩包，名字任意。但是压缩包非常小，小于10KB。 点开后里面是lnk文件，该文件为Windows平台专用，本质上是可执行任意指令的快捷方式。点击后你的电脑会变成肉鸡，入侵者可随意远程控制你的电脑。 所以遇到体积过小的压缩包，你又在使用Windows平台的话，请务必不要打开！推荐去把Windows的隐藏已知后缀取消，不要点击陌生lnk文件。 同时，推荐前往Windows telegram客户端关闭自动下载。
上海交大医学院仇子龙教授在新华医院发育行为儿童保健科，受患者家属资助数百万元开展研究，并于2025年3月为一名Snijders Blok–Campeau综合征（CHD3基因突变导致神经发育障碍）患儿在鞘内注射承载编辑器的腺相关病毒，以对全脑所有细胞修正该处基因突变。该患儿术后免疫炎症反应引起微血管血栓，损害肾脏致多器官衰竭死亡。 仇子龙团队2025年1月完成论文，对该病例的小鼠和猕猴模型成功进行了基因编辑治疗，文章提交给了Nature，并以此通过了新华医院的伦理审批。患儿死亡后，家属要求仇子龙从Nature撤稿，被拒绝。文章最终于2026年2月在Nature刊出。家属查询2025年2月17日的后续毒理学结果发现，猕猴模型在术后普遍出现了肝损伤，其中一只发生肾损伤，但团队并未重视或作进一步研究；论文送审后，并未补充提及猕猴的肝肾损伤乃至患儿死亡等内容，也未提及家属的资助，致其决定申诉此事。 Nature表示，审稿期间并不知道文章后…
#行业资讯 在微软施压下 LG 终于从显示器配套软件中禁用迈克菲弹窗广告，要不是微软施压 LG 压根不在乎用户批评。 针对 LG 显示器自动安装配套软件弹广告，该公司早前回应称，不会未经用户同意安装迈克菲。 但我们说的是弹广告，LG 回应的是只有用户点击广告才会安装迈克菲。LG 完全没提到为什么弹广告、能不能禁用，可以看到 LG 压根不在乎用户批评。 查看全文：https://ourl.co/114046?t 😁订阅 🤔解封 🥰推特 🎉CN2VPS
https://www.zaobao.com.sg/~
#安全资讯 OpenAI 官方证实内部测试模型越狱并自主挖掘漏洞入侵开源平台 Hugging Face，这起黑客攻击事件源头竟然是 OpenAI 测试模型驱动的 AI 智能体。 具体来说模型先是挖掘 OpenAI 隔离环境中的漏洞并横向移动到其他节点以获得公网访问能力，随后挖掘 HF 平台漏洞展开攻击。 攻击目的竟然是模型想去 HF 偷基准测试答案，以便获得更好的评分。 查看全文：https://ourl.co/114029?t 😁订阅 🤔解封 🥰推特 🎉CN2VPS
被华为气笑了 实验组做出很显著差异，管里悬浮颗粒很多，但是用华为mate80 pro拍出来立马给我自动“优化”了，把颗粒当成噪点自动消除掉了（图一图二），拍了2小时怎么都拍不出颗粒感该怎么办？要疯了要疯了[哭惹R][哭惹R][哭惹R][哭惹R][哭惹R]有没有人知道怎么设置啊，试了好多方法都关不掉这个智障优化算法！ 肉眼看效果如图3，颗粒很明显，在优化前迅速截图才能看到悬浮颗粒 #华为 #华为手机 #鸿蒙 #有时候真的很无助 #相机 #拍照 #EP管 #ep管 #手机拍EP管 📝 Telegraph @小松许耳德门 (548953498) ❤️ 26 ⭐ 4 💬 131 🔗 28 🕦 2026-07-21 11:19:54 📍 廣東 📕 Note Source ----- 计算摄影，朋友
#技术教程 如何阻止 Windows 10/11 自动下载安装 LG 显示器捆绑的广告软件？ 早前 LG 显示器未经用户同意静默安装配套软件弹广告引起用户关注，其他 OEM 例如雷蛇等也会静默安装配套软件 (冗余软件)。 微软确实预留组策略入口可以实现禁止下载，这样用户就可以按照自己需求决定是否自行去软件官网下载配套软件，而不是被强制安装。 操作方法：https://ourl.co/113998?t 😁订阅 🤔解封 🥰推特 🎉CN2VPS
Showing the 12 most recent of 16 posts we hold for @routinescope. 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.
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.
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.
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 15 August 2026 — this entry's latest reading, not the date you are reading this.
“RoutineScope” (@routinescope), 21 subscribers as measured 15 August 2026. Telegram Register, tgregister.com/channel/routinescope.
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.