Andrew Jorgensen

If you can confirm that that's the correct tag for the build included in the repo, and that no modifications were made before compiling it might be sufficient. The license...

It's also supposed to be complete, so if snoreToast has dependencies outside of the KDE source tree (Qt?) we've got to be able to point to those too.

The prescribed way to provide a copyright notice with the Apache-2.0 license is with a separate NOTICE file. See https://www.apache.org/legal/src-headers.html#notice (but note that the form of that NOTICE is specific...

I'm more a fan of just following whatever [`prefers-color-scheme`](https://developer.mozilla.org/en-US/docs/Web/CSS/@media/prefers-color-scheme) happens to say than I am of implementing any kind of toggle for a specific page or feature.

> Hi. I want to help with this but it works fine on my computer. I checked this on Windows and Chrome. What is your OS / Browser? Chrome on...

> Agreed. We should start looking at the $XDG_ var. It's likely safer to use a library that already has the XDG spec implemented fully. It's not as simple as...

> I think this is incorrect. Electron doens't make any modifications to FFmpeg; it simply is designed to work with the library by being compiled or linked with FFmpeg. So...

Yes! That's the idea, except that `electron-v20.0.1-linux-x64.zip` *also* contains `libffmpeg.so`. I thought that `ffmpeg-v20.0.1-linux-x64.zip` contained a *different* build of FFmpeg (compiled with different options for licensing reasons?).

Oh, and it may not be only FFmpeg, because unless I'm mistaken there are some other copyleft things that are compiled into Chrome / Chromium / maybe Electron itself, and...

> The ffmpeg builds do not differ in licensing. i.e. the license for ffmpeg in `LICENSES.chromium.html` is accurate for both builds. Not for copyright licensing, but for patent licensing, AIUI....