杜洛夫修复了这个漏洞,大家快快更新!
Signed 皮娅妹

Channel
@fuporiji
On this record: Topic · Previous handles · Observations · Channels linked by matching posts · Growth · Engagement · What this channel posts · Reactions · Stars · Posts · Posts edited after publishing · Citations · Handles named that no longer answer · Telegram's recommendations · Cite this entry
21,788subscribers
-15,642 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 10,000–31,623.
| Telegram ID | -1001877308372 |
|---|---|
| Type | Channel |
| Username | @fuporiji |
| Description | 关注富婆日记 飞机跑的最快的女记者 投稿皮娅妹 @piyameibot 免费NFT担保 皮娅 @piya |
| Created | Between 1 October 2022 and 30 September 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 12 November 2026 |
| Measurements held | 96 |
| Confirmed unchanged | 1 time, most recently 12 November 2026 |
| On Telegram | t.me/fuporiji |
Crypto & trading — 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 10 September 2026 and assigned it the closest of 31 fixed categories, at 86% 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.
@fuporiji was previously reachable at this handle, before switching to its current one. This says nothing about who or what answers at the old handle today — only that this channel no longer does.
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 2 other registered channels. This entry also sits inside a group of 3 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.
| Posted first | Then | Overlap | Gap |
|---|---|---|---|
| @fuporiji/2011 · this entry2 Nov 2026, 06:39 UTC | @chiguabu/65902 Nov 2026, 06:49 UTC | 1.00 | 10 minutes |
| @fuporiji/2018 · this entry2 Nov 2026, 13:29 UTC | @chiguabu/65972 Nov 2026, 14:33 UTC | 1.00 | 65 minutes |
| @fuporiji/2026 · this entry3 Nov 2026, 05:41 UTC | @chiguabu/65993 Nov 2026, 10:31 UTC | 1.00 | 4.8 hours |
| @fuporiji/2029 · this entry3 Nov 2026, 15:20 UTC | @chiguabu/66043 Nov 2026, 23:33 UTC | 1.00 | 8.2 hours |
| @fuporiji/2039 · this entry6 Nov 2026, 16:15 UTC | @chiguabu/66127 Nov 2026, 01:39 UTC | 1.00 | 9.4 hours |
| @fuporiji/2042 · this entry7 Nov 2026, 05:03 UTC | @chiguabu/66257 Nov 2026, 05:06 UTC | 1.00 | 3 minutes |
| Channel | Matching posts | Text overlap | Typical gap | Published first |
|---|---|---|---|---|
| @chiguabu | 9 (7/8 hand-verifiable sample passed) | 1.00 | 66 minutes | this entry (9–0) |
| @quanyi | 6 (5/6 hand-verifiable sample passed) | 1.00 | 2.2 hours | this entry (6–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. None of the 0 matches recorded here fall after that date, so for this entry we cannot say whether any of them carried a credit. The duplication is measured; the absence of attribution is not.
“Published first” means first in this corpus. We hold 62 comparable posts for this entry, running 29 July 2026 to 12 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.
Of the group of 3 channels, the one whose matching posts we hold earliest is @quanyi. That is a statement about our reading window, not a claim of authorship.
Recorded under the key clone_source, last confirmed 13 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.
This channel is in a group of 3 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.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 12 Nov 2026, 03:47 | 21,788 | +2,019 |
| 10 Nov 2026, 02:56 | 19,769 | -362 |
| 8 Nov 2026, 14:51 | 20,131 | -309 |
| 7 Nov 2026, 07:30 | 20,440 | -225 |
| 6 Nov 2026, 04:06 | 20,665 | -240 |
| 5 Nov 2026, 05:36 | 20,905 | -6 |
| 4 Nov 2026, 08:17 | 20,911 | -183 |
| 3 Nov 2026, 07:37 | 21,094 | +134 |
| 2 Nov 2026, 07:35 | 20,960 | -332 |
| 1 Nov 2026, 05:20 | 21,292 | -163 |
| 31 Oct 2026, 06:36 | 21,455 | +533 |
| 30 Oct 2026, 09:28 | 20,922 | +795 |
| 29 Oct 2026, 10:51 | 20,127 | -499 |
| 28 Oct 2026, 07:20 | 20,626 | -353 |
| 27 Oct 2026, 03:50 | 20,979 | -344 |
| 26 Oct 2026, 02:49 | 21,323 | -359 |
| 24 Oct 2026, 23:37 | 21,682 | -404 |
| 24 Oct 2026, 00:20 | 22,086 | -408 |
| 22 Oct 2026, 22:45 | 22,494 | -400 |
| 21 Oct 2026, 23:46 | 22,894 | first reading |
177 posts held, back to 29 July 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 143 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. It is computed over the 15 of 62 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 13 November 2026 |
|---|---|
| Posts held | 177 (29 July 2026 – 13 November 2026) |
| Views total | 148,190 |
| Reactions total | 36 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 13 Nov 2026, 16:05 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 13 November 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.
Measured directly from 12 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.
207 reactions across 41 posts, in 4 distinct kinds. The most used accounts for 45.9% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 6228546656237787272 | 95 | 45.9% | |
| custom 6201935653052092324 | 60 | 29.0% | |
| custom 6228893354587856148 | 39 | 18.8% | |
| custom 6059992687635864246 | 13 | 6.28% |
Custom emoji. Every row above is a Telegram custom emoji, which the public preview renders as an element carrying only a numeric id — no character, and no image we can reach. The id is printed as-is rather than substituted with a look-alike glyph, because a stand-in would be our invention showing where a measurement should be. The counts beside them are Telegram’s.
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 56 of the 177 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 207 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 177 most recent posts we hold, published 29 July 2026 to 13 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 @fuporiji. 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 177 most recent posts we hold for this entry, published 29 July 2026 to 13 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: 24 of 62 posts held from the last 30 days (38.7%) 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).
杜洛夫修复了这个漏洞,大家快快更新!
Signed 皮娅妹
通俗一点:不要打开任何外部机器人,因为病毒必须在机器人内产生 需要警惕一点 就是文字超链
Signed 皮娅妹
🆘️️️️️️🆘️️️️️️🆘️️️️️️telegram 出现严重安全漏洞~! 请立刻退出你的电脑telegram,不要用电脑登录飞机,无论是windows 还是 mac。 原文: https://t.me/crypto_okop/25777 黑客实操视频: https://t.me/crypto_okop/25803 太危险了,我还好我没什么u。
Signed 皮娅妹
tmd 别瞧不起1U,富豪为了1U都会交易无数次,更何况我现在涨到2U了! 珍惜这你唯一能和iPhone Duo产生关联的机会吧。
custom 62019356530520923241
Signed 皮娅妹
有奖征集 姐姐我换了duo,各位粉丝们帮我做一个duo的专用壁纸吧。做好了大家投票,第一名 奖励2U,参与活动还有机会获得本频道免费曝光哦! 壁纸要提现我的与众不同,高贵气质,很有品味,可可爱爱!
Signed 皮娅妹
这是一段 TG desktop 的攻击Demo展示,利用了一个TG 0DAY漏洞。 通过这个漏洞,你只需要点击攻击者的机器人 /start,无需任何交互,无需任何点击,看到消息的一瞬间即可RCE。 我问了ai,ai建议不要随便乱点机器人了。特别是群发让你点机器人。
Signed 皮娅妹
以为换个Gay就没出轨的事了? 太天真了,库克每次访华都绕着圈要去成都,大家觉得库克是那种爱吃火锅的人吗?到时候在成都搞个大新闻,英伟达股票就直了!
Signed 皮娅妹
怎么有一种黄仁勋包养小三是我出钱的感觉?
Signed 皮娅妹
你们知道这个截图意味着什么吗? 以后跟我说话,注意一下用词。
custom 62019356530520923245
Signed 皮娅妹
📱苹果用户一定注意! 苹果手机又出漏洞了,装错一个App,钱包里的U可能被无感偷走 11月8日,有个开发者在 GitHub 上公开了一个苹果漏洞,名字叫 worse_query。 用大白话说:苹果本来给每个 App(沙盒)都关在自己的小房间里,互相看不到。这个漏洞能让一个 App 从小房间里溜出来,去翻别的 App 的东西,还能改。 那问题就大了。你手机里要是装了个带毒的 App,它就能借这个漏洞去翻你钱包 App 里的数据,你这边一点感觉都没有,U 可能就没了。 受影响的版本很多,iOS 26.0 到 26.7.2,还有 27.2,连 27.3 测试版都有。作者说已经报给苹果了,但到现在还没修好,代码却已经公开,网上已经有人拿它做成工具了。 用苹果的兄弟,这段时间注意: 1. 来路不明的 App 一个都别装,特别是别人私发的安装包、要你点"信任"的企业签名 App,骗子最爱用这招。 2. 苹果一推送更新,马上升级。…
Signed 皮娅妹
@nbesim,介绍一下是不是你的业务
Signed 皮娅妹
🎉 必安担保&币安担保 双11周年庆活动 年关将至,做生意除了看收益,更要看风险。当下国际形势日趋严峻,多个国家已经跟中方拧成一股绳,实现数据互通,协查协抓,东南亚已经再没有绝对安全之地。在这样的大环境情况下,只会加剧那些毫无背景、毫无根基的野鸡担保公司跑路,倒闭,被抓等!许多担保,没有雄厚的背景支撑,也缺乏资金投入,更有甚者身处高风险国家地域,随时都有被政策/战争/严打清扫的可能,自身难保,更遑论能真正为他人提供可靠的担保服务。 君子不立危墙之下。选择担保,务必理性判断、谨慎合作。优惠值得看,履约更要看。 必安担保欢迎各位老板用实际业务和处理结果检验服务。 感谢一路支持,双11周年庆,六重福利送给大家! 📅活动日期:11月11日 - 11月18日 😀活动一|必安供需,双11特惠 认证公群老板投放供需广告: • 公群专属 5折,周年庆再享 5折 • 两重优惠叠加,最终仅需原价25% • 非公群老板用户可享 5折,不再…
Signed 皮娅妹
Showing the 12 most recent of 177 posts we hold for @fuporiji. 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.
Stars beside a post are paid reactions — Telegram Stars, bought with money and spent on that post. They are a different unit from reactions and are never added to them, here or anywhere else on this page.
@fuporiji edited 2 posts 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.
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 14 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.
@fuporiji named 8 handles that resolve to nothing today. That is a fact about the reference, not necessarily a fact about the handle’s history — see the two groups below.
Most of these may never have existed as a live channel at all. A handle a channel names can be a typo, an aspirational name nobody registered, or a channel that was already gone before this one ever mentioned it. Unless a row below is marked evidenced, all we know is that it references a handle that is not a live channel today — not that anything “died”. How this is measured.
We ourselves saw each of these resolve to a real page at some point before it went vacant — a genuine, evidenced change, not an inference from absence.
References a handle that is not a live channel — we have no record it ever was one.
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 11 September 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 3 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 12 November 2026 — this entry's latest reading, not the date you are reading this.
“富婆日记” (@fuporiji), 21,788 subscribers as measured 12 November 2026. Telegram Register, tgregister.com/channel/fuporiji.
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.