Telegram RegisterThe public register of Telegram

Channel

卖动的摸鱼日常

@MaiTungTM_Notes

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

2,557subscribers

+7 since we began measuring on 6 August 2026

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

Register entry

Telegram ID-1001232994537
TypeChannel
Username@MaiTungTM_Notes
Created29 May 2021measured — cross-checked against a third-party dataset (ext.tg_channel)
First recorded6 August 2026
Last confirmed live12 August 2026
Measurements held4
Confirmed unchanged1 time, most recently 12 August 2026
On Telegramt.me/MaiTungTM_Notes

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 11 August 2026 and assigned it the closest of 31 fixed categories, at 72% 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 (5 of the pairs behind the counts below)
Posted firstThenOverlapGap
@MaiTungNews/314831 Jul 2026, 11:42 UTC@MaiTungTM_Notes/12944 · this entry31 Jul 2026, 11:42 UTC1.00under a minute
@MaiTungNews/31504 Aug 2026, 15:28 UTC@MaiTungTM_Notes/12957 · this entry4 Aug 2026, 15:29 UTC1.00under a minute
@MaiTungNews/31515 Aug 2026, 04:25 UTC@MaiTungTM_Notes/12958 · this entry5 Aug 2026, 04:25 UTC1.00under a minute
@MaiTungNews/31526 Aug 2026, 02:25 UTC@MaiTungTM_Notes/12959 · this entry6 Aug 2026, 02:25 UTC1.00under a minute
@MaiTungNews/31536 Aug 2026, 09:41 UTC@MaiTungTM_Notes/12960 · this entry6 Aug 2026, 09:41 UTC1.00under a minute
Every channel this entry shares post bodies with
ChannelMatching postsText overlapTypical gapPublished first
@MaiTungNews7 (7/7 hand-verifiable sample passed)1.00under a minute@MaiTungNews (70)

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. 3 of the 6 matches recorded here fall after that date and carried no header when we read them. The rest predate reliable capture and are not evidence either way.

“Published first” means first in this corpus. We hold 10 comparable posts for this entry, running 31 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 @MaiTungNews. That is a statement about our reading window, not a claim of authorship.

Recorded under the key clone_copy, 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

2,5502,5572,553.56 August 2026 — 2,550 subscribers6 August 2026 — 2,552 subscribers10 August 2026 — 2,553 subscribers12 August 2026 — 2,557 subscribers6 August 202612 August 2026
4 measurements spanning 7 days, net +7. 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 2,549–2,558 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
12 Aug 2026, 18:472,557+4
10 Aug 2026, 04:472,553+1
6 Aug 2026, 19:402,552+2
6 Aug 2026, 05:522,550first reading

Engagement

25 posts held, back to 31 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 2 pagesof Telegram’s post history, 20 posts per page.

ERR · 30 days
19.1%
avg views ÷ 2,557 subscribers
Avg views / post
488
25 posts measured
Reaction rate
1.73%
reactions ÷ views · ER floor
Posts in window
25
of 25 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 10 of 25 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 7 August 2026
Posts held25 (31 July 20267 August 2026)
Views total12,210
Reactions total62
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken7 Aug 2026, 16:24 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

60 reactions across 8 posts, in 7 distinct kinds. The most used accounts for 41.7% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
😁2541.7%
🤣2135.0%
🤬610.0%
😱35.00%
👍23.33%
🔥23.33%
11.67%

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

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

7 Aug 2026, 12:29 UTC72 views1 reactionsread 7 August 2026
File

QQ v9.3.35 (15560) TargetSdkVersion 34 原生库 arm64-v8a 更新日志 - QQ 宠物焕新回归,支持多种养宠互动玩法,解锁社交新体验。 官网下载 | QQ Updates #QQ@QQUpdates

👍1

Signed QQ Updates

7 Aug 2026, 12:29 UTC69 views1 reactionsread 7 August 2026
File

Windows QQ v9.9.33.52074 架构 x64 更新日志 - 修复了一些已知问题。 官网下载 | x86 下载 | arm64 下载 | 其他平台 | QQ Updates #WindowsQQ@QQUpdates

👍1

Signed QQ Updates

7 Aug 2026, 10:36 UTC134 views1 reactionsread 7 August 2026

#News #安卓 #小米 #HyperOS 小米澎湃 HyperOS 4 系统更多特性首曝:超级小爱专家模式、全新融合设备中心等

1

Signed 卖报社

7 Aug 2026, 05:02 UTC154 viewsread 7 August 2026
Photo

这是什么软件 https://tv.cctv.com/2026/08/02/VIDEZJoabCvJXzXSA2Jrx5d7260802.shtml

6 Aug 2026, 16:09 UTC194 viewsread 7 August 2026
Forwarded from @WeeklyFreeEpicGamesPhoto

🌐Epic Games Mobile 本周赠送《巴别号漫游指南》 ➡️领取链接:一键领取 | Android | iOS 🕚领取时间截止至 2026/08/13 23:00 #喜加一 #Game #EpicGamesMobile

Signed Epic 每周白嫖资讯

6 Aug 2026, 16:09 UTC176 viewsread 7 August 2026
Forwarded from @WeeklyFreeEpicGamesPhoto

🌐Epic Games 赠送《Spider Fox》 ➡️领取链接 🕚领取时间截止至 2026/08/13 23:00 #喜加一 #Game #EpicGames

Signed Epic 每周白嫖资讯

6 Aug 2026, 16:09 UTC151 viewsread 7 August 2026
Forwarded from @WeeklyFreeEpicGamesPhoto

🌐Epic Games 本周赠送《我们曾一起在这里》 ➡️领取链接 🕚领取时间截止至 2026/08/13 23:00 #喜加一 #Game #EpicGames

Signed Epic 每周白嫖资讯

6 Aug 2026, 16:05 UTC159 viewsread 7 August 2026
Forwarded from @WeeklyFreeEpicGamesPhoto

🌐Epic Games 本周赠送《Beacon Pines》 ➡️领取链接 🕚领取时间截止至 2026/08/13 23:00 #喜加一 #Game #EpicGames

Signed Epic 每周白嫖资讯

6 Aug 2026, 13:25 UTC218 viewsread 7 August 2026
Photo

R 星《GTA 6》前瞻预告定档北京时间 8 月 28 日首播 今日晚间,Rockstar Games 通过官网发布公告:《侠盗猎车手 6:分量十足的一瞥》将于美东时间 8 月 27 日下午 3 时(北京时间 28 日凌晨 3 时)率先在 Netflix 播出。 根据 R 星官方 B 站主页介绍,该预告片将于 8 月 28 日北京时间上午 11 时推出。「对 Grand Theft Auto VI 分量十足的一瞥,锐意革新的 Grand Theft Auto 系列迎来下一步演化。带有简体中文字幕。」 《GTA 6》定于 11 月 19 日登陆 PlayStation 5 和 Xbox Series X|S,目前已在 R 星官网开放预购。 (IThome) #News #游戏资讯 #GTA6

Signed 卖报社

6 Aug 2026, 09:41 UTC270 views23 reactionsread 7 August 2026

人民日报:用「Token」还是「词元」,事关科技话语权 人工智能飞速迭代,技术更新速度远超语言规范的完善节奏。当下,大量人工智能相关英文术语未经本土化转化,便直接涌入公共传播、日常交流等场景,字母缩写频繁替代汉语表达。这不仅改变着大众的语言习惯,更暗藏科技话语权旁落、母语体系被消解的深层危机,守住母语根基、规范科技语言已然成为人工智能时代的重要课题。 汉语历来开放包容,过往「电脑」「互联网」等外来概念的本土化译名,精准贴合汉语表意逻辑,深度融入民族语言体系。但如今 Token、Agent、LLM 等英文符号大量出现,仅作为单纯符号存在,不具备汉语形音义统一的特质,既无法望文知义,也缺乏文化底蕴。这些无内核的术语频繁出现在教材、政策、媒体内容中,不断挤压汉语的表意空间,不仅抬高了大众理解前沿科技的门槛,加剧数字鸿沟,也逐步侵蚀汉语体系的完整性与传承性。 更深远的影响,体现在自主科技话语体系的缺失。语言塑造思维,长期依附外来术语、

🤣21😁2

Signed 卖报社

6 Aug 2026, 02:25 UTC≈1,230 views8 reactionsread 7 August 2026
Photo

DeepSeek:计划近期整体上调 API 服务的定价,预计涨幅较大 DeepSeek 今日公告:「计划近期整体上调 DeepSeek API 服务的定价,预计涨幅较大,请合理安排您的使用。具体方案以正式通知为准。」 当前,DeepSeek 的 API 价格按「输入 Token」和「输出 Token」分别计费,且根据「缓存命中」与「缓存未命中」情况,价格有所差异。 (IThome) #News #AI #Deepseek

😁5😱3

Signed 卖报社

Showing the 12 most recent of 25 posts we hold for @MaiTungTM_Notes. 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 — 333,708 of 1,151,006entries 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.

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 1 registered channel — 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.

Named by

Channels on the register whose posts name this channel's handle.

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

“卖动的摸鱼日常” (@MaiTungTM_Notes), 2,557 subscribers as measured 12 August 2026. Telegram Register, tgregister.com/channel/MaiTungTM_Notes.

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.