【特朗普说可能与金正恩在中国举行会晤,外交部:没有这方面的信息】 11月17日,外交部发言人郭嘉昆主持例行记者会。韩联社记者提问,当地时间16日,美国总统特朗普表示,他可能会在中国与朝鲜国务委员长金正恩举行会晤,但称目前尚不清楚金正恩委员长是否会前来,并表示这取决于中方。中方如何评价特朗普总统的上述言论?朝鲜和美国是否有举行会晤的可能性?郭嘉昆表示,我没有这方面的信息。
🤣8🤡2🖕1

Channel
@pelosi3
On this record: Topic · Observations · Growth · Engagement · What this channel posts · Reactions · Stars · Posts · Citations · Telegram's recommendations · Cite this entry
72,603subscribers
+2,823 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 31,623–100,000.
| Telegram ID | -1001382914383 |
|---|---|
| Type | Channel |
| Username | @pelosi3 |
| Description | 求存求活,最新的宏观政策,财经观点以及敏感信息分析交流,所有观点均为谈资,决策请慎重。群聊讨论请加https://t.me/pelosi233 备用频道,防走失,欢迎加入: https://t.me/pelosi333 投稿/合作请联系https://telega.io/c/pelosi3 购买广告: https://telega.io/c/pelosi3 信息分享不易,欢迎大佬打赏,USDT 投喂地址: TLKcoid5nLHViVfG1HvsArauWFdv2hXDeu |
| Created | Between 1 March 2018 and 31 August 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 6 August 2026 |
| Last confirmed live | 14 November 2026 |
| Measurements held | 66 |
| Confirmed unchanged | 1 time, most recently 14 November 2026 |
| On Telegram | t.me/pelosi3 |
International news — 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 20 August 2026 and assigned it the closest of 31 fixed categories, at 74% 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.
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.
Posts published here appear in near-verbatim form on 9 other registered channels. 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.
| Posted first | Then | Overlap | Gap |
|---|---|---|---|
| @pelosi3/28300 · this entry13 Aug 2026, 15:11 UTC | @neihanduanzi1/7258514 Aug 2026, 04:17 UTC | 1.00 | 13 hours |
| @pelosi3/28333 · this entry14 Aug 2026, 15:22 UTC | @neihanduanzi1/7267314 Aug 2026, 15:40 UTC | 1.00 | 18 minutes |
| @pelosi3/28496 · this entry20 Aug 2026, 14:53 UTC | @neihanduanzi1/7327121 Aug 2026, 04:12 UTC | 1.00 | 13 hours |
| @pelosi3/29683 · this entry16 Oct 2026, 08:30 UTC | @neihanduanzi1/8111616 Oct 2026, 09:03 UTC | 1.00 | 34 minutes |
| @pelosi3/29711 · this entry17 Oct 2026, 14:09 UTC | @neihanduanzi1/8131818 Oct 2026, 11:12 UTC | 1.00 | 21 hours |
| @pelosi3/29715 · this entry18 Oct 2026, 07:45 UTC | @neihanduanzi1/8132018 Oct 2026, 11:12 UTC | 1.00 | 3.5 hours |
| Channel | Matching posts | Text overlap | Typical gap | Published first |
|---|---|---|---|---|
| @neihanduanzi1 | 14 (7/8 hand-verifiable sample passed) | 1.00 | 8.8 hours | this entry (14–0) |
| @lilaoshibushinilaoshi | 10 (8/8 hand-verifiable sample passed) | 0.97 | 2.4 hours | @lilaoshibushinilaoshi (10–0) |
| @chigua_e | 9 (6/8 hand-verifiable sample passed) | 1.00 | 7.3 hours | this entry (9–0) |
| @tuigsc | 9 (8/8 hand-verifiable sample passed) | 1.00 | 23 hours | this entry (9–0) |
| @qiqubk | 9 (7/8 hand-verifiable sample passed) | 1.00 | 10 hours | this entry (9–0) |
| @cgsp1 | 7 (5/7 hand-verifiable sample passed) | 1.00 | 1.8 hours | this entry (7–0) |
| @luolicg9 | 7 (5/7 hand-verifiable sample passed) | 1.00 | 23 hours | this entry (7–0) |
| @chigg6885 | 6 (5/6 hand-verifiable sample passed) | 1.00 | 3 days | this entry (6–0) |
| @newszg_official | 5 (5/5 hand-verifiable sample passed) | 0.98 | 7.8 hours | this 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. 10 of the 10 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 1,140 comparable posts for this entry, running 5 August 2026 to 16 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.
Recorded under the keys clone_copy · clone_source, last confirmed 17 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.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 14 Nov 2026, 16:01 | 72,603 | +77 |
| 11 Nov 2026, 17:56 | 72,526 | +39 |
| 9 Nov 2026, 20:54 | 72,487 | -11 |
| 8 Nov 2026, 14:48 | 72,498 | +41 |
| 7 Nov 2026, 06:40 | 72,457 | +51 |
| 6 Nov 2026, 03:07 | 72,406 | +22 |
| 5 Nov 2026, 01:46 | 72,384 | +41 |
| 4 Nov 2026, 04:30 | 72,343 | +39 |
| 3 Nov 2026, 03:31 | 72,304 | +21 |
| 2 Nov 2026, 02:48 | 72,283 | +48 |
| 1 Nov 2026, 01:18 | 72,235 | +55 |
| 31 Oct 2026, 00:14 | 72,180 | +15 |
| 29 Oct 2026, 21:46 | 72,165 | +33 |
| 28 Oct 2026, 21:07 | 72,132 | +49 |
| 27 Oct 2026, 16:31 | 72,083 | +22 |
| 26 Oct 2026, 15:46 | 72,061 | +39 |
| 25 Oct 2026, 16:38 | 72,022 | +14 |
| 24 Oct 2026, 18:25 | 72,008 | +41 |
| 23 Oct 2026, 15:34 | 71,967 | +27 |
| 22 Oct 2026, 13:57 | 71,940 | first reading |
1,771 posts held, back to 5 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 207 pages of Telegram’s post history, 20 posts per page.
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.
| Window | Rolling 30 days · latest post in window 17 November 2026 |
|---|---|
| Posts held | 1,771 (5 August 2026 – 17 November 2026) |
| Views total | 2,019,338 |
| Reactions total | 19,005 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 17 Nov 2026, 08:39 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.
Lifetime counters from Telegram’s own channel header, read 17 November 2026 — not the date at the top of this page, which is when the subscriber count was last read. A count marked ≈ was rounded by Telegram before we ever saw it — t.me prints these counters in full below 1,000 and to three significant figures above, so ≈142,000 means somewhere between 141,500 and 142,499.
Measured directly from 51 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.
38,110 reactions across 990 posts, in 45 distinct kinds. The most used accounts for 26.0% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 😁 | 9,901 | 26.0% | |
| 🤡 | 5,625 | 14.8% | |
| 🎉 | 4,923 | 12.9% | |
| 👍 | 4,427 | 11.6% | |
| 🤣 | 3,052 | 8.01% | |
| ❤ | 2,123 | 5.57% | |
| 💩 | 1,703 | 4.47% | |
| 🤮 | 1,508 | 3.96% | |
| 🖕 | 832 | 2.18% | |
| 👏 | 604 | 1.58% | |
| 😱 | 548 | 1.44% | |
| 😴 | 461 | 1.21% | |
| 💊 | 417 | 1.09% | |
| 🥰 | 257 | 0.674% | |
| 🤩 | 240 | 0.63% | |
| 👎 | 234 | 0.614% | |
| 🙈 | 203 | 0.533% | |
| 🤪 | 172 | 0.451% | |
| 😢 | 96 | 0.252% | |
| 🔥 | 90 | 0.236% | |
| 25 further kinds | 694 | 1.82% |
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 990 of the 1,000 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 38,110 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 1,000 most recent posts we hold (the sample is capped at 1,000), published 17 September 2026 to 17 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.
A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @pelosi3. Telegram publishes the count on the public post preview alongside ordinary reactions, and this register reads it there. It is the only figure on this site that measures money moving rather than attention.
Stars are not reactions, and the two are never added. They are rendered in the same strip on Telegram and counted in the same shape, but one is a tap and the other is a purchase. The reaction totals and the engagement rate elsewhere on this page exclude every figure in this section, and no rate here is computed against a reaction count.
This is not revenue, and we publish no currency figure. What a Star costs a reader and what it pays a channel are different numbers, Telegram takes a share we cannot observe, and the terms have changed. Converting a Star count into money would be an estimate dressed as a measurement, so the count is where we stop.
Counted over the 1,000 most recent posts we hold for this entry (the sample is capped at 1,000), published 17 September 2026 to 17 November 2026. Star counts above 1,000 reach us in Telegram’s short form and carry the same three-significant-figure rounding as everything else on this page.
Telegram’s own ‘edited’ marker: 5 of 487 posts held from the last 30 days (1.03%) 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).
【特朗普说可能与金正恩在中国举行会晤,外交部:没有这方面的信息】 11月17日,外交部发言人郭嘉昆主持例行记者会。韩联社记者提问,当地时间16日,美国总统特朗普表示,他可能会在中国与朝鲜国务委员长金正恩举行会晤,但称目前尚不清楚金正恩委员长是否会前来,并表示这取决于中方。中方如何评价特朗普总统的上述言论?朝鲜和美国是否有举行会晤的可能性?郭嘉昆表示,我没有这方面的信息。
🤣8🤡2🖕1
以媒称美国在中东集结开战以来最大规模军事力量 据沙特媒体哈达斯(alhadath):以色列媒体报道称,美国在中东集结了自与伊朗开战以来最大规模的军事力量,该地区有17艘美国军舰、3艘航空母舰、5.5万名士兵和200架战斗机。美国在该地区的海上部署规模与3月对伊朗开战前的部署相当。
🤮4🎉2👍2🔥1😴1
本轮 APEC 美国企业家访华名单流出 特斯拉 / SpaceX CEO 马斯克 Visa CEO Ryan McInerney 万事达 CEO Michael Miebach UPS CEO Carol Tomé PayPal CEO Enrique Lores 普华永道全球主席 Mohamed Kande 德勤 CEO Joe Ucuzoglu 波音全球总裁 Brendan Nelson 谷歌全球政府事务负责人 Karan Bhatia 以上仅马斯克随特朗普同行,不在工商峰会名单上,但也会参加深圳 APEC 行程。所有信息根据各家媒体和企业声明梳理
😁3🖕1🤷1
【英伟达首席法律顾问同意在美国国会作证】 英伟达(NVDA.O)总法律顾问蒂姆·泰特(Tim Teter)已同意于12月2日向美国国会三个委员会的议员作证。英伟达的一位发言人向Politico证实了这一消息。此前,三位共和党议员——众议院外交委员会主席布莱恩·马斯特、情报委员会主席里克·克劳福德以及众议院美中战略竞争特设委员会主席约翰·穆勒纳尔——在周四致信泰特,要求他自愿参加一场闭门且有记录的访谈;信中明确表示,如果他拒绝,他们将发出传票强制其出席。
🎉12❤3🤮1😴1
特朗普要在中国见金正恩?老哥刚刚表示,他将前往中国参加 APEC 会议。这次除了跟习近平、普京见面以外,可能也会见到朝鲜领导人金正恩。 而上一次两人见面,还是 2019 年,在朝韩边境的板门店,这次跨越了足足 7 年。
🖕8😁5😴2
【民调:特朗普支持率深陷低谷,民主党大佬在党内也面临“失宠”】 根据路透社/益普索周一完成的一项民调,美国总统特朗普的支持率仍徘徊在其总统生涯的最低水平附近,而美国参议院民主党领袖在面临领导权挑战前夕,也显示出在党内失宠的迹象。这项为期四天的民调显示,32%的美国人对特朗普在白宫的表现表示认可。自10月中旬其支持率跌至职业生涯最低点31%以来,路透社/益普索连续四次民调中,该数据一直保持稳定。民调还显示,民主党受访者对本党在国会的领导层看法存在分歧,对参议院民主党领袖舒默持负面看法(43%)的人多于持正面看法(34%)的人。而众议院领袖杰弗里斯在党内的正面评价(40%)则高于负面评价(29%)。
😁22❤3💩2🤮1
【美情报:伊朗筹划在华盛顿引爆“脏弹”的计划 以备不时之需】 据CNN援引七名美国官员的话报道,美国最新情报显示,伊朗正在制定计划,考虑在华盛顿特区引爆所谓的“脏弹”或化学武器,以袭击特朗普政府高级官员。与此同时,官员仍在讨论伊朗是否有能力或是否会尝试实施此类阴谋。熟悉最新情报的消息人士表示,目前伊朗的相关筹划旨在为自己保留行动选项,并不意味着袭击即将发生。其中两名消息人士称,美国掌握的相关计划内容非常具体,涉及具体地点和目标,并已引发美国方面一系列紧急预案部署。白宫在一份声明中表示,美国正在“监控任何及所有潜在威胁,但目前美国本土不存在可信的威胁”。不过,美国官员认为,这些情报表明,在美国持续发动军事打击、实施严厉经济封锁之际,伊朗表现出令人担忧的升级冲突意愿。
🤡22😁5❤2👍2💊1🤩1
【特朗普:黄仁勋已吸取教训,不介意看到他重掌英伟达】 美国总统特朗普表示,航班停飞期间我在白宫。美国交通部长达菲干得很出色。在航班全面停飞事件后,我们需要资金以完成美国联邦航空管理局(FAA)的系统升级,亚洲之行期间的大型会晤主要聚焦经济议题,将会见俄罗斯总统普京。特朗普向记者表示,他不介意看到黄仁勋重掌英伟达,并补充说黄仁勋已经吸取了教训。
😁52🤡24❤5💩5🖕2
彭博社:中国央行收回中期资金,就货币宽松预期释放出警示信号
👍12😁4🖕3❤1
牛批牛批,谁说实体店的生意不好做的?! 强者从不抱怨环境🤣🤣🤣
❤19👻9😁4🍌3🎉1
美国总统特朗普:英伟达(NVDA.O)前CEO黄仁勋吸取了教训,不介意看到黄仁勋复职。
🤣26🤡14❤6🖕4😁3
【特朗普:《60分钟》节目关于伊朗的报道研究存在失实之处】 美国总统特朗普:《60分钟》节目的新管理层比前任更糟糕。最近关于伊朗战争初期一次袭击的研究报道存在失实之处。自2026年2月28日“史诗怒火”行动开始以来,伊朗已发射了8000至9000架单向攻击无人机。其中仅有2架突破防线,导致美军人员伤亡,这两起事件均发生在行动首日,目标分别是科威特和沙特阿拉伯。同样,伊朗还发射了约2000枚弹道导弹。在这2000枚中,仅有1枚突破防线并造成美军人员伤亡(约旦)。翻译过来即是:99.99%的伊朗导弹和无人机已被击落,或者至少没有造成美国人员伤亡。中央司令部的防御措施历来非常有效。世界上没有任何国家能做到如此出色。而《60分钟》的“报道”却对这一切只字未提。
🤡22🤣11❤4😁2
Showing the 12 most recent of 1,771 posts we hold for @pelosi3. 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.
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.
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.
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.
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.
Telegram’s own answer, not this register’s. When this register asks Telegram’s API what is similar to this channel, this is the list it returns, in the exact order Telegram returns it — never re-sorted by subscribers or by anything else this register measures. The relationship, and the order, are Telegram’s; we record them and date them, and make no claim of our own about which of these channels actually resemble this one.
Read from Telegram’s recommendation API, most recently 20 August 2026. Telegram holds a list like this for a small and growing share of the register — how this is measured, and why most channel pages show nothing here.
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.
This channel appears in 20 seed channels' Telegram-generated recommendation lists in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.
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.
“敏感经济信息分享” (@pelosi3), 72,603 subscribers as measured 14 November 2026. Telegram Register, tgregister.com/channel/pelosi3.
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.