柬埔寨菩萨省执法遇袭 嫌疑人引爆炸弹致五死两伤 2026年8月5日晚间,柬埔寨菩萨省瓦尔文县奥索姆乡突发炸弹爆炸惨案,事故最终造成五人遇难、两人受伤,现场情况惨烈。 事发前,当地警方接获举报,辖区内存在家庭暴力及吸毒违法问题,同时收到相关受害者投诉,随即针对性开展专项打击整治行动。执法过程中,涉案袭击者当场引爆炸弹,实施极端行为。 本次爆炸事故伤亡惨重,除引爆炸弹的嫌疑人本人殒命外,还造成当地警察局长、三名保安不幸身亡,另有一名警员与一名保安被炸受伤。 案件发生后,当地职能部门第一时间进驻事发地点,全面封锁现场,有序开展勘验取证、案情梳理等后续调查工作,厘清事故完整起因与经过。
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 |
|---|---|---|---|
| @jianpuzhai177/60935 Aug 2026, 07:56 UTC | @JPZ_99/6232 · this entry5 Aug 2026, 07:57 UTC | 1.00 | under a minute |
| @jianpuzhai177/60995 Aug 2026, 07:56 UTC | @JPZ_99/6238 · this entry5 Aug 2026, 07:57 UTC | 1.00 | under a minute |
| @jianpuzhai177/61066 Aug 2026, 10:06 UTC | @JPZ_99/6245 · this entry6 Aug 2026, 10:06 UTC | 1.00 | under a minute |
| @jianpuzhai177/61076 Aug 2026, 10:06 UTC | @JPZ_99/6246 · this entry6 Aug 2026, 10:06 UTC | 1.00 | under a minute |
| @jianpuzhai177/61086 Aug 2026, 10:06 UTC | @JPZ_99/6247 · this entry6 Aug 2026, 10:06 UTC | 1.00 | under a minute |
| @jianpuzhai177/61116 Aug 2026, 10:06 UTC | @JPZ_99/6250 · this entry6 Aug 2026, 10:06 UTC | 1.00 | under a minute |
| Channel | Matching posts | Text overlap | Typical gap | Published first |
|---|---|---|---|---|
| @jianpuzhai177 | 18 (6/8 hand-verifiable sample passed) | 1.00 | under a minute | @jianpuzhai177 (18–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. 10 of the 18 matches recorded here fall after that date and carried no header when we read them. The rest predate reliable capture and are not evidence either way.
“Published first” means first in this corpus. We hold 20 comparable posts for this entry, running 5 August 2026 to 6 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 @jianpuzhai177. That is a statement about our reading window, not a claim of authorship.