Dear Maintainer,

Telegram (be for the sake of some users convenience, or for copying the industry practice of other competing social networks, that enables more engaging addiction) includes some antifeatures, that are purposedly not controllable by its users, contrarily to most of its other features.

Read receipts are somewhat infamous to magnify interpersonal conflicts, increase engageability, increase addiction, and harm privacy.

Telegram even, in last release, stopped them from being sendable after a week, for the sake of privacy… this is ridiculous, and a sheer compromise for privacy.

I tried to find where were they implemented, but my inexperience, in addition to the very diverse number of (used) functionalities of C++, and above all the enormous size of Telegram’s codebase, prevents me for understanding anything to it, or knowing where to get started by.

The ideal would be to develop a patch adding to privacy settings the option to stop sending read receipts to specific contacts or group of contacts.

The easiest proof of concept would be simply a patch breaking the sending of read receipts in all Telegram (that would be acceptable to me, and maybe to some other, in protestation for the purposedly hardening of disabling them).  Possibly applied in all Debian, that should follow discussion.

A middle solution would be a setting disabling all read receipts (and a step toward ideal solution).

Thank you,

Hoping to be relevant.