Skip to content

Bring sliding sync out of experimental#1069

Merged
7w1 merged 39 commits into
devfrom
sliding-sync-stablization
Jul 17, 2026
Merged

Bring sliding sync out of experimental#1069
7w1 merged 39 commits into
devfrom
sliding-sync-stablization

Conversation

@7w1

@7w1 7w1 commented Jul 12, 2026

Copy link
Copy Markdown
Member

Description

  • Moved sliding sync into a shared "Data Sync" general section with the settings sync
  • Added a sliding sync toggle to the login screen, added a "swap to sliding/classic sync" clickable message to the loading screen.
  • Removed all the instance host options for sliding sync for an instance (afaik, it's usable ootb on Synapse, c10y, and tuwunel, so no reason to force it to be disabled). Sliding sync is still disabled by default, it's just more accessible now and should allow larger accounts to actually log in instead of using work arounds to log in so they can toggle the setting.
  • UI shell is rendered prior to full sdk init, technically means things load ever so slightly faster, but also feels faster since it's less loading screen and more UI shell. Also applies to standard sync.
  • Removed fallback loading screens from config and spec version checkers to prevent brief flickers of their messages and added the background grid to the base index.html to remove the flicker of white prior to any other files loading in.
  • Made the initial config fetch & versions check async, probably only saving a few milliseconds but easy enough. Applies to standard sync as well.
  • Made crypto start up concurrent instead of linear
  • Adjusted the initial sliding sync to be more minimal, aiming for only what's necessary to render a space/room.
  • I think I've fixed all mentioned bugs that are sliding sync specific that I can isolate in Experimental: Sliding Sync Issues #39
  • cached rooms and spaces in sidebar that get updated as syncs complete so the ui is usable prior to syncing all data on refreshes

Fixes #1091

Type of change

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to not work as expected)
  • This change requires a documentation update

Checklist:

  • My code follows the style guidelines of this project
  • I have performed a self-review of my own code
  • I have commented my code, particularly in hard-to-understand areas
  • I have made corresponding changes to the documentation
  • My changes generate no new warnings

AI disclosure:

  • Partially AI assisted (clarify which code was AI assisted and briefly explain what it does).
  • Fully AI generated (explain what all the generated code does in moderate detail).

AI did the tests, and also reviewed my code because some of this stuff is confusing. anyway. it works. i think.

@7w1 7w1 mentioned this pull request Jul 16, 2026
2 tasks
@7w1
7w1 marked this pull request as ready for review July 16, 2026 19:33
@7w1
7w1 requested a review from hazre as a code owner July 16, 2026 19:33
7w1 and others added 11 commits July 16, 2026 14:44
### Description

Open db should be closed so they don't leaks

<!-- Please include a summary of the change. Please also include
relevant motivation and context. List any dependencies that are required
for this change. -->

Fixes #

#### Type of change

- [x] Bug fix (non-breaking change which fixes an issue)
- [ ] New feature (non-breaking change which adds functionality)
- [ ] Breaking change (fix or feature that would cause existing
functionality to not work as expected)
- [ ] This change requires a documentation update

### Checklist:

- [x] My code follows the style guidelines of this project
- [x] I have performed a self-review of my own code
- [x] I have commented my code, particularly in hard-to-understand areas
- [ ] I have made corresponding changes to the documentation
- [ ] My changes generate no new warnings

### AI disclosure:

- [ ] Partially AI assisted (clarify which code was AI assisted and
briefly explain what it does).
- [ ] Fully AI generated (explain what all the generated code does in
moderate detail).
<!-- Write any explanation required here, but do not generate the
explanation using AI!! You must prove you understand what the code in
this PR does. -->
doesn't work on c10y :(
@github-actions

Copy link
Copy Markdown
Contributor

Deploying with  Cloudflare Workers  Cloudflare Workers

Status Preview URL Commit Alias Updated (UTC)
✅ Deployment successful! https://pr-1069-sable.raspy-dream-bb1d.workers.dev c2dd174 pr-1069 Fri, 17 Jul 2026 02:37:50 GMT

@7w1
7w1 merged commit 30204f5 into dev Jul 17, 2026
12 of 16 checks passed
@7w1
7w1 deleted the sliding-sync-stablization branch July 17, 2026 03:29
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

my offline status keeps reseting to online after a bit

2 participants