schildichat-desktop in the command line, you can use profiles for different accounts, e.g.
See the related issues here: https://github.com/SchildiChat/schildichat-desktop/labels/encrypted%20room%20search
Enable them inside labs and add a new theme via URL inside the advanced section of the appearance settings.
Adding a theme with the same name again does not change it, you'll either have to remove the old one first and add it anew or directly change the account data.
Also make sure the
Access-Control-Allow-Origin: * header is set on the URL you're trying to load the theme from.
Here are some: https://github.com/aaronraimist/element-themes
To get help or discuss themes, join #element-themes:raim.ist.
Any theme for Element should work for SchildiChat as well.
/devtools as message in any room and remove it from the
im.vector.web.settings account data inside the
Linux users suffer from a Chromium bug which prevents the theme being updated if the system theme is being changed.
There's now a workaround with cli options which allows to override the detected system theme even for a running profile through abusing the multi instance prevention mechanism.
Let it switch to light mode:
schildichat-desktop --system-theme-light-override --hidden
Let it switch to dark mode:
schildichat-desktop --system-theme-dark-override --hidden
You have to do this for each profile seperately, just append the
--profile option to above commands.
See here: https://github.com/SchildiChat/schildichat-desktop/issues/61
Feel free to support existing issues, or file new issue on GitHub.
Schildi = Schildkröte = German for turtle. So "Turtle"-Chat. Feel free to call it Shieldy-Chat (shield for security?), if that's easier to pronounce for you.
A turtle with a post horn.
We mainly focus on tweaking the UI to our likings and usually do not want to go deep into architectural changes to reduce merge conflicts with upstream.
Sometimes, we like to play with additional community-based features that Element does not prioritize, which means we might support a few more MSCs than Element do.
It may also happen more often than expected that we include additional bug fixes compared to Element, if the Element team misses some bugs which become apparent in our internal testing. Of course, this does not imply that SchildiChat has less bugs, since we're not safe from introducing new ones either.
To summarize, the main goal of the SchildiChat clients is as following: we want to take a Matrix client that is good, and tweak it just to match our taste, since Element's design team has a different taste than we have, and our priorities do not always align with those upstream.
We are not trying to please any particular kind of target user group, except those who share our taste :)
When you have a look at the SchildiChat version, the part before "sc" is the upstream Element version that your current SchildiChat build is based on.
Since SchildiChat is a fork of Element, "upstream" refers to "Element".
You can translate SchildiChat-specific text at translate.schildi.chat! For Element-specific translations, visit their weblate, and we will get it for our next upstream merge.
Thanks for asking! However, we currently do not accept donation. Our goal is not to make money with this project, but just create a chat client that we enjoy using. As a result, we also do not feel any obligations to satisfy user expecations or wishes - this is a hobby project, after all. Feel free to donate to a charity of your choice instead, or to matrix.org directly for maintaining the matrix specification.
Matrix is a chat network, and so you can use it to get in touch with the SchildiChat community! Feel free to join any of the following:
We have announcement rooms that you can join: