名师天团锐评:https://t.me/shmstttg 【所在位置】:浦东迪士尼 【老师艺名】:布小蛮 【联系方式】:@dc968 【验证留名】:niko 【验证时间】:8/19 【课程打赏】:7。 【颜值身材】:9 【推荐程度】:8(10分为满分) 【体验细节】:老师的工作室靠近迪士尼,不过地铁下来比较近,步行可以到。课时排得紧,卡点进的教室,教室环境不错,老师人照9分以上,基本所见即所得。贵州妹子,08,160,80,C,皮肤白嫩滑,下面粉,毛少,硬件非常顶,尤其是奶子,又大又圆的乳腺胸,奶头小,只有年轻的妹子才会那么大也不垂的。嫩妹三点后开工,下面水多,紧度一般,反馈也不多,软件上比较普通。可以打卡硬件吧 温馨提示:报告仅供参考 注:(提交报告要提供相关证明,如聊天记录,付款记录等)
Content that also appears on other registered channels
Posts published here appear word for word on 1 other registered channel. They sit inside a group of 3 channels that share the same post bodies 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 |
|---|---|---|---|
| @hmflzx/49725 Jul 2026, 05:17 UTC | @shmstttg/350 · this entry25 Jul 2026, 05:18 UTC | 1.00 | 72 seconds |
| @hmflzx/49825 Jul 2026, 07:54 UTC | @shmstttg/351 · this entry25 Jul 2026, 07:54 UTC | 1.00 | under a minute |
| @hmflzx/50025 Jul 2026, 14:34 UTC | @shmstttg/352 · this entry25 Jul 2026, 14:34 UTC | 1.00 | under a minute |
| @hmflzx/50427 Jul 2026, 08:20 UTC | @shmstttg/355 · this entry27 Jul 2026, 08:21 UTC | 1.00 | 72 seconds |
| @hmflzx/50528 Jul 2026, 13:54 UTC | @shmstttg/359 · this entry28 Jul 2026, 13:54 UTC | 1.00 | under a minute |
| @hmflzx/5126 Aug 2026, 08:09 UTC | @shmstttg/362 · this entry6 Aug 2026, 08:09 UTC | 1.00 | under a minute |
| Channel | Matching posts | Text overlap | Typical gap | Published first |
|---|---|---|---|---|
| @hmflzx | 6 (6/6 hand-verifiable sample passed) | 1.00 | under a minute | @hmflzx (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. 1 of the 6 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 20 comparable posts for this entry, running 17 July 2026 to 6 August 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).
Across the whole group of 3, the earliest publisher we hold is @hmflzx. That is a statement about our reading window, not a claim of authorship.
