Commit Graph
5121 Commits
Author SHA1 Message Date
7w1 dcd7bc3cd2 Fix klipy sending arbitrary urls and fix rendering arbitrary urls (#1107)
<!-- 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. -->

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:

- [ ] 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).
<!-- 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. -->
2026-07-17 15:14:38 -05:00
7w1 8c61ff1498 formatting 2026-07-17 15:11:47 -05:00
7w1 0cb4fbcb3d changeset and update knope formatting 2026-07-17 15:09:56 -05:00
7w1 8099c4c494 ensure gifs require klipy proxy, harden url parsing, and add tests 2026-07-17 14:40:07 -05:00
7w1 988346959e fix profile data not syncing on mobile (#1106)
<!-- 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. -->

Fixes #

#### 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).
<!-- 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. -->
2026-07-17 12:09:16 -05:00
7w1 995435bca0 fix profile data not syncing on mobile 2026-07-17 11:53:23 -05:00
7w1 7b60c45ec5 Fix unnecessary livekit support checks (#1099)
<!-- 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. -->

Allows users without livekit backends setup to join existing calls again

#### 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:

- [ ] 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).
<!-- 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. -->
2026-07-16 22:37:10 -05:00
7w1 280f6228b5 Fix encrypted message perms & DM names (#1098)
<!-- 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. -->

Fixes #1097 
Fixes #1092 

#### 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:

- [ ] 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).
<!-- 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. -->
2026-07-16 22:32:47 -05:00
7w1 30204f54b5 Bring sliding sync out of experimental (#1069)
<!-- 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. -->

- 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 #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

- [x] Bug fix (non-breaking change which fixes an issue)
- [x] 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:

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

AI did the tests, and also reviewed my code because some of this stuff
is confusing. anyway. it works. i think.
2026-07-16 22:29:15 -05:00
7w1 c2dd174394 add banners to subscription 2026-07-16 17:25:45 -05:00
7w1 56bfccccc2 scope extensions
doesn't work on c10y :(
2026-07-16 17:10:58 -05:00
7w1 b5e0ec8143 cleanup unused stuff 2026-07-16 16:41:27 -05:00
7w1 01587d9cad Merge branch 'dev' into sliding-sync-stablization 2026-07-16 16:30:37 -05:00
7w1 c7c528a3a0 formatting 2026-07-16 16:15:21 -05:00
7w1 f2078ac0b2 Merge branch 'sliding-sync-stablization' of https://github.com/SableClient/Sable into sliding-sync-stablization 2026-07-16 16:11:36 -05:00
7w1 2d95c353bf optimize room data subscriptions 2026-07-16 16:11:32 -05:00
7w1 b05d5f9178 fix: render new messages divider when read receipt anchors on a filtered event (#1101)
<!-- Please read
https://github.com/SableClient/Sable/blob/dev/CONTRIBUTING.md before
submitting your pull request -->

### Description

Follow-up to #1095. The divider re-anchoring worked, but in busy rooms
the divider often didn't show up at all after tabbing back in.
Now the divider position is tracked across every iterated event, before
the render filters run, so a receipt on a filtered event still places
the divider on the next rendered message. Regression tests cover each
filtered anchor type; they fail on `dev` and pass here.

<!-- 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
- [x] I have made corresponding changes to the documentation
- [x] 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. -->
2026-07-16 20:55:32 +00:00
Erwan Leboucher 131224d66c fix: render new messages divider when read receipt anchors on a filtered event 2026-07-16 22:43:30 +02:00
7w1 303fa7028b fix: close IndexedDB connections to prevent leaks (#1100)
### 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. -->
2026-07-16 15:14:40 -05:00
7w1 e0d7406238 hide connecting and add some diagnostics 2026-07-16 15:09:55 -05:00
Erwan Leboucher 4384599a79 fix: close IndexedDB connections to prevent leaks 2026-07-16 22:08:45 +02:00
7w1 1e0acd629e Update improve-sliding-sync.md 2026-07-16 14:44:58 -05:00
7w1 dcdb0b60f3 improve the caching i think 2026-07-16 14:29:04 -05:00
7w1 4032d1f184 remove stale rooms 2026-07-16 14:11:35 -05:00
7w1 f24c03371e extract client config and have it block load 2026-07-16 14:04:41 -05:00
7w1 aadf445e23 changeset and disable presence manager from dev 2026-07-16 13:44:55 -05:00
7w1 7c29062403 Merge remote-tracking branch 'origin/dev' into sliding-sync-stablization 2026-07-16 13:38:46 -05:00
7w1 08fd774312 Create fix-join-existing-calls-without-livekit.md 2026-07-16 13:16:10 -05:00
7w1 c7913e8397 dont require livekit to answer/join calls 2026-07-16 13:12:31 -05:00
7w1 00fd9ca7ef fix room naming 2026-07-16 12:52:59 -05:00
7w1 c74a546efb Create fix-encrypted-message-power-level.md 2026-07-16 12:39:23 -05:00
7w1 1747db887b fix permission checks for encrypted rooms 2026-07-16 12:33:15 -05:00
7w1 b07f7a60d9 Theme system improvements (#1087)
<!-- 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. -->

Fixes #774 
Adds pages for tweaks/themes browsing
Adds some simple catalog auto updating based on hashes
Adds the ability to load themes from uploaded `.sable.css` files in
rooms

#### 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:

- [ ] 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:

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

Tests were AI generated
2026-07-16 12:18:22 -05:00
7w1 f5bc7594df Merge branch 'dev' into theme-system-improvements
# Conflicts:
#	src/app/components/message/MsgTypeRenderers.tsx
2026-07-16 12:11:04 -05:00
7w1 29d8df9982 only update installed themes 2026-07-16 12:03:34 -05:00
7w1 2f4dcc0d8d fix: re-anchor new messages divider at last read when tabbing out (#1095)
<!-- Please read
https://github.com/SableClient/Sable/blob/dev/CONTRIBUTING.md before
submitting your pull request -->

### Description
The "New Messages" divider was anchored to the read position captured
when the room was first opened (unreadInfo is computed once on mount and
never refreshed while the room stays open). So if you kept a room open,
tabbed away, and messages streamed in, the timeline auto-scrolled but
the divider stayed stuck at the open-time position instead of marking
where you actually left off.

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. -->
2026-07-16 15:47:26 +00:00
7w1 e13dc1616c fix: render redacted state events as deleted instead of hiding them (#1090)
<!-- Please read
https://github.com/SableClient/Sable/blob/dev/CONTRIBUTING.md before
submitting your pull request -->

### Description

When a state event (room name, topic, avatar, membership, pins, etc.) is
redacted, Sable either:
- renders it with empty/garbage content (e.g. "changed room name" with
no name), or
- hides it entirely (the fallback handler returns null on empty content)

Fixes #988

#### 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:

- [ ] 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. -->
2026-07-16 15:46:02 +00:00
7w1 8f7100a054 feat: show unread count in page title (#1093)
<!-- Please read
https://github.com/SableClient/Sable/blob/dev/CONTRIBUTING.md before
submitting your pull request -->

### Description

Adds an unread indicator to the browser tab <title> so a backgrounded
Sable window shows new-message state at a glance. A new PageTitleUpdater
component watches the unread atom and sets document.title to (N) Sable
Client when there are unread mentions, reverting to Sable Client when
there are none.

<img width="171" height="34" alt="image"
src="https://github.com/user-attachments/assets/f9ab0428-8de6-4254-820d-2462a130a47c"
/>

Fixes #1082

#### Type of change

- [ ] Bug fix (non-breaking change which fixes an issue)
- [x] 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
- [x] 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. -->
2026-07-16 15:41:49 +00:00
Erwan Leboucher 6412a0ac91 feat: show unread count in page title 2026-07-16 10:58:47 +02:00
Erwan Leboucher f3cb4b74c5 fix: re-anchor new messages divider at last read when tabbing out 2026-07-16 10:41:24 +02:00
7w1 b68bc73e80 fix unreads
seems to require a timeline item sadly
2026-07-15 17:41:29 -05:00
7w1 071b29bff7 adjust sliding sync toggle style and login with sso compatibility 2026-07-15 17:10:28 -05:00
7w1 539125cb14 fix presence sync and member list subscription 2026-07-15 16:48:44 -05:00
Erwan Leboucher 8d8692daec fix: render redacted state events as deleted instead of hiding them 2026-07-15 23:34:55 +02:00
7w1 ae69b8bbaf fix: render redacted messages as deleted instead of unsupported (#1089)
<!-- 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. -->

When sliding sync delivers a message that has been redacted, the
redaction event may not be in the client's timeline. In this case,
mEvent.isRedacted() returns false even though the event content has
already been stripped to {}.

Sable's timeline renderer only checked isRedacted(), so these messages
fell through to the fallback renderer and displayed as "Unsupported
message (no body)".
This adds an isContentEmpty check (Object.keys(safeContent).length ===
0) so that m.room.message events with empty content render as "Message
deleted" instead.

<img width="321" height="73" alt="Screenshot 2026-07-15 at 22 57 30"
src="https://github.com/user-attachments/assets/82cae806-1a14-473d-b45c-045de6032b81"
/>

```json
{
"content": {},
"origin_server_ts": 1784136316933
},
...
{
   "content": {
                "redacts": "$3xt7_zZiHMYPEdrDXaEFvu5cPtv-flc-oijPuv9elbU"
            },
            "origin_server_ts": 1784136364105,
```

#### 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
- [ ] 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. -->
2026-07-15 21:16:47 +00:00
7w1 1300e3ac1c stabilize sliding sync room state and membership updates 2026-07-15 16:11:27 -05:00
Erwan Leboucher 2b1f7c5971 fix: render redacted messages as deleted instead of unsupported 2026-07-15 23:10:02 +02:00
7w1 ea95d17f99 Fix file downloads not always being the right files (#1086)
<!-- 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. -->

Fixes #1084 

Centralizes the download file name generation and adds some related
safety and hardening

#### 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:

- [ ] 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).
<!-- 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. -->
2026-07-15 16:08:45 -05:00
7w1 487955465e Merge branch 'dev' into sliding-sync-stablization
# Conflicts:
#	src/app/pages/auth/login/loginUtil.ts
#	src/app/pages/client/BackgroundNotifications.tsx
#	src/app/pages/client/space/SpaceProvider.tsx
#	src/client/initMatrix.ts
2026-07-15 14:59:29 -05:00
7w1 6f73b46c0e fix: allow joining spaces with sliding sync enabled (#1085)
<!-- Please read
https://github.com/SableClient/Sable/blob/dev/CONTRIBUTING.md before
submitting your pull request -->

### Description

With sliding sync enabled, joining a space was impossible. The root
cause was a navigation dead-end: when a room's m.room.create event
wasn't yet in the client store (common with sliding sync's delivery
model), isSpaceRoom() returned false, causing spaces to be misrouted.

<!-- 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
- [ ] 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:

- [ ] 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. -->
2026-07-15 19:42:06 +00:00