[Story] Setting: Disable sending typing notifications and read receipts

[VolkerJunginger]

Story

As a user of the EX client I do not want to expose to other user that I am active in the app and therefor be able to not send read receipts or typing notifications.

Add a setting to disable user-presence:

• The setting disables sending of typing notifications
• The setting disables sending of read-receipts and make the client send private-read-receipts

If the user enabled the setting do the following in the timeline:

• Don't show typing. notifications of other users
• Don't show read receipts of other users.

Dependencies

• TBD

Sign-offs

Android

• [ ] Design sign-off on completion
• [ ] QA sign-off on completion
• [ ] Product sign-off on completion

iOS

• [ ] Design sign-off on completion
• [ ] QA sign-off on completion
• [ ] Product sign-off on completion

Web

• [ ] Design sign-off on completion
• [ ] QA sign-off on completion
• [ ] Product sign-off on completion

Scope

### Android
- [ ] https://github.com/element-hq/element-x-android/issues/2241

### iOS
- [ ] https://github.com/element-hq/element-x-ios/issues/2348

Out of scope

• TBD

[manuroe]

@VolkerJunginger: the app does not support typing notification at all. It is weird to add a settings about them.

[jmartinesp]

@manuroe @VolkerJunginger : there is some code for sending typing notification in the Rust SDK, it's not exposed to the apps though. Should we create the bindings, send the typing notifications and add this option to disable them?

[VolkerJunginger]

yes, please.

[jmartinesp]

We'll also need some designs for displaying the typing notifications on the timeline. I guess we'll use more or less the same designs and animations that we had in the legacy apps, but it would still be good to confirm this.

[bmarty]

FTR this is the current design for this setting in Element Android, in Settings/Preferences section Message editor:

[amshakal]

Here is a suggestion for what copy can be

[bmarty]

@amshakal the wording looks good, but I would replace all the or by and. Note that I am not a native English speaker, so you may just ignore me :)

Also, just to confirm, the toggle will be enabled by default.

[bmarty]

Regarding the implementation, we will keep separate booleans internally, like:

• renderTypingNotifications
• sendTypingNotifications
• renderReadReceipts
• sendPublicReadReceipts (this one already exists on EXA) rather that just a global isPresenceEnabled or anything similar, just to be able to be flexible. There will still be one setting Share presence visible to the user that will set all the booleans at once.

To complete this, these settings will be lost when the user logs out, so they are stored in a store scoped to the session. This store is named SessionPreferencesStore on Android.