Telegram RegisterThe public register of Telegram

Channel

奶思🍒资源分享|频道

@inaisi

On this record: Topic · Observations · Also posting the same content · Growth · Engagement · Reactions · Posts · Citations · Cite this entry

12,211subscribers

+102 since we began measuring on 6 August 2026

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

Register entry

Telegram ID-1001792928933
TypeChannel
Username@inaisi
CreatedBetween 1 December 2021 and 28 February 2023— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded6 August 2026
Last confirmed live13 August 2026
Measurements held8
Confirmed unchanged1 time, most recently 13 August 2026
On Telegramt.me/inaisi

Topic

Technology — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-UD-Q6_K_XL, prompt version 1) read this channel’s own recent posts on 10 August 2026 and assigned it the closest of 31 fixed categories, at 97% 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.

Observations

These are measurements, not verdicts. Each one below states something we counted, alongside the evidence it was counted from, so you can check it rather than take it. None of them is graded: every observation this register holds is recorded at severity 0, because the precision of the detectors behind them has not been measured yet, and a rating we cannot support is worse than none. Read each as a fact about the data, not as a judgement about the channel. How we measure.

Content that also appears on other registered channels

Posts published here appear word for word on 1 other registered channel. The matching is on the text itself, not on Telegram’s forward marker, so it finds a copy whether or not it was labelled as one.

Matching posts — open both and compare (1 of the pairs behind the counts below)
Posted firstThenOverlapGap
@inaisi/744 · this entry3 Aug 2026, 17:05 UTC@Aa28413761/22363 Aug 2026, 17:07 UTC1.002 minutes
Every channel this entry shares post bodies with
ChannelMatching postsText overlapTypical gapPublished first
@Aa284137615 (5/5 hand-verifiable sample passed)1.0016 minutesthis entry (50)

Text overlap is the Jaccard coefficient over the set of distinct three-word phrases in the two bodies: 1.00 is identical wording, and the threshold for counting a pair at all is 0.70. Candidates are generated by simhash LSH (4 x 16-bit bands, exact Hamming <= 3) verified against the bodies with Jaccard over the SET of distinct 3-word shingles. Published first counts which side of each matching pair carries the earlier timestamp — in this corpus, which is the limitation directly below.

What this cannot establish

MEASURED, DOMINANT ERROR SOURCE: a post ingested before 2026-08-06 may have carried a forward header that was not recorded. A 45-pair hand-check against live t.me pages found 14 (31%) where the live page shows a forward header naming the other channel and the database has none, plus 4 more (9%) naming a third party. The text match itself was wrong 0 times out of 45. Read attribution_capture.items_in_trusted_window before treating the unattributed count as a claim.

Telegram lets a channel forward a post with a header naming the source, and we only began reliably recording that header on 2026-08-06. None of the 0 matches recorded here fall after that date, so for this entry we cannot say whether any of them carried a credit. The duplication is measured; the absence of attribution is not.

“Published first” means first in this corpus. We hold 17 comparable posts for this entry, running 29 July 2026 to 7 August 2026. A channel we have read one page deep will look younger than a neighbour we have read in full, and the order would flip with no change in the underlying facts.

The detector’s own notes on this observation, as it recorded them. Names in this_style are fields of the underlying evidence record, which the plain-English paragraphs above read out for this entry.

  • Verbatim republication has three causes and the text separates only two: a clone/mirror, unattributed copy-paste, or BOTH channels copying a common third source that neither attributes. The spread filter (content held by at most 8 channels) reduces the third and does not remove it.
  • 'Earliest' means earliest IN THIS CORPUS. A channel ingested one page deep will look younger than a neighbour ingested in full; corpus_coverage above is there to be checked before the direction is believed.
  • shared_verified_est extrapolates the sampled pass rate over the full narrow match count; sampled/passed are the numbers actually measured.
  • Absence of a forward header is not proof of intent: Telegram lets a channel disable forward attribution, and a credit written in the body is not parsed as attribution here (mention_edge_either_way above is the closest available signal).

Across the whole group of 2, the earliest publisher we hold is @inaisi — which is this entry. That is a statement about our reading window, not a claim of authorship.

Recorded under the key clone_source, last confirmed 7 August 2026. An observation that a later pass no longer finds is cleared, and a cleared observation is removed from this page rather than being shown struck through — we do not keep publishing a claim we have withdrawn. Dispute an observation.

Also posting the same content

This channel’s posts match, word for word or near enough, posts on 1 other registered channel, found by comparing text fingerprints across every channel on the register. That matching has been checked by hand against the live Telegram pages and found reliable — 0 wrong of 45 pairs re-read.

Which channel, if either, published first is deliberately not shown. The same hand-check found that reading wrong 18 of 45 times — 60%, no better than a coin flip — because it depends on how deep our own crawl happened to reach into each channel’s history, not on when the content was actually first posted. This list is ordered by subscriber count, the same as every other listing on this site, never by which channel we think came first. Word-for-word matching has several ordinary explanations besides copying — a channel mirroring itself, an unattributed repost, or two channels independently repeating the same wire story — and this measurement cannot tell those apart. How this is measured.

Growth

12,10912,21112,1606 August 2026 — 12,109 subscribers6 August 2026 — 12,116 subscribers7 August 2026 — 12,126 subscribers8 August 2026 — 12,152 subscribers10 August 2026 — 12,162 subscribers11 August 2026 — 12,170 subscribers12 August 2026 — 12,193 subscribers13 August 2026 — 12,211 subscribers6 August 202613 August 2026
8 measurements spanning 7 days, net +102. 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 12,094–12,226 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
13 Aug 2026, 09:5612,211+18
12 Aug 2026, 07:5212,193+23
11 Aug 2026, 05:5512,170+8
10 Aug 2026, 02:3112,162+10
8 Aug 2026, 23:3012,152+26
7 Aug 2026, 22:3812,126+10
6 Aug 2026, 23:4512,116+7
6 Aug 2026, 12:3112,109first reading

Engagement

31 posts held, back to 29 July 2026the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 16 pagesof Telegram’s post history, 20 posts per page.

ERR · 30 days
33.7%
avg views ÷ 12,211 subscribers
Avg views / post
4,110
31 posts measured
Reaction rate
0.261%
reactions ÷ views · ER floor
Posts in window
31
of 31 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 28 of 31 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 12 August 2026
Posts held31 (29 July 202612 August 2026)
Views total127,450
Reactions total310
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken13 Aug 2026, 03:36 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

310 reactions across 26 posts, in 17 distinct kinds. The most used accounts for 23.9% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
🤡7423.9%
6521.0%
👎5517.7%
🤣278.71%
💩237.42%
😁185.81%
👍144.52%
🤯113.55%
🤮72.26%
😨41.29%
🎉30.968%
👏30.968%
🥰20.645%
🌚10.323%
🍾10.323%
🖕10.323%
🤬10.323%

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

Measured over the 31 most recent posts we hold, published 29 July 2026 to 12 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

12 Aug 2026, 15:58 UTC≈1,310 views2 reactionsread 13 August 2026
Photo

😀 SpaceXAI发布Grok 4.6 Grok 4.6 是 xAI 在 Grok 4.5 基础上的重要升级,主打前沿智能水平,重点强化长时程代理、复杂交互与视觉任务。 主要亮点: 😀在 Artificial Analysis Intelligence Index 等综合基准上达到前沿水平,与 GPT-5.6 Sol 等顶级模型相当,多项任务显著优于 Grok 4.5。 😀更擅长把想法落地成完整项目:研究、分析、编码、构建抛光应用、自我测试与迭代,长时程任务表现更强。 😀速度更快,能处理更复杂的挑战性任务。 😀定价极具竞争力:输入 $2 / 百万 tokens,输出 $6 / 百万 tokens(约为其他前沿模型的一半)。 😀即日起已在 Grok Build、Cursor、Grok Bot 和 API 中上线,首周 Cursor 与 Grok Build 提供 2 倍用量。 #资讯 #Grok

1👎1

Signed KISS NAISI

12 Aug 2026, 15:36 UTC≈1,340 viewsread 13 August 2026
Photo

😀 微信发布自研模型WeLM 小微:由微信团队打造的一系列大型语言模型,以资源效率为核心。 之前微信就在测试AI功能,入口具体位置在微信左上角的绿点。 两大模型: 😀 WeLM-80B(80B参数 · 3B激活) 已上线小微AI:聊天搜索、调用微信功能、接入小程序 😀 WeLM-617B(617B参数 · 23B激活) MoE架构开发中,强化推理,支持智能小程序开发、工具生成 #微信 #资讯

Signed KISS NAISI

12 Aug 2026, 08:29 UTC≈1,960 views0 reactionsread 13 August 2026
Photo

😀 xAI 正式上线 Grok Bot 号称真正能干活的 AI 队友: • 每个 Bot 拥有自己的持久云端电脑,可以像真人一样登录并操作你的各种工具、App 和网站(即使没有 API 也能用)。 • 支持 24/7 不间断工作,即使你关机也能继续执行任务。 • 能独立完成多步骤、端到端的真实工作,只在需要你审批时才回来汇报。 • 像和同事聊天一样给它派任务(支持桌面和 iOS)。 • 可同时运行多个 Bot,它们能并行工作、互相协作、传递上下文。 • 可通过一次演示学习你的工作流,并保存为可定时运行的 Routine。 • 会持续记忆你的偏好和工作方式,越用越懂你。 目前对 SuperGrok Heavy、Cursor Ultra 和 Cursor Teams Premium 用户开放,官网:https://x.ai/bot #资讯 #grok

Signed KISS NAISI

11 Aug 2026, 15:36 UTC≈2,620 views11 reactionsread 13 August 2026
Photo

🎉 天眼Bot 2.0 大版本上线! 经过持续打磨,天眼Bot 从「群管理机器人」升级为 Telegram 一站式工具小程序 🚀 📱 全新管理面板 液态玻璃质感 UI,标签页一目了然;把 Bot 设为群管理员,即可在面板中管理你加入的全部群组 👮 智能群管理 入群即管:昵称 / 用户名 / 消息违禁内容自动检测与封禁;头像检测自动清理无头像发言;白名单保护误伤,规则全程可视、可开关; 本次新增简介检测与连坐功能:简介命中规则也封禁,简介中提及到的用户/群组/邀请链接命中连坐封禁。 📦 代理工具规则库 Loon / Surge / QuanX / Egern等代理工具插件与模块,海量规则分页浏览、一键导入,持续更新 🎯 TestFlight 情报库 数万款 App 的 TF 名额信息随时查询,热门应用不再错过 👉 立即体验:@TheSkyEyeBot 💬 官方群:@inaisi_chat #资讯 #skybot

10🤮1

Signed KISS NAISI

11 Aug 2026, 14:16 UTC≈2,650 views5 reactionsread 13 August 2026

😀诈骗性的婚介产业正将目标锁定在一些随着年龄增长、愈来愈难找到伴侣的脆弱男性群体,尤其是在男女比例悬殊的地区。 在一些案例中,新娘会带着大笔“彩礼”逃走。有些女性曾经多次结婚,甚至已有子女。 这是目前人口危机的一个侧面。由于过去偏好生男孩,目前男性人口比女性多出约3000万人。 兄弟萌保护好自己的钱袋子。 #资讯

2🤡2👏1

Signed KISS NAISI

10 Aug 2026, 17:15 UTC≈3,100 views27 reactionsread 13 August 2026
Photo

😀 据报道,苹果因生产困难取消了其全玻璃材质的20周年纪念iPhone。 更新:推到2027年发布 #资讯 #苹果

👎27

Signed KISS NAISI

9 Aug 2026, 10:12 UTC≈3,460 views4 reactionsread 13 August 2026
Photo

😀 重做了群管机器人 主包的机器人 @TheSkyEyeBot 目前准备升级到2.0版本,页面好看吗? #资讯

🤡2🥰2

Signed KISS NAISI

8 Aug 2026, 10:25 UTC≈4,000 views28 reactionsread 13 August 2026
Photo

😀 Apple 智能现已现身苹果官网支持手册 Apple 智能的相关信息现已现身 Apple 官网的 Mac 使用支持手册,该手册为用户使用和操作 Mac 提供上手指引。其中提到了中国 Apple 智能的合作伙伴“千问”。 这代表着 Apple 智能有望在不远的将来(下周?)于中国上线。 优先在Mac上线? https://support.apple.com/zh-cn/guide/mac-help/mchl46b3ab20/26/mac/26 #资讯 #苹果

👎9😁6💩5🎉3🤮21🌚1🍾1

Signed KISS NAISI

8 Aug 2026, 05:53 UTC≈3,840 views1 reactionsread 13 August 2026
Photo

😀 苹果据报道将于下周一(8月10日)上调iPhone 17的价格 #苹果 #资讯

🤮1

Signed KISS NAISI

7 Aug 2026, 18:18 UTC≈3,650 views2 reactionsread 13 August 2026
Photo

😀 Steam限免 🔊 《呼吸边缘》 在外太空中活下来!与永生不死的鸡作伴,探寻太空飞船意外坠毁背后的真相。制作物品、驾驶载具、探索残骸,甚至为了生存控制太空站。 https://store.steampowered.com/app/738520/_/ #steam #游戏 #限免

2

Signed KISS NAISI

7 Aug 2026, 10:53 UTC≈4,220 views41 reactionsread 13 August 2026
Photo

😀 恭喜clash verge荣登央视 视频中用的也不知道哪家的机场 https://tv.cctv.com/2026/08/02/VIDEZJoabCvJXzXSA2Jrx5d7260802.shtml #资讯 #clash-verge

🤣27😁122

Signed KISS NAISI

7 Aug 2026, 01:42 UTC≈6,600 views2 reactionsread 13 August 2026
Photo

😀 Epic Games 限免 🤫 《We Were Here Together》 当我们探索这片冰冷的荒地时,不幸再次降临。在狂风暴雪中,一道信号弹划破天空,紧接着,无线电传来求救信号——断断续续,奄奄一息…… 没有任何其他人可以来营救他们。我们能一起成功返回吗? https://store.epicgames.com/p/we-were-here-together-6a6d66 🤫 《Beacon Pines》(灯塔小镇) 一款可爱又略带恐怖的冒险游戏。在夜晚偷偷溜出去,结交新朋友,揭开隐藏的真相,并收集能够改变命运的词语! https://store.epicgames.com/p/beacon-pines-629fc3 #游戏 #限免 #epic

2

Signed KISS NAISI

Showing the 12 most recent of 31 posts we hold for @inaisi. 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 — 149,493 of 1,169,250entries 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 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.

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.

“奶思🍒资源分享|频道” (@inaisi), 12,211 subscribers as measured 13 August 2026. Telegram Register, tgregister.com/channel/inaisi.

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.