Telegram RegisterThe public register of Telegram
Telegram profile photo for 奶思🍒资源分享|频道

Channel

奶思🍒资源分享|频道

@inaisi

On this record: Topic · Observations · Channels linked by matching posts · Growth · Engagement · What this channel posts · Reactions · Posts · Posts edited after publishing · Citations · Telegram's recommendations · Cite this entry

14,221subscribers

+2,112 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
Description各种资源分享包括但不限于1、QuanX/Loon/Surge/Egern等代理工具规则。2、科技社会新闻。 关联群组:@inaisi_chat,@QuantumultXCommunity
CreatedBetween 1 December 2021 and 30 April 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded6 August 2026
Last confirmed live11 November 2026
Measurements held64
Confirmed unchanged1 time, most recently 11 November 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 the other topics.

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 in near-verbatim form on 1 other registered channel. This entry also forms a group of 2 channels linked by matching posts. 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
Channels this entry shares post bodies with, where at least one matching post pair has no forward credit between the two channels, or to a common source, recorded in our data
ChannelMatching postsText overlapTypical gapPublished first
@Aa284137618 (8/8 hand-verifiable sample passed)1.004 minutesthis entry (7–1)

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 154 comparable posts for this entry, running 29 July 2026 to 11 November 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).

Of the group of 2 channels, the one whose matching posts we hold earliest 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 12 November 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.

Channels linked by matching posts

This channel is in a group of 2 registered channels linked by matching posts. Links are found by comparing text fingerprints across every channel on the register.

Which channel, if either, published first is deliberately not shown in this list. “First” could only mean first in our own crawl, which depends on how deep we happened to reach into each channel’s history, not on when the content was actually first posted. Our one hand-check read 45 of the highest-confidence flagged pairs against the live Telegram pages. In 18 of them the live page showed a “Forwarded from” credit that our database had no record of, so reading that pair as an unattributed copy was wrong; the check did not measure who published first. This list is ordered by subscriber count, the same as every other listing on this site, never by which channel we think came first. Near-verbatim 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,10914,22113,1656 August 202611 November 2026
64 measurements spanning 97 days, net +2,112. 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 11,792–14,538 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 64
Measured (UTC)SubscribersChange
11 Nov 2026, 14:1814,221+23
9 Nov 2026, 19:1814,198+41
8 Nov 2026, 09:5614,157+30
7 Nov 2026, 01:0614,127+16
6 Nov 2026, 00:1714,111+8
5 Nov 2026, 00:4914,103+10
3 Nov 2026, 21:1514,093+19
2 Nov 2026, 21:0714,074+26
1 Nov 2026, 21:3914,048+20
31 Oct 2026, 19:3914,028+13
30 Oct 2026, 22:5014,015+6
30 Oct 2026, 01:1814,009+8
28 Oct 2026, 23:0614,001+17
27 Oct 2026, 20:1013,984+35
26 Oct 2026, 19:1013,949+18
25 Oct 2026, 20:5713,931+21
24 Oct 2026, 20:2013,910+17
23 Oct 2026, 22:5513,893+11
23 Oct 2026, 00:0113,882+18
21 Oct 2026, 21:0913,864first reading

Engagement

187 posts held, back to 29 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 66 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
14.6%
avg views ÷ 14,221 subscribers
Avg views / post
2,070
122 posts measured
Reaction rate
0.226%
reactions ÷ views · ER floor
Posts in window
122
of 187 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 107 of 122 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 November 2026
Posts held187 (29 July 2026 – 12 November 2026)
Views total252,680
Reactions total523
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken12 Nov 2026, 07:33 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.

What this channel posts

Photos
652
Videos
81
Links
442

Lifetime counters from Telegram’s own channel header, read 12 November 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.

Video runtime
5m 12s
Average length
35s

Measured directly from 9 videos with a duration reading, out of the posts we hold for this channel — not this channel’s whole posting history, only the sample this register has actually read. An exact reading to the second, taken from the post itself rather than from Telegram’s own rounded chrome, so it carries no ≈ mark.

Reaction mix

1,191 reactions across 149 posts, in 27 distinct kinds. The most used accounts for 25.5% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
❤30425.5%
🤡29624.9%
👍20517.2%
👎15613.1%
💩655.46%
🤣282.35%
😁262.18%
👏242.02%
🤮211.76%
🤯110.924%
🎉90.756%
🔥80.672%
🍾40.336%
😨40.336%
😴40.336%
🤷‍♂40.336%
🥰40.336%
🏆30.252%
👀30.252%
💊30.252%
7 further kinds90.756%

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

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

Telegram’s own ‘edited’ marker: 9 of 122 posts held from the last 30 days (7.38%) carried it when this register last read them. The marker says a post was changed after publishing, not what it said before — this register holds the earlier wording only where an edit fell between two of its own reads (see the edit ledger and how it is measured).

12 Nov 2026, 05:37 UTC695 views1 reactionsread 12 November 2026
Photo

🔴 群晖曝出 27 个 DSM 安全漏洞,最高危 9.8 分! 群晖近日公开了 27 个 DSM 安全漏洞,其中最严重的 CVSS 评分高达 9.8 分(满分 10 分),引发广泛关注。这是继此前 C3RB3R 勒索软件攻击事件后,群晖再次发布的安全公告。 ▫️ 最严重的漏洞位于 DSM 的 Auth API(认证接口),属于 SQL 注入问题。远程攻击者无需账户权限、无需用户配合,即可利用该漏洞。 ▫️ 第二个值得关注的漏洞评分为 8.6 分,影响 DSM 中的 rsync 组件,攻击者可能通过认证绕过漏洞读取特定文件、写入任意文件,或造成有限的拒绝服务。 ▫️ 其余 25 个漏洞还涉及 NFS、VPN、WebDAV 等组件。 目前没有证据表明,这次公开的 27 个漏洞与此前的 C3RB3R 勒索攻击存在直接关联。此前调查中提到的攻击路径(涉及 Synology-SA-26:13 公告中的两个漏洞)不属于本次新披露的范围…

👍1

Signed KISS NAISI

12 Nov 2026, 04:36 UTC922 viewsread 12 November 2026
Photo

🔋 苹果 iPhone 18 Pro Max 登顶 CNET 续航测试,综合表现最佳 科技媒体 CNET 对 32 款手机进行掉电测试,总测试时长超 120 小时。结果显示,iPhone 18 Pro Max 在 45 分钟压力测试中仅掉电 1%,与 iPhone Duo 并列第一;谷歌 Pixel 11 Pro XL 以 3% 耗电并列第三。在 3 小时视频测试中,iPhone 18 Pro 表现最佳,仅消耗 6% 电量。 ▫️ 胜出原因:CNET 认为 iPhone 18 Pro Max 得益于更大电池容量、iOS 27 系统优化以及 A20 Pro 芯片能效提升。 ▫️ 值得注意:电池容量大并不必然等于续航久,更亮的屏幕、更强的处理器和 AI 功能会消耗新增电量,2026 年新机平均续航与 2024、2025 年基本持平。 ▫️ 技术趋势:硅碳电池成为本年度最受关注变化,摩托罗拉 Razr(2026)和三星 Galax…

Signed KISS NAISI

12 Nov 2026, 04:13 UTC794 viewsread 12 November 2026
Photo

🚀 百度天池 1024 卡超节点发布:可支撑 5 万亿参数模型训练,明年上市 在今日举办的百度世界 2026 大会上,百度集团执行副总裁沈抖正式发布百度天池 1024 卡超节点,该算力集群计划于明年推向市场。 ▫️ 搭载业界领先光引擎技术,卡间互联带宽提升 3 倍,实现高速数据互联。 ▫️ 对比上一代产品,训练性能提升 2.5 倍,推理性能提升 3 倍。 ▫️ 配套 G3.5 KV Cache 显存加速柜,长上下文推理性能提升 2 倍;多轮对话缓存命中场景下,首 token 等待时间降低 90%,整体吞吐提升 7 倍。 ▫️ 单套超节点可支撑 5 万亿参数大模型训练,并具备优秀横向扩展能力,可扩展至万卡规模集群。 值得注意的是,百度去年曾宣布天池千卡级超节点 2028 年上市,如今节奏加快了一年;昆仑芯 N 系列也提前至 2028 年发布。 #资讯 #数码

Signed KISS NAISI

12 Nov 2026, 03:13 UTC907 viewsread 12 November 2026
Photo

🛡️ 700号段来了可放心接听,央视提醒4种电话别接、别回、别点 工信部近日批复10家企业试点号码保护服务,核配700专用码号资源。这项服务相当于给真实手机号披上“隐身外衣”,在外卖、网约车等高频场景中,用户与骑手、司机将通过700开头的15位专用号码联系,双方真实号码互不展示。 ▫️ 用户下单勾选号码保护后,来电显示和接通前语音播报会提示使用场景与平台主体,实现“放心接、明白接”。 ▫️ 订单结束后一段时间,临时号码自动失效,不会留下长期联系通道。 既然700号段可以放心接,那哪些号码要警惕?央视新闻汇总了4类: ▫️ “400”开头:企业客服电话只接不打,正规企业不会主动用它拨出。接到这类电话可能是诈骗分子用改号软件伪装,建议不接。 ▫️ “00”或“+”开头:按工信部规定,境外电话进入国内必须加国际冠字“00”(部分手机显示为“+”)。没有海外亲友的话,这类来电基本可判定为境外诈骗。 ▫️ “95”开头:5位或6位…

Signed KISS NAISI

12 Nov 2026, 03:05 UTC873 views3 reactionsread 12 November 2026
Photo

🛑 中消协发声:网购“AB货”涉嫌欺诈与大数据杀熟 中国消费者协会就近期持续升温的网购“AB 货”争议公开发声,指出部分电商以同一链接、同一价格,对不同消费者区别发送品质明显不同的商品,偏远农村消费者常被定向发送降级商品。 ▫️ 商家以次充好,侵害知情权和自主选择权,涉嫌货不对板,甚至构成欺诈。 ▫️ 利用算法画像区别发货,同时触及个人信息权益与公平交易权,违反《个人信息保护法》及算法推荐管理规定。 ▫️ 破坏公平竞争秩序,属于不正当竞争,侵蚀消费者信任和行业诚信根基。 监管层面已有动作:2026 年 4 月施行的《互联网平台价格行为规则》明确禁止基于消费者画像实施差异化发货;拼多多等平台也已将“AB 货”列为重点违规情形并采取处罚措施。 中消协提醒消费者保存商品页面、直播录屏、下单记录和收货实物照片等凭证,依法维权。 #资讯 #数码

👍2🤡1

Signed KISS NAISI

12 Nov 2026, 01:03 UTC≈1,090 views4 reactionsread 12 November 2026
Photo

🚀 中国移动完成业界首个230GBaud单波1.6Tb/s长距传输试验 中国移动联合合作伙伴基于230GBaud关键技术,在骨干长距G.652.D光纤上实现单波1.6Tb/s信号实时传输,传输距离达960公里,创下中国移动单波1.6T传输最长纪录,也是业界首个基于230GBaud的单波1.6T长距传输验证。 ▫️ 从130GBaud到230GBaud:中国移动于2024年完成400G骨干全光网首次规模应用时,主力波特率为130GBaud。但在城域场景单波1.2T现网试验中,该方案被判定与骨干长距传输需求差距较大,由此确立超200GBaud为重点研发方向。历时两年攻关,波特率水平进入业界前列(对比Ciena WaveLogic 6 Extreme单载波1.6T方案为200GBaud,主要面向城域距离)。 ▫️ 波特率提升的意义:在调制格式不变前提下,更高波特率意味着单位时间承载更多比特,从而在不额外占用波长资源的情况下提升单…

🤡4

Signed KISS NAISI

11 Nov 2026, 23:46 UTC≈1,140 viewsread 12 November 2026
Photo

📱 iCloud+ 在 iOS 27 为高存储用户新增 HomeKit 摄像头 AI 功能 ▫️ 苹果持续扩展 iCloud+ 的附加权益,不再局限于云端存储本身。 ▫️ 在 iOS 27 中,选择更高存储档位的 iCloud+ 订阅用户将获得一项新福利:HomeKit 摄像头的 AI 功能。 ▫️ 该功能预计将利用设备端或云端智能,为安防摄像头提供更高级的识别与通知能力,具体细节有待苹果进一步公布。 #iCloud #iOS27 #HomeKit #Apple #智能家居

Signed KISS NAISI

11 Nov 2026, 23:45 UTC≈1,160 viewsread 12 November 2026
Photo

🤖 Gemini 应用正式登陆 Apple CarPlay,车内畅聊 AI 助手 Google 宣布,Gemini 应用现已直接支持 Apple CarPlay,即日起对所有支持 Gemini Live 的语言开放。此前用户只能通过 Google Maps 应用间接使用该 AI 助手,现在只需在车载显示屏上点击 Gemini 图标,即可随时开启或继续对话。 ▫️ 车内使用场景:通勤时准备会议、处理邮件、收听每日简报,或获取周边值得探索的地点推荐。 ▫️ 对话同步:所有对话会与 iPhone 上的 Gemini 应用同步,并保留在聊天历史中。 ▫️ 使用条件:需确保 iPhone 上安装最新版 Gemini 应用、开启麦克风权限,并至少使用过一次 Gemini Live。 ▫️ 扩展布局:此前 Google 已在 Android Auto 上启用个人助理功能,未来还将把个人智能引入内置 Google 的汽车系统。 #资讯 #…

Signed KISS NAISI

11 Nov 2026, 23:44 UTC≈1,040 views0 reactionsread 12 November 2026
Photo

🎉 Apple Invites 更新:新增投票与表情效果 Apple 的免费邀请应用 Apple Invites 今天迎来更新,新增两项功能: ▫️ 主持人可在邀请中添加投票,让宾客对派对主题、食物等细节进行表决。 ▫️ 主持人还可添加“表情符号效果”,让表情在邀请中浮动。 #资讯 #Apple

Signed KISS NAISI

11 Nov 2026, 14:30 UTC≈1,430 views1 reactionsread 12 November 2026
Photo

🔔 Apple Watch 也能“听”门铃了!声音识别扩展到新款手表 苹果将 iPhone 上的辅助功能“声音识别”扩展到了 Apple Watch Series 12 和 Ultra 4,即使 iPhone 不在身边,也能在手腕上收到门铃、警报等重要声音的提醒。 这对听障人士尤其有用,日常也很实用——比如戴着降噪耳机工作时,不想错过门铃或快递,手表就能提醒你。 ▫️ Apple Watch 可检测的 15 种声音:火警、警报器、烟雾报警、猫叫、狗叫、家电、汽车喇叭、门铃、敲门、玻璃破碎、水壶、流水、婴儿哭、咳嗽、喊叫 ▫️ 如果声音未被自动识别,还可以在 iPhone 上自定义闹钟、家电或门铃声音 ▫️ 需要 Apple Watch Series 12 或 Ultra 4,配对 iPhone 11 或更新机型(或 iPhone SE 2 代及更新),运行 iOS 27 ▫️ 如果已在 iPhone 上开启声音识别,App…

❤1

Signed KISS NAISI

11 Nov 2026, 13:32 UTC≈1,410 views2 reactionsread 12 November 2026
Photo

😀【拆分模块更新】 仓库中的单独模块补上了之前漏掉的 MITM 主机名。用单独模块之前反馈不生效的,更新对应模块后可以测试是否生效。 彩云天气 新增双十一活动弹窗拦截。 补上主机名的模块 财新网、得物、粉笔、故宫博物馆小程序、横店电影小程序、汇付天下、IT之家、夸克、广告联盟(快手联盟 / 优量汇 / 穿山甲)、乐堡潮玩馆小程序、LING Club、去哒、Reddit、腾讯新闻、vgTime、温尼伯站、香蕉是一种水果、小米商城、中国国际航空、全民生活、中国银行缤纷生活。 Shadowrocket 财新网模块已补全。 CSDN、华盛通、深圳通由失效占位恢复为可用模块。 另外删掉了一份重复的 Surge「WIFI万能钥匙」模块,请改用 WiFi万能钥匙(WiFiMasterKey)。 https://github.com/fmz200/wool_scripts #去广告 #规则

❤2

Signed KISS NAISI

11 Nov 2026, 13:18 UTC≈1,330 views1 reactionsread 12 November 2026
Photo

🎙️ OpenAI官宣:12月11日停用旧版语音模式,全面转向GPT-Live OpenAI今日宣布,将于2026年12月11日正式停用ChatGPT中的Advanced Voice Mode(高级语音模式)和Standard Voice Mode(标准语音模式),全面转向新一代语音模型GPT-Live。 ▫️ GPT-Live于今年7月推出,采用全双工架构,允许ChatGPT在倾听用户说话的同时进行语音回复,对话更自然流畅。 ▫️ 自GPT-Live发布以来,ChatGPT语音功能使用量已接近翻倍,大多数语音用户已转向GPT-Live。 ▫️ 12月11日起,旧版语音模式将从ChatGPT“设置-语音”选项中移除,用户将自动切换至GPT-Live。 ▫️ 历史语音对话记录仍会保留,可继续通过文字或GPT-Live接续。 ▫️ 例外:实时视频和屏幕共享功能,以及自定义GPT语音对话,仍继续使用Advanced Voice M…

❤1

Signed KISS NAISI

Showing the 12 most recent of 187 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.

Posts edited after publishing

@inaisi edited 1 post after it first published — the same permalink now carries different wording than the one this register originally read, caught because our own crawl held a copy of the earlier text.

An edit is not deception. Typo fixes, price updates and corrections look exactly like this too — this register can tell you the wording changed and when, not why. How this is measured.

First edit seen
25 August 2026
Most recent edit
25 August 2026

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

Appears in Telegram’s recommendations for other channels

The reverse of the list above, and a different kind of signal. This does not require this channel to have ever been asked about directly — each row below is a channel we DID ask Telegram about, whose Telegram-generated list happened to include this one. A channel can appear here with an empty list above it, because being named by someone else’s query is independent of having been queried itself.

🍟 整点薯条: 频道
@GetSomeFriesChannel · 20,341
Telegram ranks this channel #8 of 45 here — alongside 44 others — read 29 September 2026
懒猫的频道
@lanmaoshare · 20,718
Telegram ranks this channel #9 of 27 here — alongside 26 others — read 3 October 2026
广告必须死
@Aa28413761 · 26,843
Telegram ranks this channel #10 of 37 here — alongside 36 others — read 13 September 2026
֍可莉日常֎
@ibilibili · 49,570
Telegram ranks this channel #16 of 40 here — alongside 39 others — read 14 September 2026
iOS宝藏
@iosrxwy · 100,301
Telegram ranks this channel #17 of 28 here — alongside 27 others — read 31 August 2026
iOS优质应用
@ioskk · 50,666
Telegram ranks this channel #18 of 35 here — alongside 34 others — read 25 August 2026
小果子|iOS越狱交流频道
@guozhiapp · 21,887
Telegram ranks this channel #23 of 25 here — alongside 24 others — read 20 September 2026
叮当猫のiOS资源分享频道
@ddm1023 · 50,362
Telegram ranks this channel #30 of 41 here — alongside 40 others — read 26 August 2026
不止QuantumultX
@Quantumultxxxx · 22,065
Telegram ranks this channel #31 of 37 here — alongside 36 others — read 25 September 2026
Surge & Loon & QX 脚本收集
@NobyDa · 64,555
Telegram ranks this channel #33 of 42 here — alongside 41 others — read 21 August 2026
Faker | iKun聚集地
@scriptalking · 27,954
Telegram ranks this channel #39 of 41 here — alongside 40 others — read 10 September 2026
Loon News
@LoonNews · 48,288
Telegram ranks this channel #39 of 49 here — alongside 48 others — read 27 August 2026
折腾啥
@zhetengsha · 53,830
Telegram ranks this channel #40 of 50 here — alongside 49 others — read 26 August 2026

This channel appears in 13 seed channels' Telegram-generated recommendation lists in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.

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

“奶思🍒资源分享|频道” (@inaisi), 14,221 subscribers as measured 11 November 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.