Description

This release is the eighth and final leg of the media hash-scanning rollout (versions 2.0.2030–2.0.2037; the full canister train is already released). It ships the frontend for the features in that train: moderation report cards now display media hash-match provenance (provider, record and match distance) when a detection came from a hash match rather than a user report, blocked re-post attempts appear as clearly-labelled attempt cards which mirror the original report's verdict rather than offering their own resolve actions, and platform operators gain the configuration surface (under the existing dual-authorization propose/confirm flow) for registering media scanner principals and enabling media scanning.

Releasing this website does not switch anything on: media scanning remains disabled until the separate dual-authorized platform-operator action is taken, now that the train is complete.

It also cleans up client-side error reporting so that genuine faults stand out: expected worker failures (session teardown, transient gateway and network errors) and known browser-extension noise are no longer reported to the error tracker, while replica rejections and canister traps remain reportable, and reports now group by the real underlying cause.

Added

• Show media hash-match provenance (provider, record id, match distance) on moderation report cards and alerts (#9161)
• Platform-operator configuration for media scanning (scanner principals, enablement) under the dual-authorized propose/confirm flow (#9161)
• Label moderation report cards for blocked re-post attempts, which follow the original report's verdict instead of carrying their own resolve actions (#9162)

Changed

• Stop reporting expected client-side failures (session teardown, transient gateway and network errors, known browser-extension noise, transient version-check failures) to the error tracker, and group the remainder by underlying cause; replica rejections and canister traps remain reportable (#9160)

Fixed

• Fix a spurious error when a WebRTC peer reconnected on its own before the reconnect handler ran (#9160)

Proposal to execute nervous system function:

Nervous system function:

NervousSystemFunction { id: 10000, name: "Update OpenChat frontend assets", description: Some( "This will commit a newly prepared batch of assets which have been uploaded to the asset canister by a principal which has been granted the "Prepare" permission.", ), function_type: Some( GenericNervousSystemFunction( GenericNervousSystemFunction { target_canister_id: Some( 6hsbt-vqaaa-aaaaf-aaafq-cai, ), target_method_name: Some( "commit_proposed_batch", ), validator_canister_id: Some( 6hsbt-vqaaa-aaaaf-aaafq-cai, ), validator_method_name: Some( "validate_commit_proposed_batch", ), topic: Some( DappCanisterManagement, ), }, ), ), }

Payload sha256:

4be9207af01190493761bf70a06a7cd4da529508b6d0da73b9c69978332df76b

Payload:

commit proposed batch 253 with evidence 75adc49792e4c91d009a4e47b1043242977fa33baac4248b23ad8766b2b7cb68