Some events non-obviously cause notification count changes

[turt2live]

To name a couple:

• Edits: Editing a comment increases notification count even if comment is unread. element-web#20377
• Poll votes: Poll votes increment the message counter in room list element-web#21115
• Call end events: "call ended" events cause an unread notification in the systray although all messages in the room have been read element-web#7941
• Voice Broadcast chunks (actually MSC3245 voice messages)
• Any other new event type we send and don't introduce a push rule for

For reactions and such we fixed this with MSC2153 (a push rule).

This issue exists to track the client-side concern, though the fix is concretely with the spec.

Related: #1088 (possible short-term solution?)

[SimonBrandner]

This is sometimes caused by the fact the server can't see the event type due to the event being encrypted (e.g. call hangups)

[turt2live]

That just means we're processing push rules either too correctly, or incorrectly. Our behaviour should be exactly the same as in unencrypted rooms.

[SimonBrandner]

That just means we're processing push rules either too correctly, or incorrectly. Our behaviour should be exactly the same as in unencrypted rooms.

We show notif counts based on what the server sends down during sync both in E2EE and non-E2EE rooms which is not ideal :/

[turt2live]

That might be an entirely different case then, annoyingly.

one day we'll fix notifications.

[HarHarLinks]

• other call events like switching (my own!) screen sharing state also gives a notification

[SimonBrandner]

• my own!

The other side is responding to your SDP offer with an answer - the two ends need to agree on the media being sent

[HarHarLinks]

Thank you for the technical explanation. I'm sure you understand that from an end user perspective it feels like I am the one sending something when I change one of my settings.
Regardless, this should not happen.

[SimonBrandner]

Thank you for the technical explanation. I'm sure you understand that from an end user perspective it feels like I am the one sending something when I change one of my settings. Regardless, this should not happen.

Yes, of course, this is a super annoying (was just trying to add some context as to how this happens)

[whitequark]

This has been an issue since 2018 and it's absolutely intolerable in 1:1 voice calls when the other party frequently mutes and unmutes. Are there any concrete plans to fix this?