Skip to content
This repository was archived by the owner on Apr 26, 2024. It is now read-only.
This repository was archived by the owner on Apr 26, 2024. It is now read-only.

Add config option to disable sending read receipts to other users. #9253

@bavarialogy

Description

@bavarialogy

Hello,

I'm implementing Synapse for a public sector entity where the worker's council is likely to enforce enhanced privacy for message read receipts. As far as I understood Synapse's event handling, this isn't easy to accomplish in the current state of implementation.

I'm currently looking at pseudonymizing read receipt events for a public room as a workaround (others, like private rooms, might be harder to implement and will likely not be requested here in the first place). Is it possible to overwrite events in the database, i.e. so that every m.read or m.fully_read is then related to some dummy user (e.g. a service account)? People would see 'someone' read the message but can't tell who it was anymore.

Metadata

Metadata

Assignees

No one assigned

    Labels

    T-EnhancementNew features, changes in functionality, improvements in performance, or user-facing enhancements.

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions