30 Nov 2025, 15:06 UTC≈12,500 viewsread 3 September 2026
Photo
Канал временно не обслуживается, за рекламой обращаться к действующему сотруднику на других каналах @Oksana_rek
Content that also appears on other registered channels
Posts published here appear word for word on 2 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 |
|---|---|---|---|
| @Orenburg_Future/162412 Nov 2025, 12:53 UTC | @Orenburg_nauch/1541 · this entry14 Nov 2025, 14:42 UTC | 1.00 | 2 days |
| @Orenburg_Future/162614 Nov 2025, 09:06 UTC | @Orenburg_nauch/1542 · this entry15 Nov 2025, 20:37 UTC | 1.00 | 36 hours |
| @Orenburg_Future/162816 Nov 2025, 13:42 UTC | @Orenburg_nauch/1545 · this entry18 Nov 2025, 17:34 UTC | 1.00 | 2 days |
| @Orenburg_Future/163522 Nov 2025, 09:03 UTC | @Orenburg_nauch/1551 · this entry24 Nov 2025, 15:00 UTC | 1.00 | 2 days |
| @Orenburg_Future/163724 Nov 2025, 17:37 UTC | @Orenburg_nauch/1553 · this entry26 Nov 2025, 16:33 UTC | 1.00 | 47 hours |
| @Orenburg_Future/163926 Nov 2025, 09:02 UTC | @Orenburg_nauch/1554 · this entry27 Nov 2025, 17:51 UTC | 1.00 | 33 hours |
| Channel | Matching posts | Text overlap | Typical gap | Published first |
|---|---|---|---|---|
| @Orenburg_Future | 6 (6/6 hand-verifiable sample passed) | 1.00 | 2 days | @Orenburg_Future (6–0) |
| @Orenburg_inside | 5 (5/5 hand-verifiable sample passed) | 1.00 | 20 minutes | 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. None of the 6 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 19 comparable posts for this entry, running 11 November 2025 to 29 November 2025. 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 @Orenburg_Future. That is a statement about our reading window, not a claim of authorship.