🚀亿万集团业务通知 亿万集团🏆业界Top1霸榜多年 为了继续保持亿万集团的发展势头、我方已购入众多个4字🆔并且客服全部配备+888匿名号码❗️【亿万集团-业务集团最多4字以及+888号码保持者】 ------------------------- ⭐购买那么多4字、以及+888号码是为了什么-让你们更放心在我们亿万集团这里做单、给你们提供一个温馨的做单环境、我方不愿看到你们成为别人“待宰羔羊”愿你们一直跟随我们亿万集团、不要别再“任人宰割”跟随我们亿万集团共同发展、一路前行! ------------------------- ⭐我方作为一个成熟的集团向你们保证客服绝对不会出现态度不好/不回信息/不解决售后/这些问题。客服都是线下人员若还有违反请联系 @zmpc 投诉、我方会严厉处罚❗️ ------------------------- ⭐亿万集团从无人知晓到广为人知、成为世人口中的老牌集团。我方从不单一依赖担保、在✈️多年…
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 |
|---|---|---|---|
| @huiligx/154966 Feb 2026, 02:04 UTC | @belan/1948 · this entry6 Feb 2026, 10:02 UTC | 1.00 | 8.0 hours |
| @huiligx/154996 Feb 2026, 03:35 UTC | @belan/1942 · this entry6 Feb 2026, 04:02 UTC | 1.00 | 27 minutes |
| @huiligx/155026 Feb 2026, 05:17 UTC | @belan/1944 · this entry6 Feb 2026, 05:17 UTC | 1.00 | under a minute |
| @huiligx/155036 Feb 2026, 06:29 UTC | @belan/1945 · this entry6 Feb 2026, 06:29 UTC | 1.00 | under a minute |
| @huiligx/155076 Feb 2026, 10:11 UTC | @belan/1949 · this entry6 Feb 2026, 10:11 UTC | 1.00 | under a minute |
| @huiligx/155086 Feb 2026, 10:25 UTC | @belan/1950 · this entry6 Feb 2026, 10:25 UTC | 1.00 | under a minute |
| Channel | Matching posts | Text overlap | Typical gap | Published first |
|---|---|---|---|---|
| @huiligx | 10 (8/8 hand-verifiable sample passed) | 1.00 | under a minute | @huiligx (7–3) |
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 7 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 18 comparable posts for this entry, running 6 February 2026 to 10 March 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 @huiligx. That is a statement about our reading window, not a claim of authorship.
