Page MenuHomePhabricator

[lib] Don't sync users with non-authoritative keyservers
ClosedPublic

Authored by tomek on Mar 7 2024, 4:52 AM.
Tags
None
Referenced Files
Unknown Object (File)
Thu, Apr 25, 7:23 AM
Unknown Object (File)
Apr 7 2024, 11:10 PM
Unknown Object (File)
Apr 6 2024, 10:05 AM
Unknown Object (File)
Apr 6 2024, 3:00 AM
Unknown Object (File)
Apr 5 2024, 2:41 AM
Unknown Object (File)
Apr 3 2024, 10:29 PM
Unknown Object (File)
Mar 31 2024, 6:09 AM
Unknown Object (File)
Mar 12 2024, 9:27 PM
Subscribers

Details

Summary

We can take a similar approach to what we do with threads that are being hashed - inform the server that there are no inconsistencies. This is a kind of hack, but it will be later improved when we start syncing the store between clients - then the keyserver will no longer attempt the sync.

https://linear.app/comm/issue/ENG-7132/stop-performing-state-sync-of-users-and-current-user-with-non

Test Plan

Check if the state sync still works for one keyserver - modify keyserver DB and check if the state is fixed.
Connect to the second keyserver and check if the state difference doesn't cause an update on client side - modified username on the authoritative keyserver and checked if the name remains changed after state sync with the second keyserver.

Diff Detail

Repository
rCOMM Comm
Lint
Lint Not Applicable
Unit
Tests Not Applicable

Event Timeline

tomek requested review of this revision.Mar 7 2024, 5:07 AM

This is quite hacky, but I guess it's fine since it's temporary

This revision is now accepted and ready to land.Mar 8 2024, 1:39 AM

Is this is a temporary hack, shouldn't we have a Linear task to revert it?

Is this is a temporary hack, shouldn't we have a Linear task to revert it?

This is a temporary hack, and this code will be completely removed / reworked as a part of https://linear.app/comm/issue/ENG-4730/syncing-keyserverstore-and-userstore-without-keyserver - so we don't need a dedicated task to handle it.