Regarding the screenshot.png file on the README.md page

[mahkoh]

Discussed in #808

^{Originally posted by onelittlehope March 16, 2026}
I noticed that the neofetch window in the screenshot reports the WM as sway and not jay. :-)

The neofetch project is archived and so can't get them to fix their detection logic.

With the 1.12.0 release, it might be a good time to update the screenshot with a new one show casing the control centre and window-to-tray project.

[mahkoh]

My concern with this is that the image is pretty large, almost 1.5 MB. Changing the image would mean that every clone would have to download an additional 1.5 MB. Not impossible but also not something that I want to do often.

[Stoppedpuma]

I would suggest looking into using avif for the screenshot since file size is a big factor and all modern browsers support it. AVIF lossless with avifenc -s 0 -l got the file down to 1.2 MB. If you're okay with visually lossless, avifenc -s 0 -q 80 got the file down to 201 KB and the image looks practically the same even when highly zoomed in. The file size can definitely be improved more from here.

Video showing me switching between the files (file name can be seen on the window title bar, screenshot.png is the original file).

avif.mp4

Up close text screenshot comparison:

[mahkoh]

Using avif with loss is probably ok. I've also looked into jxl but the quality seems to be worse at equivalent file sizes.

[kotarac]

LFS would mitigate this a bit by only needing to fetch the latest object currently in use by the repo and wouldn't waste space as the image changes over time.
It should show fine in the README.

Caveat is then LFS is basically there just for that, although since it's only that image, cloning without LFS and having the repo without git hooks for it wouldn't actually break anything else.

[mahkoh]

The problem with LFS is that data stored in LFS is never deleted unless the entire repo is deleted, even if I were to rewrite the repo to remove old files.

I'd prefer not to use LFS since it counts against my personal LFS quota.

[Stoppedpuma]

Using avif with loss is probably ok. I've also looked into jxl but the quality seems to be worse at equivalent file sizes.

I would've suggested jpeg-xl as well as it usually out performs avif for both lossless and lossy but browser support is still pretty lacking.

I'm surprised about avif outperforming jpeg-xl though, especially as heavily as I'm seeing in my local tests. I'll open an issue on the libjxl repo concerning that.