New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

MSC1796: improved e2e notifications #1796

wants to merge 5 commits into
base: master


None yet
2 participants
Copy link

ara4n commented Jan 11, 2019

ara4n added some commits Jan 11, 2019

@@ -0,0 +1,125 @@
# Proposal for improving notifications for E2E encrypted rooms

This comment has been minimized.


turt2live Jan 16, 2019


leaving this here so I don't forget later:

My overall concern with this proposal is that it proposes that notifications still be handled server-side. Given the direction of e2e and extensible events, I continue to be convinced that server-side unread/notification counts are not the right approach. Instead, clients should be responsible for tracking this information as they are the best part of the stack to determine what the numbers should be.

Doing client-side notifications/unread counts does mean that clients are more complicated and duplicating efforts, however the server cannot possibly be expected to be as reliable anymore. I think it's better worth our time making it easier for clients to calculate counts and set expectations for how they work rather than continue to try and keep this server-side.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment