Hidden/private read-receipts must be remembered by server which mustn't send them even from legacy clients unless configured otherwise

Nobody has claimed this yet.

**Suggestion**

Currently private read receipts or hidden read markers are client-specific and need to be configured on every client separately and if some client doesn't support them, that one publicises the read-receipts.

In my opinion the Matrix homserver must take more active role on them and if the user enables hidden read-receipts on configured clients, the server must remember that and hide read-receipts from all of the users devices until the user explicitly decides to publish their read-receipts again. I think this would also be more in line with user expectations and every other protocol implementing option to disable read-receipts.

Further reading:

* [Read receipts, presence and typing notifications should be disabled by default | neilalexander.dev](https://neilalexander.dev/2021/04/09/read-receipts-typing-notifs)

No files, tests, or entry points are identified in the issue. Start by locating the Matrix specification sections governing read receipts and server/device behavior; done means the remembered hidden-read-receipt behavior and explicit republishing rules are specified consistently, including legacy clients.

Written by the indexing model from the issue text.