#菲律宾新闻马卡蒂市发生枪击案一人死亡一人受伤 一名女子在马卡蒂市一起枪击事件中死亡,另一人受伤。 事件发生于当晚约6:45,地点位于马卡蒂市马卡蒂大道City Garden区域附近。 根据初步调查,两名女性受害者遭到身份不明的嫌疑人开枪袭击。 警方及相关部门接报后迅速赶到现场,并将两名伤者送往医院抢救,但其中一名女子到院时已被宣布死亡(DOA,Dead on Arrival)。 目前,执法部门仍在继续调查此案,以确认嫌疑人的身份以及作案动机。
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 |
|---|---|---|---|
| @feilvbin177/42835 Aug 2026, 03:20 UTC | @FLB_88/4495 · this entry5 Aug 2026, 07:59 UTC | 1.00 | 4.7 hours |
| @feilvbin177/42865 Aug 2026, 07:23 UTC | @FLB_88/4496 · this entry5 Aug 2026, 07:59 UTC | 1.00 | 36 minutes |
| @feilvbin177/42945 Aug 2026, 07:58 UTC | @FLB_88/4504 · this entry5 Aug 2026, 07:59 UTC | 1.00 | under a minute |
| @FLB_88/4508 · this entry6 Aug 2026, 10:14 UTC | @feilvbin177/43006 Aug 2026, 10:20 UTC | 1.00 | 7 minutes |
| @FLB_88/4509 · this entry6 Aug 2026, 10:14 UTC | @feilvbin177/43016 Aug 2026, 10:20 UTC | 1.00 | 7 minutes |
| @FLB_88/4511 · this entry6 Aug 2026, 10:14 UTC | @feilvbin177/43036 Aug 2026, 10:20 UTC | 1.00 | 7 minutes |
| Channel | Matching posts | Text overlap | Typical gap | Published first |
|---|---|---|---|---|
| @feilvbin177 | 18 (7/8 hand-verifiable sample passed) | 1.00 | 7 minutes | @feilvbin177 (13–5) |
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. 2 of the 13 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 4 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 @feilvbin177. That is a statement about our reading window, not a claim of authorship.