Telegram RegisterThe public register of Telegram
Telegram profile photo for 临境 Liminal Emby 通知频道

Channel

临境 Liminal Emby 通知频道

@LiminalChannel

On this record: Topic · Observations · Channels linked by matching posts · Growth · Engagement · What this channel posts · Reactions · Posts · Posts edited after publishing · Posts recorded as deleted · Citations · Cite this entry

10,968subscribers

+1,639 since we began measuring on 7 August 2026

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

Register entry

Telegram ID-1002670085865
TypeChannel
Username@LiminalChannel
CreatedBetween 1 March 2025 and 31 July 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live11 November 2026
Measurements held45
Confirmed unchanged1 time, most recently 11 November 2026
On Telegramt.me/LiminalChannel

Topic

Other / unclassifiable — 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 11 September 2026 and assigned it the closest of 31 fixed categories, at 57% 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 (5 of the pairs behind the counts below)
Posted firstThenOverlapGap
@LiminalChannel/293 · this entry15 Jul 2026, 09:07 UTC@Luxrealm_Channel/8515 Jul 2026, 09:07 UTC1.00under a minute
@LiminalChannel/299 · this entry26 Jul 2026, 10:54 UTC@Luxrealm_Channel/9226 Jul 2026, 11:21 UTC1.0027 minutes
@LiminalChannel/300 · this entry27 Jul 2026, 08:49 UTC@Luxrealm_Channel/9327 Jul 2026, 08:50 UTC1.00under a minute
@LiminalChannel/313 · this entry13 Aug 2026, 18:14 UTC@Luxrealm_Channel/10213 Aug 2026, 18:15 UTC1.00under a minute
@LiminalChannel/314 · this entry15 Aug 2026, 07:13 UTC@Luxrealm_Channel/10315 Aug 2026, 07:14 UTC1.0072 seconds
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
@Luxrealm_Channel11 (8/8 hand-verifiable sample passed)1.00under a minutethis entry (10–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. 1 of the 1 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 19 comparable posts for this entry, running 1 July 2026 to 9 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 @LiminalChannel — 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 11 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

9,32910,96810,148.57 August 2026 — 9,329 subscribers7 August 2026 — 9,329 subscribers11 August 2026 — 9,350 subscribers13 August 2026 — 9,357 subscribers17 August 2026 — 9,392 subscribers20 August 2026 — 9,416 subscribers24 August 2026 — 9,438 subscribers27 August 2026 — 9,448 subscribers29 August 2026 — 9,468 subscribers2 September 2026 — 9,484 subscribers6 September 2026 — 9,498 subscribers11 September 2026 — 9,521 subscribers14 September 2026 — 9,536 subscribers18 September 2026 — 9,531 subscribers27 September 2026 — 9,588 subscribers5 October 2026 — 9,909 subscribers12 October 2026 — 10,231 subscribers14 October 2026 — 10,284 subscribers15 October 2026 — 10,303 subscribers16 October 2026 — 10,319 subscribers17 October 2026 — 10,336 subscribers18 October 2026 — 10,363 subscribers19 October 2026 — 10,394 subscribers20 October 2026 — 10,414 subscribers21 October 2026 — 10,431 subscribers22 October 2026 — 10,470 subscribers23 October 2026 — 10,498 subscribers24 October 2026 — 10,523 subscribers25 October 2026 — 10,563 subscribers26 October 2026 — 10,588 subscribers27 October 2026 — 10,629 subscribers28 October 2026 — 10,660 subscribers29 October 2026 — 10,678 subscribers30 October 2026 — 10,721 subscribers31 October 2026 — 10,758 subscribers1 November 2026 — 10,784 subscribers2 November 2026 — 10,801 subscribers3 November 2026 — 10,812 subscribers4 November 2026 — 10,835 subscribers5 November 2026 — 10,856 subscribers6 November 2026 — 10,868 subscribers7 November 2026 — 10,883 subscribers8 November 2026 — 10,901 subscribers9 November 2026 — 10,922 subscribers11 November 2026 — 10,968 subscribers7 August 202611 November 2026
45 measurements spanning 96 days, net +1,639. 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 9,083–11,214 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 45
Measured (UTC)SubscribersChange
11 Nov 2026, 23:0110,968+46
9 Nov 2026, 22:5410,922+21
8 Nov 2026, 11:0510,901+18
7 Nov 2026, 06:4910,883+15
6 Nov 2026, 07:1110,868+12
5 Nov 2026, 09:4910,856+21
4 Nov 2026, 12:1710,835+23
3 Nov 2026, 13:1510,812+11
2 Nov 2026, 14:2610,801+17
1 Nov 2026, 15:4110,784+26
31 Oct 2026, 12:3810,758+37
30 Oct 2026, 12:5910,721+43
29 Oct 2026, 10:3110,678+18
28 Oct 2026, 12:0910,660+31
27 Oct 2026, 11:1910,629+41
26 Oct 2026, 09:0010,588+25
25 Oct 2026, 07:0510,563+40
24 Oct 2026, 07:4610,523+25
23 Oct 2026, 11:0010,498+28
22 Oct 2026, 09:1410,470first reading

Engagement

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

ERR · 30 days
28.7%
avg views ÷ 10,968 subscribers
Avg views / post
3,150
5 posts measured
Reaction rate
0.039%
reactions ÷ views · ER floor
Posts in window
5
of 43 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 4 of 5 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 9 November 2026
Posts held43 (20 June 2026 – 9 November 2026)
Views total15,760
Reactions total5
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken11 Nov 2026, 21:57 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

Video runtime
20s
Average length
10s

Measured directly from 2 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

62 reactions across 20 posts, in 7 distinct kinds. The most used accounts for 59.7% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
❤3759.7%
🤯914.5%
👍812.9%
🫡34.84%
🤔23.23%
🥰23.23%
🎉11.61%

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

Measured over the 43 most recent posts we hold, published 20 June 2026 to 9 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: 1 of 5 posts held from the last 30 days (20.0%) 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).

9 Nov 2026, 16:10 UTC≈2,900 viewsread 11 November 2026
Photo

🎉临境享境双十一特惠来啦 🎉 双十一活动期间,全场享 88 折优惠 充值按照 1.13 倍倍率到账(实际折算约为 88 折) 本次优惠活动截止至 11 月 15 日,有需要的朋友可以按需充值 ———————————— ⭐️ 临境 Liminal EA 「10CNY/月起」 ✅ 60W+ 高码资源 ✅ 全新 EA 架构加持 ✅ 混合架构硬盘缓存新增至100T ⭐️ 享境 Luxrealm EA 硬盘服 「5CNY/月起」 ✅ 30W+ 精品中低资源 ✅ 全新 EA 架构加持 ✅ 全新硬盘架构秒拖秒拉无压力 ⚡购买入口点这里⚡ 临境 频道: @LiminalChannel 临境 群组: @Liminal_Emby 享境 频道: @Luxrealm_Channel 享境 群组: @Luxrealm_Group

27 Oct 2026, 14:48 UTC≈2,350 views0 reactionsread 11 November 2026

标准优化 Lite 线路 01 切换路由,尝试解决目前直链网络表现不佳的问题 PS:不要抱太大期待,这几天开会,好不了 再次提醒,我方不建议任何非刚需用户选购标准优化 Lite 线路套餐,本服推荐的最佳观看方式是海外网络环境,并非直连,并且不对直连质量作任何质量保证(除302之外)

26 Oct 2026, 10:44 UTC≈5,110 views1 reactionsread 11 November 2026
Photo

🌌 临境 Liminal 302 Next | 次世代直连媒体服务 下一代媒体平台,除了更多资源,还能带来什么? 过去数月,我们一直在尝试:让起播更快一点,让资源更新更及时一点,也让播放不再过度依赖单一网盘账户。 现在,我们很高兴地宣布: 临境 Liminal 302 Next 正式发布🎉 ✨ 不只是扩充资源,更是一次架构更新 突破性的 TMDB 持久化本地数据集与分布式秒传系统,与传统的「先转存、再刮削、再入库」不同,新系统将首页与搜索交给 TMDB,再与分布式资源集进行匹配。当您进入媒体详情页时,系统便会自动启动转存或秒传流程,为后续播放提前做好准备。 🚀 302 Next 的五大升级 ✔️ Next 技术架构赋能极速起播 提前准备播放资源,缩短等待时间,带来接近秒播的观看体验。 ✔️ 分布式秒传技术 不再局限于已经转存入库的内容,只要有资源在互联网上传,即可极速观看,无需人工刮削入库。 ✔️ 更强的容灾与…

❤1

21 Oct 2026, 14:41 UTC≈2,140 views2 reactionsread 11 November 2026

🌌 临境 Liminal 302 Next | 全新架构内测公告 下一代媒体平台,除了更多资源,还能带来什么? 过去数月,我们一直在尝试:让起播更快一点,让资源更新更及时一点,也让播放不再过度依赖单一网盘账户。 现在,我们很高兴地宣布: 临境 Liminal 302 Next 正式进入内测阶段! 🎉 ✨ 不只是扩充资源,更是一次架构更新 突破性的 TMDB 持久化本地数据集与分布式秒传系统,与传统的「先转存、再刮削、再入库」不同,新系统将首页与搜索交给 TMDB,再与分布式资源集进行匹配。当您进入媒体详情页时,系统便会自动启动转存或秒传流程,为后续播放提前做好准备。 🚀 302 Next 的五大升级 ✔️ Next 技术架构赋能极速起播 提前准备播放资源,缩短等待时间,带来接近秒播的观看体验。 ✔️ 分布式秒传技术 不再局限于已经转存入库的内容,只要有资源在互联网上传,即可极速观看,无需人工刮削入库。 ✔️ 更…

🥰2

18 Oct 2026, 15:15 UTC≈3,260 views2 reactionsread 11 November 2026

关于最近线路问题的说明 尊敬的各位用户 我方最近收悉部分用户关于标准优化 Lite 线路的卡顿问题,在此我方再次强调 1.标准优化 Lite 线路套餐系尽力优化但不保证绝对直连可用,恕不接受任何直连速度问题投诉 2.我方在近半年内没有对标准优化 Lite 套餐线路01 02进行过任何的降级行为和改动,标准优化套餐线路直连质量会受包括但不限于自身网络影响、运营商网络 QOS 限速、 GFW 阻断、CloudFlare 服务政策改变等多方面影响。 因此我方不建议任何非刚需用户选购标准优化 Lite 线路套餐,本服推荐的最佳观看方式是海外网络环境,并非直连,并且不对直连质量作任何质量保证(除302之外) 如您是使用代理环境连接临境 Liminal EA 或者享境 Luxrealm EA,请您在遭遇播放卡顿的情况多检查自身使用的代理服务是否稳定,根据最近反馈的实际情况,多数是用户使用的机场节点速度较慢或者分流问题。 如遇到…

❤2

3 Oct 2026, 17:16 UTC≈2,940 viewsread 11 November 2026

临境 Liminal 302 更新,请前往官网获取最新线路地址(就换了个端口)

1 Oct 2026, 04:51 UTC≈4,460 viewsread 11 November 2026

尊敬的各位用户: 由于进阶优化 Pro 线路套餐预计维护时间较长,为了不影响用户的使用,现为所有购买进阶优化 Pro 线路套餐的用户退款至账户余额(不折抵,直接按购买原价全额退,包括已经过期的用户) 用户可以自行转购临境 Liminal 302或者其他服务。 再次感谢您对本服的一贯支持和体谅,国庆快乐🎉

29 Sept 2026, 15:14 UTC≈4,480 viewsread 11 November 2026

临境&享境 更新日志 09.29 UTC+8 修复了数据库阻塞问题 修复了部分播放器可能存在的起播之后掉速为 300k/s 的问题 提升了图片加载速度

25 Sept 2026, 09:02 UTC≈4,800 views0 reactionsread 11 November 2026

302 复活吧,我的爱人😭 (去官网获取新地址) 临境、享境 Pro 线路套餐暂停新售,准备升级(已有订阅用户自动预补十五天时长)

24 Sept 2026, 14:26 UTC≈15,600 views6 reactionsread 11 November 2026
Photo

🎉临境享境中秋国庆双节特惠来啦 🎉 双节期间,全场享 88 折优惠 充值按照 1.13 倍倍率到账(实际折算约为 88 折) 本次优惠活动截止至 10 月 7 日,有需要的朋友可以按需充值 另外,截至今晚,现有用户的公费时长统一顺延 10 天,感谢大家一直以来的支持😝 假期难得,希望大家少看片,多陪陪家人😄 祝大家双节快乐,假期愉快!🎉(^▽^)🎉 ———————————— ⭐️ 临境 Liminal EA 「10CNY/月起」 ✅ 60W+ 高码资源 ✅ 全新 EA 架构加持 ✅ 混合架构硬盘缓存新增至100T ⭐️ 享境 Luxrealm EA 硬盘服 「5CNY/月起」 ✅ 30W+ 精品中低资源 ✅ 全新 EA 架构加持 ✅ 全新硬盘架构秒拖秒拉无压力 ⚡购买入口点这里⚡ 临境 频道: @LiminalChannel 临境 群组: @Liminal_E…

❤6

18 Sept 2026, 02:29 UTC≈2,860 viewsread 11 November 2026
Video

🎁 抽奖开始啦! 详情: 方式:⏰ 定时开奖 订阅:星星的集邮地, 享境 Luxrealm 2.0 截止:2026年9月20日 12:34:00 奖品:享境月卡 参与要求: • 订阅 享境 Luxrealm 2.0 • 订阅 星星的集邮地 现在可以参与这场抽奖啦,祝你好运!

Showing the 12 most recent of 43 posts we hold for @LiminalChannel. 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

@LiminalChannel 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
9 August 2026
Most recent edit
9 August 2026

Posts recorded as deleted after publishing

We recorded 1 post on @LiminalChannel as deleted — posts this register held that were missing from the channel’s public page on two separate reads, taken from different network addresses at least an hour apart.

A deletion is not wrongdoing. This register can see that a post it held is no longer on the channel’s public page, and when — not why. Expired ad placements, reposts, rotating links and corrections all look the same. This is a count of recorded detections, not an exact total: it misses deletions we could not see, because only a post we held and later re-read inside the page can be seen to go, and it may include a small number of wrong records. How this is measured.

First seen missing
15 August 2026
Most recent seen missing
15 August 2026
Median time before seen missing
4 days
Seen missing in the last 30 days
0

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

“临境 Liminal Emby 通知频道” (@LiminalChannel), 10,968 subscribers as measured 11 November 2026. Telegram Register, tgregister.com/channel/LiminalChannel.

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.