<!-- 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#733 - animates apngs
Fixes#734 - adds dmed user to founders
Also fixes a few of the changeset types so they appear in the updates
#### 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. -->
<!-- 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.
<!-- 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. -->
Pulls themes and tweaks from https://github.com/SableClient/themes and
allows basic searching and filtering in the themes settings.
Migration modal should work fine, prompts the user to either enable
fetching from github or disable it and be limited to the built-in
light/dark themes.
Theme links that end in *.preview.sable.css from the official repo will
generate embeds, optional setting to allow generating embeds for any
*.preview.sable.css file.
In chat previews are generated with extracted css values and are safe
from injection. Full theme files will load the entire file, and are
vulnerable to injection, hence the official safe repo. Third party
themes sent in chat show a prominent banner making the risks clear.
Todo:
- ~~More clarity in settings menu when github fetching themes are
disabled (right now it just has a browse button that immediately enables
it, no confirmation or explanation)~~ updated labels and added
confirmation
- ~~Improve UI ?~~ consolidated card styling
Maybe worth adding in the future but out of scope for the time being:
- Info icon or some way to link to theme sources.
Mitigates #492 ?
Fixes#71Fixes#617 (via tweak in theme repo)
<img width="500" alt="image"
src="https://github.com/user-attachments/assets/3c97eb4c-0c3b-4b68-8ba5-132e1585ad1e"
/>
<img width="500" alt="image"
src="https://github.com/user-attachments/assets/600ce518-aba4-4679-8bf7-ed541587ac9a"
/>
#### Type of change
- [ ] Bug fix (non-breaking change which fixes an issue)
- [x] New feature (non-breaking change which adds functionality)
- [x] Breaking change - disables themes, but there's a migration modal
that prompts the user with 1 click to redownload and enable their
existing theme(s).
- [x] 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. -->
AI was used to write the code for parsing and extracting data from the
raw css files/links and dynamically populate the lists as well as
develop the migration system for current themes. Tests were AI
generated.
All code has (or will be) thoroughly reviewed by me by the time this PR
is ready.
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.
so much writing for such little change :(
### Description
partial implementation of
[MSC4459](https://github.com/matrix-org/matrix-spec-proposals/pull/4459)
Currently only sending the data and not rendering anything
Partially #729
#### 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:
No AI used
### Description
At some point between commits
[43cb531](https://github.com/SableClient/Sable/commit/43cb5313be960746c984bbf1336f1a0dfde078a4)
and
[f4cc4d5](https://github.com/SableClient/Sable/commit/f4cc4d51de4301c8e3f201ecc2aec4bb7604cc1d),
in the process of switching various UI elements into unified modals, the
read receipts modal (specifically the one that opens from an individual
message's context menu) lost its ability to be scrolled through.
In this patch, I've reverted that specific component to its old form,
both to immediately return the functionality and to provide a useful
reference state for the process of creating a more polished fix.
I recommend directly patching this pull request to properly unify the
modals first, but it _should_ be functional enough on its own to be
implemented as an immediate fix if you prefer.
#### 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).
<!-- 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. -->
Replaced Cinny's custom markdown parsing with marked which should
drastically reduce the various random obscure errors and crashes caused
by it.
Added math rendering support with KaTeX, sent using standard formatting
of $ for inline and $$ for block with LaTeX.
Supersedes #726Fixes#711Fixes#587Fixes#467Fixes#684
Tbh I doubt I've tested this enough so there's probably still a bunch of
bugs, especially in parsing html back to markdown, but hopefully it's
less than our current system?
Might consider using another library like Turndown for converting html
into markdown, currently using a partial custom parser with... well okay
results.
Updated to also remove the WYSIWYG editor because it's largely unused,
can be entirely covered by markdown, and complicates translating html to
markdown. Keyboard shortcuts from the editor have been rewritten to
instead apply markdown syntax.
#### Type of change
- [x] Bug fix (non-breaking change which fixes an issue)
- [x] New feature (non-breaking change which adds functionality)
- [x] Breaking change - removes the WYSIWYG editor.
- [ ] 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 (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 and then reviewed by me. I can confirm that the
tests probably test the right stuff.
I had AI do the initial merge and write the marked plugins for the link
preview hiding and spoiler hiding features, which I then tested and
reviewed.