I just use the built-in email function that comes with mdadm. If a drive fails, I’ll know right away and replace it with a spare. You do need your server to be able to send emails with something like postfix.

If you have hardware RAID, there’s often a monitoring tool that comes with it or at the very least a command-line utility that can report the RAID state which you can then use in a script.

Oh, you are going to love this one then if you haven’t seen it before: https://robertheaton.com/pyskywifi/

Additionally, the GUI in KDE plasma in System Settings is not entirely reliable. It sometimes makes stuff up about IPv6 rules for example. It seems to be a very light-weight wrapper over the FirewallD DBUS interface.

It’s in the announcement for Plasma 6.1, see https://kde.org/announcements/plasma/6/6.1.0/

To enable it, you need to use the Brightness & Colour widget. See also the merge request for this: https://invent.kde.org/plasma/plasma-workspace/-/merge_requests/4093

I guess the documentation is a bit lagging still! I don’t know about a list of compatible keyboards, but I suppose you can just try it out to see if it works! 😁

Yes, but you have to enable the checkbox “Increase maximum volume” in the audio widget on the taskbar panel.

The way I have it, is that I copied org.kde.plasma.browser_integration.json from /usr/lib/mozilla/native-messaging-hosts/org.kde.plasma.browser_integration.json (for Kubuntu 22.04, might be elsewhere for you) to ~/.var/app/org.mozilla.firefox/.mozilla/native-messaging-hosts and then changed the path to a shell script that calls the original executable with flatpak-spawn --host. Of course this kind of breaks sandboxing since you are allowing the browser to access programs on your machine but it works.

So I have: org.kde.plasma.browser_integration.json :

{
  "name": "org.kde.plasma.browser_integration",
  "description": "Native connector for KDE Plasma",
  "path": "/home/username/.var/app/org.mozilla.firefox/.mozilla/native-messaging-hosts/org.kde.plasma.browser_integration.sh",
  "type": "stdio",
  "allowed_extensions": ["[email protected]"]
}

and org.kde.plasma.browser_integration.sh

#!/bin/bash
flatpak-spawn --host /usr/bin/plasma-browser-integration-host "$@"

Don’t forget to chmod +x the shell script.

I have the same for the KeePassXC extension.

I have an AKASO Brave 7LE. I just take out the SD card and put it in an USB reader that I plug into my home server to move the videos. Then I just use my desktop for editing with Kdenlive which has a defish filter for getting rid of the camera distortion these actioncams have.

It’s also possible to connect to the camera through WiFi, but it’s much slower than using the SD card reader.

Regarding firmware updates, I don’t think AKASO is really into that but at some point I had an issue and support sent me a file that you just put on the SD card and the camera does the rest.

Yeah that is annoying. I just copy the link and paste in Firefox. I don’t ever need to go back I find since I only use Edge for MS365 stuff.

I use Edge daily for work. Everything it Office 365 and there is of course no Outlook client or Word or whatever on Linux. So I use the web version for everything. So I might as well have Edge to do the Microsoft since surely MS must make sure their stuff works on their own browser, right? (right??).

I also use the PWA version of Teams since the native client doesn’t really work well and since somewhat recently is also “officially” unsupported.

Anyway, it keeps the MS stuff separate from my normal browsing with Firefox and I’ve disabled JavaScript in Edge for all non-MS stuff. It works pretty well. Took me some battles to get rid of the Bing sidebar but they finally made that an option you can set.