Commit Graph
2569 Commits
Author SHA1 Message Date
7w1 4d2fcfccbe fix: harden Matrix HTML sanitization (#571)
### Description

- switch Matrix custom HTML sanitization from `sanitize-html` to
`DOMPurify`
- enforce the Matrix v1.18 tag and attribute allowlist exactly,
including scheme and `mxc://` restrictions
- sanitize reply previews before trimming/parsing so untrusted
`formatted_body` never reaches the reply extraction path unsanitized
- move `data-mx-color` and `data-mx-bg-color` translation to render time
and explicitly ignore incoming `style` in the HTML parser
- use `sanitizeText` for plain-text interpolation paths that were
previously running through the HTML sanitizer
- add regression tests for sanitizer allowlist behavior, reply preview
sanitization, parser color translation, and parser-side style stripping

#### 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
- [x] My changes generate no new warnings

### AI disclosure:

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

This PR replaces the Matrix custom HTML sanitizer with a DOMPurify-based
implementation that matches the Matrix v1.18 allowlist instead of the
broader legacy rules. The sanitizer now validates tag-specific
attributes, rejects incoming `style`, limits links to
`https/http/ftp/mailto/magnet`, limits images to `mxc://`, strips
`mx-reply`, and keeps the existing nesting guard. Reply previews now
sanitize `formatted_body` before any reply trimming or parsing. The
React HTML parser now turns `data-mx-color` and `data-mx-bg-color` into
React styles at render time and ignores raw incoming `style` attributes
even if unsanitized HTML somehow reaches the parser. The plain-text HTML
interpolation paths in forwarding, the room composer, and the message
editor now use text escaping instead of the HTML allowlist sanitizer.
The new tests lock down the sanitizer contract, the reply-preview
regression, parser color translation, and parser-side style stripping.
2026-03-30 02:50:05 +00:00
hazre fb1732ce82 fix: harden MXC image rendering and simplify HTML paths 2026-03-29 23:42:17 +02:00
Rye dae8e6ac29 fix(PMP, ID): changed pmp id handling and generation 2026-03-29 03:29:56 +02:00
Shea c2de0c5e4e Merge branch 'SableClient:dev' into links-msc4095 2026-03-29 00:01:33 +02:00
Shea Duma f4ddda6048 added general fallback 2026-03-28 22:08:54 +02:00
Shea Duma 8b287644d9 added /shorts/ support to stop sable from crashing 2026-03-28 22:04:54 +02:00
hazre 149550639c Merge remote-tracking branch 'origin/dev' into hazre/fix/matrix-html-sanitization
# Conflicts:
#	src/app/components/message/Reply.tsx
#	src/app/features/room/RoomInput.tsx
2026-03-28 17:33:33 +01:00
hazre ee1b718737 fix: harden Matrix HTML sanitization 2026-03-28 17:11:25 +01:00
7w1 14b2e34f33 fix: recover profile and avatar loading (#566)
### Description

Fixes profile and avatar loading regressions introduced around the
MSC4440 bio compatibility work.

This PR addresses two related problems:

- Own profile data could disappear when `useUserProfile` encountered
`gay.fomx.biography` in an unexpected shape or when the field was
missing entirely.
- Avatar components could get stuck in fallback mode after a transient
image load failure, causing the account avatar and other avatars to
disappear until a full reload.

The fix does three things:

- parses `gay.fomx.biography` defensively with optional access instead
of assuming `m.text[0].body` always exists
- retries profile fetches when the cache was previously poisoned into an
`_fetched`-only state after normalization failed
- resets avatar error state when the image `src` changes so transient
media/auth failures can recover on later renders

This was verified against the broken Account settings / account switcher
behavior where avatar, banner, bio, status, and pronouns could appear
missing.

Fixup of #559

#### 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 (GitHub Copilot)

`useUserProfile.ts`: Hardened MSC4440 bio parsing so missing or
malformed `gay.fomx.biography` data does not throw during normalization,
and allowed refetching when the profile cache only contains `_fetched:
true` from a prior failed normalization.

`UserAvatar.tsx` and `RoomAvatar.tsx`: Reset local image error state
when `src` changes so a temporary image load failure does not
permanently lock the component into fallback rendering.
2026-03-28 15:26:37 +00:00
Rose 5433f293c1 FIX dev branch error with loading youtube links that have no params (#570)
<!-- Please read
https://github.com/SableClient/Sable/blob/dev/CONTRIBUTING.md before
submitting your pull request -->

### Description
This is a quick and dirty fix to youtube links not having parameters

**This fixes a branch issue**

#### 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. -->
I have asked God for the solution
2026-03-28 15:26:10 +00:00
Shea Duma e286911a6a removed redundant fallback 2026-03-28 17:24:29 +02:00
7w1 748794cedc fix: scroll-to-bottom regression and timeline pagination fixes (#529)
### Description

Fixes several timeline bugs introduced after the
timeline-reset-on-navigation refactor:

- Scroll-to-bottom no longer gets stuck after navigating to a room
- Timeline pagination no longer uses a stale timeline chain after a
sliding sync reset
- URL preview requests are deduplicated so the same URL only fires one
network request
- Removed a redundant spidering call that was generating an extra
sliding sync request per room visit

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
- [x] My changes generate no new warnings

### AI disclosure:

- [x] Partially AI assisted (GitHub Copilot)

`RoomTimeline.tsx`: Added a `liveTimelineLinked` guard so the initial
scroll doesn't fire with stale data from the previous room, and a
`pendingReadyRef` that defers `setIsReady(true)` when `processedEvents`
is still empty (preventing the room opening at position 0).
`useTimelineSync.ts`: A `useEffect` resets the timeline state on room
change so revisited rooms aren't stuck with `liveTimelineLinked =
false`. Reads `linkedTimelines` fresh after each `await` in pagination
so a sliding sync reset mid-paginate doesn't cause count comparisons on
a detached chain. A `continuing` flag prevents two concurrent pagination
calls from racing on the lock. URL preview dedup uses a module-level
`Map` to share in-flight promises for the same URL. Removed a redundant
`startSpidering` subscription call in the sync setup path.
2026-03-28 10:23:55 -05:00
Evie Gauthier 724b45fd61 fix: remove extra blank line in useUserProfile.ts 2026-03-28 11:09:29 -04:00
Shea Duma 705adf0d6e fix youtube video links missing params in dev branch 2026-03-28 16:59:24 +02:00
Rose e0a666c6ef Add PluralKit style command (limited) handler an proxy recognition (#550)
### Description

Fixes #427
Fixes #425 (you can use shorthands, instead of `/usepmp`)

#### PluralKit Compatibility and Per-Message Profile Enhancements

- Added limited compatibility for PluralKit-style (`pk;member`)
commands, allowing users to interact with PMPs using familiar PK syntax.
- Introduced shorthand syntax for sending messages with a Persona, such
as `✨:test`, and an option to enable/disable this in settings.
- Added a new settings section (`PKCompatSettings`) in the Persona
profile page to toggle PK command compatibility and shorthand proxying.

#### Command Handling Improvements

- Updated `/addpmp` and `/usepmp` command parsing to use regular
expressions, fixing syntax issues and clarifying usage. The `/usepmp`
command now has a new syntax and properly resets room associations when
requested.
- Added a new `/pmpproxy` command to associate a proxy with a profile,
and integrated feedback for unsupported flags in `/usepmp`.

#### Data Model and Utility Updates

- Expanded the per-message profile data model to support compatibility
versions and proxy associations, including new type definitions and
parsing utilities.

These changes collectively improve the user experience for those using
per-message profiles and PluralKit-style workflows, and provide more
flexible and robust command handling.

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

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

no AI was used in the creation of this PR
2026-03-28 14:56:56 +00:00
Rose a912387e2d Fix unsanitized HTML in reply renderer (#569)
### Description

Fix reply preview rendering so formatted reply content is sanitized
before React HTML parsing.

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:

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

AI-assisted parts:
- Extracted `sanitizeReplyFormattedPreview()` in `Reply.tsx` so
formatted reply previews are always sanitized before parsing.
- Added regression tests in `ThreadIndicator.test.tsx` for quote
stripping and sanitizer behavior.
- Adjusted the test payload and formatting to satisfy lint and prettier
checks.
2026-03-28 14:52:47 +00:00
Evie Gauthier 0816b0aa65 test: fix reply sanitizer regression test lint issues 2026-03-28 10:39:36 -04:00
Evie Gauthier 04fd0fd76e Fix reply HTML sanitization and add regression test 2026-03-28 10:29:35 -04:00
Evie GauthierandCopilot 2a30a22c24 Update src/app/hooks/useUserProfile.ts
Co-authored-by: Copilot <[email protected]>
2026-03-28 01:28:15 -04:00
Evie Gauthier e7fd523759 chore: format profile avatar fix files 2026-03-28 01:25:41 -04:00
Evie Gauthier 7ac1935424 Revert "fix: recover profile and avatar loading"
This reverts commit fe3900a657.
2026-03-28 01:21:45 -04:00
Evie Gauthier 282de15601 fix: recover profile and avatar loading 2026-03-28 01:19:39 -04:00
Evie Gauthier fe3900a657 fix: recover profile and avatar loading 2026-03-28 01:13:31 -04:00
Evie Gauthier 6ccb85f96b fix: resolve PR #529 quality check failures 2026-03-27 23:52:45 -04:00
Evie Gauthier f9c725e0ab Add tests 2026-03-27 23:33:47 -04:00
Evie Gauthier 1114c047d5 fix: resolve Copilot code review comments on PR #529
- Clear initialScrollTimerRef when room changes to prevent stale timer
  from firing in a new room after navigation (RoomTimeline.tsx)
- Scope URL preview cache by MatrixClient to prevent cross-account
  deduplication when multiple clients/sessions exist (UrlPreviewCard.tsx)
- Delete cache entries after promise settles (both success/rejection)
  to prevent unbounded cache growth over long sessions (UrlPreviewCard.tsx)
- Fix pagination token direction check: use appropriate timeline end
  and token direction based on pagination direction (forward/backward)
  instead of always checking first timeline's backward token
  (useTimelineSync.ts)
2026-03-27 23:17:03 -04:00
Evie Gauthier f707acc713 fix: scroll-to-bottom race and stale lTimelines after pagination
RoomTimeline.tsx:
- Add liveTimelineLinked guard to the initial-scroll useLayoutEffect.
  Without this, a render with stale data from the previous room (before
  the room-change reset propagates) fires scrollToIndex at the wrong
  index and marks hasInitialScrolledRef = true, blocking the correct scroll
  when the right data arrives.
- Add pendingReadyRef to defer setIsReady(true) when the 80 ms timer fires
  but processedEvents is empty (e.g. the onLifecycle reset cleared the
  timeline within the window). A recovery useLayoutEffect watches for
  processedEvents.length becoming non-empty and performs the final scroll +
  setIsReady when the flag is set. Previously setIsReady(true) was called
  unconditionally from the timer, revealing the room at position 0 when
  events had not yet arrived.
- Reset pendingReadyRef on room change so dangling recovery state from a
  previous room cannot fire in the new room context.

useTimelineSync.ts:
- After await paginateEventTimeline, re-read from timelineRef.current
  instead of using the pre-await lTimelines capture. A sliding sync reset
  (resetLiveTimeline) during pagination replaces lTimelines[0] with a new
  EventTimeline object; the stale reference causes getLinkedTimelines to
  traverse the wrong chain, making countAfter/countBefore comparisons wrong
  and triggering incorrect pagination decisions.
- Add room-change useEffect that resets the timeline state to the new room's
  initial linked timelines when room.roomId changes. Without this, the
  component retains stale data from the previous room, keeping
  liveTimelineLinked false until a TimelineReset event fires -- which may
  never happen for revisited rooms where the sliding sync response does not
  include initial:true.
2026-03-27 22:10:52 -04:00
7w1 f0ad4f5b33 Fix message forwarding by removing relation to avoid issues (#558)
### Description

This pull request fixes an issue with forwarding messages for users on
Synapse homeservers by ensuring that relations and mentions are properly
removed from forwarded messages. The changes focus on improving privacy
and preventing confusion when messages are forwarded to other rooms.

#### Forwarding and privacy improvements

- Removed the `m.relates_to` and `m.mentions` fields from the forwarded
message content to avoid leaking relations or mentions from the original
message.
- Removed the addition of a new `m.relates_to` relation when
constructing the forwarded message, preventing references to the
original event in the forwarded message.

Fixes #539

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

no AI was used in the creation of this PR
2026-03-27 22:59:45 +00:00
Vesper 5f62b92ffe Try to strip HTML from the plain text body field 2026-03-27 21:30:06 +00:00
Vesper 05de0d6b34 Add example 2026-03-27 20:17:51 +00:00
Vesper 34924ec8f3 Add /html command 2026-03-27 18:50:39 +00:00
Rose dae136e119 Implement initial MSC4440 Bios with extensible events formatting (#559)
### Description

This pull request adds support for saving and reading user bios in the
MSC4440 format, improving compatibility with the MSC4440 specification
for Matrix user profiles. The changes ensure that bios are now stored
and retrieved in both the legacy and MSC4440-compliant formats, and
introduce new types to support this functionality.

#### MSC4440 Bio Compatibility

- User bios are now saved in the MSC4440 format (`gay.fomx.biography`)
in addition to existing formats, ensuring forward compatibility with the
MSC4440 spec. When saving, both HTML and plain text representations are
stored.
- The user profile normalization logic now reads bios from the MSC4440
field first, falling back to legacy fields if necessary.
- The fields handled by the normalization function are updated to
include the MSC4440 bio key.

#### Type and Import Updates

- New types `MSC1767Text` and `MSC4440Bio` are introduced to represent
the MSC4440 bio format, and relevant imports are updated throughout the
codebase.

implements https://github.com/matrix-org/matrix-spec-proposals/pull/4440

#### 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
- [ ] 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).

No AI was used in the creation of this PR
2026-03-27 17:32:04 +00:00
Rye 0c62e75576 it now uses extensible events to format the bio, as per msc4440 2026-03-27 17:26:29 +01:00
Rye 9c61f4c62e fix(message forwarding): remove relation from the forwarded message, to avoid synapse weirdness 2026-03-27 16:13:26 +01:00
Rye 6e238ef948 first implementation of MSC4440 Bios (will have to be changed later) 2026-03-27 15:13:17 +01:00
7w1 86a3ccb88f fix: fetch room/sender avatar and display name for push notifications (#551)
### Description

When the pusher is configured with `event_id_only` format, the service
worker fetches event details itself rather than receiving them in the
push payload. Previously only the sender display name and room name were
retrieved — `room_avatar_url` was always `undefined`, so every
notification showed the default app logo regardless of whether the room
or sender had an avatar set. Display names could also be stale in the
encrypted path when the app resumed from a cold state.

**Changes in `src/sw.ts`:**

- `fetchMemberDisplayName` → `fetchMemberInfo`: the same single HTTP
request to `m.room.member` state now also extracts `avatar_url`, giving
both display name and sender avatar for free
- `fetchRoomAvatar`: new helper that fetches the `m.room.avatar` state
event URL
- `mxcToNotificationUrl`: converts `mxc://` to a legacy unauthenticated
thumbnail URL (`/_matrix/media/v3/thumbnail/…`) so the OS can load the
notification icon without an auth header
- `handleMinimalPushPayload`: room avatar is now fetched in the initial
parallel batch alongside the event and room name; icon is resolved as
room avatar → member avatar (DM fallback) → default logo;
`room_avatar_url` passed to all `handlePushNotificationPushData` call
sites
- Encrypted relay path now uses the server-fetched `senderDisplay`
(authoritative) rather than the SDK cache value from the relay, which
can be absent or stale when the app hasn't fully synced after a cold
resume

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
- [x] My changes generate no new warnings

### AI disclosure:

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

`fetchMemberInfo` extends the existing member state fetch to also return
`avatar_url`. `fetchRoomAvatar` GETs `m.room.avatar` state.
`mxcToNotificationUrl` builds a legacy `/_matrix/media/v3/thumbnail/`
URL (no auth required, OS-loadable) from an `mxc://` URI.
`handleMinimalPushPayload` adds `fetchRoomAvatar` to its parallel fetch
batch, resolves the notification icon with room > member > default
priority, and passes it through as `room_avatar_url` to every
`handlePushNotificationPushData` invocation. The encrypted relay path is
updated to prefer the server-fetched display name over the relay's
potentially-stale SDK cache value.
2026-03-27 03:46:59 +00:00
7w1 8e30086bf4 add ability to show user info in member and state event messages (#536)
### Description

Add ability to open the user hero by clicking on the usernames shown in
member and state events (e.g. user joins room, room name changed). I
expected this behavior based on previous usage of discord, it wasn't
doing anything previously so I think this is a useful addition.

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

- [ ] 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).
2026-03-27 03:34:03 +00:00
Rye 0c7911cbf8 fix: remove unused files and added fallback for regex escaping 2026-03-27 02:32:41 +01:00
Rye 7dfafc31c8 Merge branch 'feat/compat/pluralkit' of https://github.com/dozro/Sable2 into feat/compat/pluralkit 2026-03-27 01:44:18 +01:00
Rye bc8e9646ce docs(PMP-Command): adjusted the description of /usepmp and also added a changeset 2026-03-27 01:43:33 +01:00
Rose 523fcbbc9f Merge branch 'dev' into feat/compat/pluralkit 2026-03-27 01:39:39 +01:00
Rye 155ac64c65 fix(PMP-Command): fix the syntax handling of pmp related command 2026-03-27 01:38:05 +01:00
Evie Gauthier a704a3500f Merge branch 'dev' into fix/bug-fixes 2026-03-26 17:25:14 -04:00
Evie Gauthier 32663bd51c Merge branch 'dev' into fix/push-notification-metadata 2026-03-26 17:24:08 -04:00
7w1 95cdfa1b23 feat: room abbreviations with hover tooltips and space inheritance (#514)
<!-- Please read
https://github.com/SableClient/Sable/blob/dev/CONTRIBUTING.md before
submitting your pull request -->

### Description

Adds a room abbreviations feature: moderators can define term/definition
pairs in room settings. Defined terms are highlighted with a dotted
underline in messages and show a tooltip on hover (tap-to-pin on
mobile). Abbreviations defined in a parent space are inherited by child
rooms and nested spaces, with overrides allowed at each level. The
settings UI shows a flat list of inherited and locally-defined entries.

Fixes #

#### 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
- [ ] 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).
- [X] 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. -->

The code adds changes that allow for setting and viewing room
abbreviations, with an on-hover tooltip (or press on mobile -
semi-persistent). It stores these in the room state under a new key, and
recursively fetches abbreviations from the space level. This also adds
regex so that abbreviations correctly work at word boundaries. Also adds
the needed hooks to `room.ts` and `slidingSync.ts`
2026-03-26 21:18:00 +00:00
7w1 99d2b4bf87 fix confusing ui for client side embed settings (#535)
### Description

this is a tiny fix to a potentially confusing "problem" that i thought
of when going to sleep last night, previously if you enabled client side
embeds in both unencrypted and encrypted rooms, and then turned off the
main client side embeds toggle, the encrypted rooms setting would remain
on, even though it would be hidden in the setting ui

feel free to just close if this is stupid

#### 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
- [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).
2026-03-26 21:17:16 +00:00
7w1 64082c4cec Add better parsing for youtube embed links (#534)
### Description

Replace the previous hacky regex method with a slightly better link
parser. Add support for timestamps, playlists and youtube music links,
tracking info is still stripped and embeds use the timestamp. Previously
none of these features were supported, this might also be slightly more
robust.

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

- [ ] 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).
2026-03-26 21:16:50 +00:00
Evie Gauthier cc2c51a95b fix: replace for...of with Array.from().forEach() to satisfy no-restricted-syntax 2026-03-26 16:50:52 -04:00
Evie Gauthier 5ddb05e1b4 fix: address review comments on room abbreviations PR 2026-03-26 16:40:33 -04:00
Rye 2a4fd48af9 feat(PMP-PK): added more options (removing shorthand,...) and documentation 2026-03-26 19:47:59 +01:00