#马来西亚新闻 砂州鳄鱼越来越多!三年22人遇害,当地人直呼不敢靠近河边 马来西亚砂拉越州近年来鳄鱼数量明显回升,官方最新数据显示,2024年当地鳄鱼数量已经突破2.5万只,比几十年前大幅增加。 随着数量增长,人鳄冲突也越来越频繁。统计显示,2023年至2025年期间,当地已有22人因鳄鱼袭击丧命,今年截至目前又新增5起死亡案例,引发社会广泛关注。 据了解,砂拉越州的鳄鱼在上世纪80年代一度因大量捕杀接近绝迹,经过多年保护后数量快速恢复。如今,当局开始面对新的难题——如何在保护野生动物与保障居民安全之间取得平衡。 为了降低风险,砂州政府已经开放发放鳄鱼狩猎许可证,同时推出手机举报平台,方便民众第一时间上报鳄鱼出没地点。相关部门也会联合持证猎人,将靠近村庄或居民区的鳄鱼转移到其他区域。 虽然官方表示,与20年前相比,鳄鱼攻击事件整体并未明显增加,但由于鳄鱼越来越常出现在河边、村庄附近,不少居民已经感到不安。林业部门分析…
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 |
|---|---|---|---|
| @yinni977/4562 · this entry6 Aug 2026, 09:43 UTC | @ML_188/47436 Aug 2026, 10:01 UTC | 1.00 | 17 minutes |
| @yinni977/4574 · this entry6 Aug 2026, 10:00 UTC | @ML_188/47556 Aug 2026, 10:01 UTC | 1.00 | under a minute |
| @yinni977/4575 · this entry6 Aug 2026, 10:00 UTC | @ML_188/47566 Aug 2026, 10:01 UTC | 1.00 | under a minute |
| @yinni977/4576 · this entry6 Aug 2026, 10:00 UTC | @ML_188/47576 Aug 2026, 10:01 UTC | 1.00 | under a minute |
| @yinni977/4580 · this entry6 Aug 2026, 10:00 UTC | @ML_188/47616 Aug 2026, 10:01 UTC | 1.00 | under a minute |
| @yinni977/4581 · this entry6 Aug 2026, 10:00 UTC | @ML_188/47626 Aug 2026, 10:01 UTC | 1.00 | under a minute |
| Channel | Matching posts | Text overlap | Typical gap | Published first |
|---|---|---|---|---|
| @ML_188 | 20 (6/8 hand-verifiable sample passed) | 1.00 | under a minute | this entry (20–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 0 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 20 comparable posts for this entry, running 6 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 @yinni977 — which is this entry. That is a statement about our reading window, not a claim of authorship.