Telegram RegisterThe public register of Telegram
Telegram profile photo for 你不知道的那些事

Channel

你不知道的那些事

@justlook2024

On this record: Topic · Observations · Channels linked by matching posts · Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry

6,019subscribers

-152 since we began measuring on 7 August 2026

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

Register entry

Telegram ID-1002401016509
TypeChannel
Username@justlook2024
CreatedBetween 1 September 2024 and 31 March 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live14 November 2026
Measurements held27
Confirmed unchanged1 time, most recently 14 November 2026
On Telegramt.me/justlook2024

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 12 September 2026 and assigned it the closest of 31 fixed categories, at 99% 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 3 other registered channels. This entry also sits inside a group of 11 channels linked by matching posts, directly or through other channels in the group; two members of the group may share no posts with each other. 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 (6 of the pairs behind the counts below)
Posted firstThenOverlapGap
@inside1024/891653 Nov 2026, 15:56 UTC@justlook2024/53087 · this entry3 Nov 2026, 15:57 UTC1.00under a minute
@inside1024/891693 Nov 2026, 16:07 UTC@justlook2024/53089 · this entry3 Nov 2026, 16:07 UTC1.00under a minute
@inside1024/891783 Nov 2026, 20:10 UTC@justlook2024/53099 · this entry3 Nov 2026, 20:10 UTC1.00under a minute
@inside1024/892564 Nov 2026, 16:42 UTC@justlook2024/53158 · this entry4 Nov 2026, 16:43 UTC1.00under a minute
@inside1024/892715 Nov 2026, 00:26 UTC@justlook2024/53168 · this entry5 Nov 2026, 00:26 UTC1.00under a minute
@inside1024/893255 Nov 2026, 13:38 UTC@justlook2024/53215 · this entry5 Nov 2026, 13:38 UTC1.00under a minute
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
@inside102427 (8/8 hand-verifiable sample passed)0.99under a minute@inside1024 (27–0)
@Gaoxiaoman19 (8/8 hand-verifiable sample passed)1.00under a minute@Gaoxiaoman (15–4)
@DNYQWCG5 (5/5 hand-verifiable sample passed)0.981.9 hoursthis entry (5–0)

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. 42 of the 42 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 106 comparable posts for this entry, running 6 August 2026 to 5 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 11 channels, the one whose matching posts we hold earliest is @liangxing365. That channel is not among the channels listed above, so this entry may share no posts with it and this does not say where this entry’s content came from. It is a statement about our reading window, not a claim of authorship.

Recorded under the keys clone_copy · clone_source, last confirmed 16 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 11 registered channels linked by matching posts, directly or through other channels in the group. This channel may share no posts with some of the channels listed below, and listed channels may share none with each other. 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

6,0106,1716,090.57 August 2026 — 6,171 subscribers7 August 2026 — 6,171 subscribers10 August 2026 — 6,170 subscribers13 August 2026 — 6,154 subscribers17 August 2026 — 6,160 subscribers20 August 2026 — 6,158 subscribers23 August 2026 — 6,151 subscribers27 August 2026 — 6,137 subscribers30 August 2026 — 6,130 subscribers2 September 2026 — 6,127 subscribers6 September 2026 — 6,126 subscribers11 September 2026 — 6,109 subscribers15 September 2026 — 6,094 subscribers19 September 2026 — 6,082 subscribers28 September 2026 — 6,041 subscribers6 October 2026 — 6,031 subscribers12 October 2026 — 6,019 subscribers16 October 2026 — 6,010 subscribers19 October 2026 — 6,015 subscribers22 October 2026 — 6,020 subscribers25 October 2026 — 6,024 subscribers27 October 2026 — 6,038 subscribers30 October 2026 — 6,040 subscribers3 November 2026 — 6,054 subscribers6 November 2026 — 6,056 subscribers10 November 2026 — 6,043 subscribers14 November 2026 — 6,019 subscribers6,0197 August 202614 November 2026
27 measurements spanning 99 days, net -152. 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 5,986–6,195 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 27
Measured (UTC)SubscribersChange
14 Nov 2026, 15:556,019-24
10 Nov 2026, 01:366,043-13
6 Nov 2026, 05:306,056+2
3 Nov 2026, 00:366,054+14
30 Oct 2026, 15:066,040+2
27 Oct 2026, 23:596,038+14
25 Oct 2026, 08:106,024+4
22 Oct 2026, 15:596,020+5
19 Oct 2026, 09:296,015+5
16 Oct 2026, 01:576,010-9
12 Oct 2026, 20:466,019-12
6 Oct 2026, 00:226,031-10
28 Sept 2026, 18:366,041-41
19 Sept 2026, 06:196,082-12
15 Sept 2026, 06:216,094-15
11 Sept 2026, 10:196,109-17
6 Sept 2026, 20:206,126-1
2 Sept 2026, 05:136,127-3
30 Aug 2026, 05:066,130-7
27 Aug 2026, 00:036,137first reading

Engagement

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

ERR · 30 days
0.324%
avg views ÷ 6,019 subscribers
Avg views / post
19.5
70 posts measured
Reaction rate
1.54%
reactions ÷ views · ER floor
Posts in window
70
of 153 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 2 of 70 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 5 November 2026
Posts held153 (6 August 2026 – 5 November 2026)
Views total1,366
Reactions total1
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken5 Nov 2026, 17:12 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
16m 12s
Average length
1m 37s

Measured directly from 10 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 reaction across 1 post, in 1 kind.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
❤1100.0%

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

Measured over the 153 most recent posts we hold, published 6 August 2026 to 5 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: 0 of 70 posts held from the last 30 days (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).

5 Nov 2026, 15:37 UTC19 viewsread 5 November 2026
Photo

俄乌打到最后,极有可能复刻芬兰模式,乌克兰被占领土是收不回来了。就像当年的芬兰一样,忍痛割让领土,摆脱大鹅的纠缠,才能正常发展经济,然后加入欧盟。 咱们先说说芬兰当年到底发生了啥。 当年苏联和芬兰开打冬季战争。苏军兵力多,装备强,想把边界往外推,给自己城市留一块缓冲地带。芬兰军队依托森林、雪地和防线防守,给苏军造成不小伤亡。可两边体量差得太远,芬兰撑不住长期消耗。 之后双方签了莫斯科和平协定。芬兰割让卡累利阿地峡、维堡、拉多加湖沿岸这些地方,占本国一成左右国土,四十多万当地居民搬到芬兰剩下的区域。这块丢出去的土地,之后一直没有收回来。 没过几年,芬兰跟着德国对苏联作战,想着拿回失地。一开始芬军往前推进,打到后来苏军大规模反攻,芬兰再次战败。 又签停战协议,再加割让佩琴加地区,还要给苏联支付物资赔款,并且动手把境内德军赶出去。 仗打完之后,芬兰没有接着和苏联死磕。它和苏联签友好条约,承认对方的安全诉求,不搞针对苏联的军事结盟。 芬…

5 Nov 2026, 15:29 UTC13 viewsread 5 November 2026
Photo

一个行业,一个秘密,记下来,少走弯路! 内幕消息|优质资源 | 优质信息

5 Nov 2026, 15:12 UTC20 viewsread 5 November 2026
Photo

不是,怎么没人明白,尹希加入OpenAI是北美教职每七年的一次sabbatical leave,压根就没从哈佛离职。 这种七年一次的leave是制度,完全可以自己支配,绝大多数教授会找个其他大学继续当visiting professor,只不过尹希选择了去OpenAI干了大半年而已。 怎么一堆大傻子又跑出来说尹希到处跳槽,服了。 内幕消息|优质资源 | 优质信息

5 Nov 2026, 14:29 UTC23 viewsread 5 November 2026
Photo

一家中国工厂为美国生产了超十万件印有“抵制中国”字样的T恤。 还是“中国制造”😆😆😆 围观这草台班子的世界 @justlook2024

5 Nov 2026, 13:38 UTC34 viewsread 5 November 2026

苏联在那边虎视眈眈,核武器都快追上美国了。 这个时候不跟中国缓和,难道等着被苏联和越南两头拖死?尼克松不是慈善家,他是被逼的,开门是当时美国能选的最好的一条路。 说白了,这就好比你当年打麻将缺个角,拉了个新手进来凑局,结果人家在家练了几十年,现在水平比你还高,你回头怪当年拉他入局的人,这就有点不讲理了。 真正的问不是谁开的门,而是门开了之后,人家靠自己的本事跑出来了。 你当年没拦住,现在回头骂开门的前辈,这棋下得就有点输不起了。 内幕消息|优质资源 | 优质信息

5 Nov 2026, 13:38 UTC35 views1 reactionsread 5 November 2026
Photo

特朗普曾说,要不是尼克松 "释放" 了中国,在外交上破冰,打开了中国的大门,现在也就不会有这么大的麻烦,就不会有一个这么强大的对手。 上世纪七十年代初的美国,已经被越南战争拖到了崩溃边缘。 累计 2000 亿美元的战争开支砸进东南亚丛林,几十万美军陷在热带雨林里动弹不得,国内反战游行此起彼伏,社会撕裂到了极点。 但尼克松心里跟明镜似的,他头疼的不止越南这一件事。 那几年正是苏攻美守的阶段,苏联的核导弹数量追了上来,在全球到处扩张,美国有点扛不住了。 你想啊,西边要防苏联,南边陷在越南,东边还跟中国憋着气 —— 这就好比一个人同时被两个壮汉堵在胡同里,你总得先松一头,不然两个一起上,那真就得交代在那儿了。 所以尼克松打了个算盘:拉着中国一起来压苏联。 说干就干,先是乒乓外交,小球转大球,然后基辛格秘密访华,保密工作做得极其到位,连国务卿都被蒙在鼓里。 1972 年 2 月,尼克松真的飞到北京,一下飞机就伸手跟周恩来握,那只手据说在…

❤1

5 Nov 2026, 13:28 UTC29 viewsread 5 November 2026
Photo

属于日本🇯🇵经济的黄金时代彻底一去不复返。 1980年代末期,日本曾经是全世界半导体产业绝对的霸主。 1988年巅峰期,日本企业占全球半导体销售额高达50.3%。那时候,全球每卖出两颗芯片,就有一颗来自日本企业。 但随着韩国与台湾半导体企业迅速崛起,到了2025年,根据TechInsights对全球前50大半导体企业的统计,日本企业的销售额占比已降至只剩5%。 内幕消息|优质资源 | 优质信息

5 Nov 2026, 13:17 UTC28 viewsread 5 November 2026
Photo

靠打工,几乎不可能成为真正的富人。很多人奋斗了一辈子,拼命升职加薪,却忽略了一个最基本的财富常识: 真正的大财富,往往来自拥有资产。 最近美国普林斯顿大学经济学教授 Owen Zidar 接受彭博社(Bloomberg)访谈,介绍了他与芝加哥大学教授 Eric Zwick 合著的畅销新书《The Everywhere Millionaire》(遍布各地的百万富翁)。 他们利用美国财政部的税务数据,研究了一个长期被忽视的富豪群体。美国有大量身家几千万美元的富人,既没有创办什么高科技公司,也不是什么华尔街金融大亨。他们可能只是经营着一家汽车经销商、牙科诊所、水管维修公司,甚至是一家专门帮人铲雪的企业。 这些看起来毫不起眼的传统生意,在美国🇺🇸却能在几十年里创造出惊人的财富。研究发现,在拥有2500万至1亿美元财富的人群中,私人企业是非常重要的财富来源。这些富人的平均年龄约62岁,很多人花了二三十年,甚至一辈子的时间,把一家普通的小企…

5 Nov 2026, 13:14 UTC24 viewsread 5 November 2026
Photo

分享一个医药圈的行业内幕: 经常吃避孕药的都知道,那一粒药非常小,芝麻绿豆点大小让很多人怀疑是不是效果不够。 但很多其他疾病的药,又做的非常大,临床上直径快1厘米的片剂,让很多人难以下咽。 为什么会有这种区别呢,其实是迎合人的心理状态,无论避孕药还是其他片剂,绝大部分比例都是淀粉,有效的药物成分都是毫克级别的。 那为什么要把前者做那么小呢,其实就是减轻服用者的心理压力,有些人一觉得是终止妊娠就会非常害怕,但是一看到药片那么小,潜意识就有安全感。 相反,临床上其他重大疾病的片剂,就是要做的足够大,给服用者心理暗示这药足够猛足够有效,最好像中药那样一碗下去药到病除。 内幕消息|优质资源 | 优质信息

5 Nov 2026, 13:07 UTC19 viewsread 5 November 2026
Photo

这8种常见的洗脑术,一定要看懂! 1、恐惧洗脑:先制造焦虑,再让你相信只有他能救你。 2、信息洗脑:封锁其他声音,让你只能接受他的观点。 3、重复洗脑:一句反复灌输,听多了连谎言都信了。 4、情感洗脑:用“我都是为你好”,逼你服从他的安排。 5、打压洗脑:先摧毁你的自信,再偶尔给点甜头,让你离不开他。 6、对立洗脑:把外界塑造成敌人,让你只相信自己人。 7、控制洗脑:不断否定你的判断,直到你不敢自己做决定。 8、愧疚洗脑:把所有错误推给你,让你觉得亏欠他一辈子。 内幕消息|优质资源 | 优质信息

5 Nov 2026, 11:46 UTC21 viewsread 5 November 2026
Photo

这就是AI圈慕容复吗? @justlook2024 #内幕消息

5 Nov 2026, 11:46 UTC19 viewsread 5 November 2026
Photo

太ne了,真有他的! @justlook2024 #内幕消息

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

Mentions

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

“你不知道的那些事” (@justlook2024), 6,019 subscribers as measured 14 November 2026. Telegram Register, tgregister.com/channel/justlook2024.

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.