⚽️8月5日足球赛事精选⚽️ 【欧冠资 00:00】米亚尔比 vs 布拉迪斯拉发🔥🔥 米亚尔比主场阵形严密中前场衔接流畅! 👉盘口推荐:米亚尔比[email protected] 【欧冠资 01:30】索菲亚列夫斯基 vs 海拉提🔥🔥 海拉提后防收缩果断防守反击犀利韧性十足! 👉盘口推荐:海拉提+0.5/[email protected] 【欧冠资 02:00】圣吉罗斯 vs 博多格林特🔥🔥 博多格林特客场高位压制掌控比赛节奏! 👉盘口推荐:博多格林特+0/[email protected] 【欧联资 03:00】拉恩 vs 伊比利亚1999🔥🔥 拉恩坐镇主场战意高涨中后场防守稳扎稳打! 👉盘口推荐:拉恩+0/[email protected] 【哥伦甲 09:20】百万富翁 vs 帕斯托体育🔥🔥 百万富翁主场气势如虹火力全开攻势犀利! 👉盘口推荐:百万富翁[email protected] 【俄罗斯杯 23:30】莫斯科斯巴达 vs 奥伦堡🔥🔥 莫斯科斯巴达主场统治力强锋线多点开花! 👉盘口推荐:莫斯科斯巴…
Content that also appears on other registered channels
Posts published here appear word for word on 1 other registered channel. 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 |
|---|---|---|---|
| @sjb0101/85718 Jul 2026, 06:04 UTC | @OB200000/4323 · this entry18 Jul 2026, 06:04 UTC | 0.97 | under a minute |
| @OB200000/4321 · this entry17 Jul 2026, 06:05 UTC | @sjb0101/85517 Jul 2026, 06:05 UTC | 0.96 | under a minute |
| @sjb0101/85311 Jul 2026, 06:03 UTC | @OB200000/4319 · this entry11 Jul 2026, 06:03 UTC | 0.96 | under a minute |
| @sjb0101/86529 Jul 2026, 07:26 UTC | @OB200000/4331 · this entry29 Jul 2026, 07:26 UTC | 0.96 | under a minute |
| @sjb0101/86122 Jul 2026, 08:54 UTC | @OB200000/4327 · this entry22 Jul 2026, 08:54 UTC | 0.86 | under a minute |
| Channel | Matching posts | Text overlap | Typical gap | Published first |
|---|---|---|---|---|
| @sjb0101 | 5 (5/5 hand-verifiable sample passed) | 0.94 | under a minute | @sjb0101 (4–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. None of the 4 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 10 comparable posts for this entry, running 11 July 2026 to 4 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 2, the earliest publisher we hold is @sjb0101. That is a statement about our reading window, not a claim of authorship.
