21 Oct 2021, 09:25 UTC813 viewsread 7 August 2026
Learn & Trade FUN - $100,000 Rewards Up for Grabs! https://www.binance.com/en/support/announcement/39fe5be158e6464ba4a798dec6ca1963
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 377 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 |
|---|---|---|---|
| @binance_announcements/330013 Oct 2021, 12:42 UTC | @binancesmartchainscommunity/396 · this entry13 Oct 2021, 12:58 UTC | 1.00 | 16 minutes |
| @binance_announcements/330114 Oct 2021, 05:49 UTC | @binancesmartchainscommunity/404 · this entry14 Oct 2021, 05:50 UTC | 1.00 | under a minute |
| @binance_announcements/330414 Oct 2021, 08:54 UTC | @binancesmartchainscommunity/405 · this entry14 Oct 2021, 09:01 UTC | 1.00 | 7 minutes |
| @binance_announcements/331215 Oct 2021, 11:23 UTC | @binancesmartchainscommunity/406 · this entry15 Oct 2021, 11:24 UTC | 1.00 | 72 seconds |
| @binance_announcements/333221 Oct 2021, 09:25 UTC | @binancesmartchainscommunity/414 · this entry21 Oct 2021, 09:25 UTC | 1.00 | under a minute |
| Channel | Matching posts | Text overlap | Typical gap | Published first |
|---|---|---|---|---|
| @binance_announcements | 5 (5/5 hand-verifiable sample passed) | 1.00 | 72 seconds | @binance_announcements (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. None of the 5 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 14 comparable posts for this entry, running 13 October 2021 to 21 October 2021. 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 377, the earliest publisher we hold is @mash. That is a statement about our reading window, not a claim of authorship.