7w1 fc7aec771c Some potential sync request spam fixes (#736)
<!-- Please read
https://github.com/SableClient/Sable/blob/dev/CONTRIBUTING.md before
submitting your pull request -->

### Description

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

As I haven't really had any issues I'm not 100% sure this fixes anything
at all, but it at least doesn't break anything.

Increase the timeout for background clients to 60s, separates them into
their own store, and makes sliding sync respect the setting instead of
the client setting, and hopefully better management.

Adds a startup timeout of 45s to the main loading screen to prevent
anything from getting stuck behind that which may or may not actually do
anything.

Replaces the sdk's thread root event fetching on initial load to prevent
the useless loading delay and request spam on load. Get's swapped back
once the client loads which then functions normally, only loading thread
events when a room is opened.

Also some random formatting changes that happened in initMatrix.ts when
I saved for some reason?? They're more readable imo so I just left them
in.

Also fixed the 1 lint issue from #730 

Maybe related to #710 

#### 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
- [ ] I have commented my code, particularly in hard-to-understand areas
- [ ] I have made corresponding changes to the documentation
- [x] My changes generate no new warnings

### AI disclosure:

- [x] 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. -->

Bickered with an AI to diagnose some potential syncing issues but none
of the changes were directly AI written.
2026-05-04 23:13:19 -05:00
2026-05-01 04:59:25 +03:00
2026-05-01 04:59:25 +03:00
2026-03-05 22:34:11 -06:00
2026-05-01 04:59:25 +03:00
2026-03-04 19:21:00 -06:00
2026-05-01 04:59:25 +03:00
2026-05-01 04:59:25 +03:00
2026-03-13 21:38:40 -05:00
2026-05-04 21:50:11 -05:00
2026-05-01 04:59:25 +03:00
2026-03-12 00:31:27 +01:00
2026-05-01 04:59:25 +03:00
2026-05-01 04:59:25 +03:00
2023-02-24 17:28:04 +05:30
2026-05-01 04:59:25 +03:00
2026-05-01 04:59:25 +03:00
2026-05-01 04:59:25 +03:00
2026-05-01 04:59:25 +03:00
2026-05-01 04:59:25 +03:00
2026-05-01 04:59:25 +03:00

Sable

A Matrix client built to enhance the user experience with quality-of-life features, cosmetics, utilities, and sheer usability. See the changelog.

Soon to be replaced desktop apps can be downloaded here. They auto-update by pulling the website.

Join our matrix space here to discuss features, issues, or meowing.

Forked from Cinny.

Getting started

The web app is available at app.sable.moe and gets updated on frequently, as soon as a feature is deemed stable.

You can also download our desktop app for windows and linux from releases.

Self-hosting

You have a few options for self hosting, you can:

  1. Run the prebuilt docker container.
  2. Deploy on a site like GitLab Pages. Jae has a guide here.
  3. Build it yourself.

Docker

Prebuilt images are published to ghcr.io/sableclient/sable.

  • latest tracks the current dev branch image.
  • X.Y.Z tags are versioned releases.
  • X.Y tags float within a release line.
  • Pushes to dev also publish a short commit SHA tag.

Run the latest image with:

docker run --rm -p 8080:8080 ghcr.io/sableclient/sable:latest

Then open http://localhost:8080.

If you want to override the bundled config.json, mount your own file at /app/config.json:

services:
  sable:
    image: ghcr.io/sableclient/sable:latest
    ports:
      - '8080:8080'
    volumes:
      - ./config.json:/app/config.json:ro

Build it yourself

To build and serve Sable yourself with nginx, clone this repo and build it:

pnpm i # Installs all dependencies
pnpm run build # Compiles the app into the dist/ directory

After that, you can copy the dist/ directory to your server and serve it.

  • In the config.json, you can modify the default homeservers, feature rooms/spaces, toggle the account switcher, and toggle experimental simplified slilding sync support.

  • To deploy on subdirectory, you need to rebuild the app youself after updating the base path in build.config.ts.

    • For example, if you want to deploy on https://sable.moe/app, then set base: '/app'.

Local development

Tip

We recommend using a version manager as versions change quickly. fnm is a great cross-platform option (Windows, macOS, and Linux). NVM on Windows and nvm on Linux/macOS are also good choices. Use the version defined in .node-version.

Execute the following commands to start a development server:

fnm use --corepack-enabled # Activates the Node version and enables corepack
# If you not using fnm, install corepack manually: npm install --global corepack@latest
corepack install # Installs the pnpm version specified in package.json
pnpm i # Installs all dependencies
pnpm run dev # Serve a development version

To build the app:

pnpm run build # Compiles the app into the dist/ directory

Deployment and infrastructure

Deployment workflows and infrastructure details live in infra/README.md.

S
Description
No description provided
Readme AGPL-3.0
107 MiB
0 Stars 1 Watchers 0 Forks
Languages
TypeScript 93.2%
Rust 5.2%
JavaScript 0.8%
Kotlin 0.2%
CSS 0.2%
Other 0.3%