iOS 版本已经通过苹果审核! 不必再继续TF 我们会手动分发, 内部在做最后的API稳定测试和参数调整后, 会立刻通知大家下载链接 (免费app但带内购, 但建议后续大家仅在官网购买套餐因为商店吃佣金%) 目前通过的审核是 1.0 版本内核, 内部已经有稳定 内核2.0 版本的测试版本app, 过一些时日尝试提交2.0版本给苹果审核新版本 请准备苹果外区ID, 将会上架到这些地区的 iOS AppStore: 澳洲, 加拿大, 法国, 德国, 香港, 日本, 韩国, 澳门, 新加坡, 英国, 美国 我们这几天会告知大家下载方式, 谢谢大家的等待
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 |
|---|---|---|---|
| @muguacloud/13228 Apr 2025, 00:52 UTC | @biteb2/150 · this entry28 Apr 2025, 00:52 UTC | 1.00 | under a minute |
| @muguacloud/1336 May 2025, 04:19 UTC | @biteb2/151 · this entry6 May 2025, 04:19 UTC | 1.00 | under a minute |
| @muguacloud/13414 Jun 2025, 04:25 UTC | @biteb2/152 · this entry14 Jun 2025, 04:25 UTC | 1.00 | under a minute |
| @muguacloud/13815 Aug 2025, 05:25 UTC | @biteb2/156 · this entry15 Aug 2025, 05:25 UTC | 1.00 | under a minute |
| @biteb2/157 · this entry20 Aug 2025, 17:00 UTC | @muguacloud/13920 Aug 2025, 17:00 UTC | 1.00 | under a minute |
| @biteb2/158 · this entry30 Aug 2025, 02:08 UTC | @muguacloud/14030 Aug 2025, 02:08 UTC | 1.00 | under a minute |
| Channel | Matching posts | Text overlap | Typical gap | Published first |
|---|---|---|---|---|
| @muguacloud | 16 (8/8 hand-verifiable sample passed) | 1.00 | under a minute | @muguacloud (11–5) |
| @jinkelanotify | 9 (8/8 hand-verifiable sample passed) | 1.00 | under a minute | @jinkelanotify (9–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 20 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 17 comparable posts for this entry, running 26 January 2025 to 16 June 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 @muguacloud. That is a statement about our reading window, not a claim of authorship.
