Thanks for your effort!

Pros: it’s Linux :D

Cons: it’s Linux ;(

I recently read this super interesting and in depth blogpost about this topic:

https://nocoffei.com/?p=451

Gaben is great!

But I was thinking of the founder of Blue Systems https://en.wikipedia.org/wiki/Blue_Systems

I agree, but I’m still glad some rich people are spending tons of money to make some free and very useful apps for me.

Ideally they should be doing it like the millionaire that partially funds KDE though.

I’m using soquartz compute modules on soquartz blades, because of the nvme slot and PoE. Just one cable for each is so nice in a tiny rack. They are running dietpi and docker swarm with dokploy.

I generally recommend the pine64 stuff, but shipping and tax might be high depending on where you live :/

Somehow both your screenshots are cut off where the red circle is.

But usually if it’s not in the settings, you have to open an issue at bugs.kde.org

5 seconds? How?

My grub is set to 2sec.

From pressing the power on button to an open start menu (I measure like this because the DE is still unusable for a good 5s after it becomes visible) it takes me about 36 seconds.

I recently tried hibernation thinking it would speed things up, but it takes about 2 minutes… huge RAM bad I guess.

(And yes, windows on the same hardware is way faster at about 17s, because it does some magic idk about)

Must be difficult if you judge an OS based on whether other users of it are nice online… how do you get anything done?

Sarcasm aside, I used to mod ad artix community back when I was using it and it was 99% support requests that have already been answered somewhere else… so like most other linux communities. And I’ve seen my share of toxic people in most of them. I mean, maybe it changed for the worst from when I last experienced it, but then, just don’t participate in the community?

The OS itself is alright. Pretty much same as arch, but you hage to tinker more… It gets somewhat annoying writing your own init/unit files for each app that needs systemd, thats why I switched back to plain old arch. I can see the tradeoff being worth it if you dislike the systemd direction/philosophy enough.

And I hate that artix puts it’s flair on KDE, just give me the vanilla experience, I don’t want to manually remove your ugly theme.

Yeah you probably have to play around with the flags to figure out the right approach. I can not look into it right now

The problem is that your desktop environment’s shortcut handler intercepts Alt+V before KeePassXC ever sees it, so the internal keybinding never fires. And when pgrep finds the process running, your command simply does nothing.

The fix is to use KeePassXC’s --auto-type CLI flag, which sends the auto-type signal to a running instance:

Command for your custom shortcut (Alt+V):

bash -c 'pgrep -x keepassxc > /dev/null && keepassxc --auto-type || keepassxc'

Not sure how keepass behaves though. Maybe you don’t need the condition at all and can just run keepassxc --auto-type from the shortcut and if there is no running instance it will start it.

https://chrisdown.name/2026/03/24/zswap-vs-zram-when-to-use-what.html

Mine sits at about 50-60W

same but it doesn’t change with load, whether it’s idle or maxed out, it’s in that watt range

I’ve been running it for 2 years.

The swarm support integration is first class, but there is not much to do in the gui, you can add nodes and see basic info about them and thats it basically.

Most of the stuff happens in the compose files where you can define how many copies of a container you run and what nodes you want to restrict them to. etc.

I’m not sure about the moving features tbh. It should move them automatically when a node is down. In my setup I don’t use that at all, all my containers are pinned to specific nodes by feature flags (one node has lots of hdd storage, another has more ram, another has a gpu).

You can see the container logs, but you have to select “swarm” in a dropdown when the container is not on your master node.

And also when deploying a new app you have to select “Compose” and then in a further dropdown “Swarm”.

deleted by creator

I’m running dokploy in swarm mode on 3 nodes.

The only downside is the development of swarm is basically halted and some features are missing (like passing /dev devices to a container, you have to use dirty workarounds) but otherwise it just works.

Should have used agpl if they wanted to be noble.

But this is just a corpo moating strategy.

Mostly the uutils.

• MIT license isn’t nice.
• They have way more CVEs than the core utils they replace.
• They don’t have feature parity yet, so if you use some rare flags in your scripts, those will break.

https://www.youtube.com/watch?v=tG2ZMvBT8W4

4:25

(sorry my third party youtube frontend can’t share timestamp links)

tldw:

• more CVEs than the old core utils that have been tested and in prod for over 30years
• no feature parity, so existing stuff that uses them will suddenly misbehave, when certain flags are missing
• different license, MIT instead of copyleft, so it’s more friendly for companies to use it for profit, while abusing the work of volunteer contributors

https://en.wikipedia.org/wiki/Anthropic#U.S._military_and_intelligence