Skip to content
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

MSC2855: Server-Initiated Client Clear-Cache & Reload #2855

Open
wants to merge 1 commit into
base: old_master
Choose a base branch
from

Conversation

auscompgeek
Copy link
Contributor

@auscompgeek auscompgeek commented Nov 8, 2020

Author: @jevolk

Rendered

@auscompgeek auscompgeek changed the title MSC2856: Server-Initiated Client Clear-Cache & Reload MSC2855: Server-Initiated Client Clear-Cache & Reload Nov 8, 2020
Signed-off-by: Jason Volk <jason@zemos.net>
@jevolk jevolk force-pushed the jevolk/msc-server-clear-cache branch from 54d0b76 to 5b89a30 Compare November 8, 2020 09:52

### Proposal

This MSC proposes a mechanism be standardized within the sync API to force a
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This sounds like a horible thing for accounts like those by TravisR, jcgruenhage and sorunome ^^ (They need quite a long time for initial syncs). (Not pinging on purpose)

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

In some cases the server messed up though and returned invalid events, effectively desyncing the server from the client. There is no way to recover from that, except by telling the user to clear cache and reload currently. This would provide an option to fix that, when the server side bug is fixed. One example of that is dendrite kicking you out of rooms and then never sending you a proper join again, just assuming you still know, that you are in that room, although it explicitly told you otherwise.

@turt2live turt2live added kind:feature MSC for not-core and not-maintenance stuff proposal A matrix spec change proposal proposal-in-review labels Nov 9, 2020
@turt2live turt2live added the needs-implementation This MSC does not have a qualifying implementation for the SCT to review. The MSC cannot enter FCP. label Jun 8, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind:feature MSC for not-core and not-maintenance stuff needs-implementation This MSC does not have a qualifying implementation for the SCT to review. The MSC cannot enter FCP. proposal A matrix spec change proposal
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

5 participants