苹果短暂从全球市场下架Telegram然后重新上架,目前尚不清楚具体原因 https://www.landian.news/~
Channel
tg生态观察 ٭✡️⚝✹✸✶✷✴️✧⊛🔯❂⍣≛✨🇻🇳
@tgsucks
On this record: Topic · Growth · Engagement · Reactions · Posts · Citations · Cite this entry
2,050subscribers
+23 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 | -1001124604036 |
|---|---|
| Type | Channel |
| Username | @tgsucks |
| Created | 26 August 2017 — measured — cross-checked against a third-party dataset (TGDataset) |
| First recorded | 6 August 2026 |
| Last confirmed live | 16 September 2026 |
| Measurements held | 11 |
| Confirmed unchanged | 1 time, most recently 16 September 2026 |
| On Telegram | t.me/tgsucks |
Topic
Technology — 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 16 September 2026 and assigned it the closest of 31 fixed categories, at 61% 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
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 16 Sept 2026, 14:40 | 2,050 | +5 |
| 9 Sept 2026, 06:18 | 2,045 | -2 |
| 31 Aug 2026, 16:16 | 2,047 | -3 |
| 28 Aug 2026, 05:27 | 2,050 | -2 |
| 24 Aug 2026, 20:54 | 2,052 | -4 |
| 20 Aug 2026, 21:22 | 2,056 | -7 |
| 18 Aug 2026, 07:22 | 2,063 | +40 |
| 12 Aug 2026, 05:52 | 2,023 | -3 |
| 9 Aug 2026, 13:12 | 2,026 | -2 |
| 6 Aug 2026, 17:50 | 2,028 | +1 |
| 6 Aug 2026, 14:47 | 2,027 | first reading |
Engagement
19 posts held, back to 12 June 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 2 pages 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 19 posts for this entry, the most recent from 4 August 2026. An engagement rate over an empty window would be a number about nothing.
Reaction mix
23 reactions across 10 posts, in 3 distinct kinds. The most used accounts for 47.8% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 😁 | 11 | 47.8% | |
| ❤ | 7 | 30.4% | |
| 💩 | 5 | 21.7% |
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 12 of the 19 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 23 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 19 most recent posts we hold, published 12 June 2026 to 4 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
杜叔叔似乎打赢复活赛了
❤1😁1
Telegram 已从苹果 iOS 应用商店中下架 即时通讯应用Telegram已从全球苹果 iOS 应用商店中下架,现有已安装仍可正常使用。 —— Telegram
poc: t.me/kimifuckingbot
❤1
https://fixupx.com/Fried_rice/status/2080200610985689222
Posted without readable text
❤1
t.me 于昨日被 serverHold 而无法解析;现已恢复。 - serverHold 代表这是由注册局(而非域名注册服务商)发起的行为。 - .me 域名的管理者 domain .ME 回复称 t.me 域名被封锁是由于 OFAC 合规方面的原因。 twitter.com/domainME/~ #Telegram
💩1
domain .ME 解释:一个 Telegram 频道被美国制裁导致 t.me 域名被停止解析。 - .me 是欧洲国家黑山的国别域名 (ccTLD)。 - domain .ME 是 .me 域名的注册局。 twitter.com/domainME/~ thread: /4884 #Telegram #TLD #US
💩2❤1
Telegram Serverless (Score: 150+ in 10 hours) Link: https://readhacker.news/s/6Yz3g Comments: https://readhacker.news/c/6Yz3g
❤1
t.me 域名被 .me 注册局 serverHold 导致目前无法解析,个人猜测可能是有人举报 Telegram 黑灰产官方一直不处理,一怒之下举报去了注册局,注册局给处理了,那杜叔叔咋办呢?
但是如果是举报被处理的话,为啥只封了 t.me 而不是 telegram.me 一起封?
杜罗夫在巴黎第四次接受讯问,持续超六小时 Telegram 创始人帕维尔·杜罗夫日前在巴黎再度接受讯问,时长超过 6 小时。这是自 2024 年 8 月被正式指控以来,他第四次接受法国司法部门问讯。他的三名律师随后表示,近两年过去,仍无任何证据支持相关指控,并已在法国及欧洲司法机构提出投诉。 法国当局指控杜罗夫未充分审核平台内容且未配合执法部门,认为其涉嫌与儿童色情传播、毒品交易和诈骗等犯罪有关联。巴黎检察官今年 5 月表示,调查仍在进行中,杜罗夫仍受司法控制。不过,自 2025 年 11 月起,法国已解除对他的行动限制,他可自由离境。 Caliber 🌸 在花频道 · 茶馆水群 · 投稿通道
😁5❤1
Showing the 12 most recent of 19 posts we hold for @tgsucks. 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
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
Republishes
Channels on the register whose posts this channel has forwarded.
@hatschannel · 3,0853 posts每日消费电子观察
@CE_Observe · 74,7942 posts层叠 - The Cascading
@outvivid · 9,0092 posts烧饼博客 & 论坛
@sbDOTsb · 1,7032 postsTelegram Alpha
@tg_alpha · 5322 postsBeta Info 中文
@betainfocn · 2,1601 postfree347 免费资源分享
@free347 · 26,8961 postHacker News
@hacker_news_feed · 29,6821 post厘米碎碎念
@limisay · 3,3481 postSoha 的日常
@sohadays · 4,7471 post风向旗参考快讯
@xhqcankao · 163,2381 post
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 2 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.
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 16 September 2026 — this entry's latest reading, not the date you are reading this.
“tg生态观察 ٭✡️⚝✹✸✶✷✴️✧⊛🔯❂⍣≛✨🇻🇳” (@tgsucks), 2,050 subscribers as measured 16 September 2026. Telegram Register, tgregister.com/channel/tgsucks.
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.