It doesn’t support OPDS-PSE, which is the most common way of tracking progress.
It doesn’t support OPDS-PSE, which is the most common way of tracking progress.
It actually has a ui. But it looks minimal enough. I’ll try it.
Gollum. Hit integration is required if you value wiki content.
ConnectBot is fine.
Why do we invent new DEs instead of making proper settings app in already existing ones?
Fight for Americans’ fit bodies! Stop illegal oil production!
Wayland is like Busybox runit. Xorg is like SystemD.
Some seem to use Debian.
IMO the closest one.
Linux Libre makes Guix unusable on most hardware. It also requires much effort to configure. Learn scheme, how to use shepherD, etc.
It’s really cool, when automation tools create more problems than they actually solve.
There is really no reason to implement extensively audited runC in C, but the Dev only has the journey, no goals.
Ncmcpp, MPV with scripts
Not really. Void, alpine, gentoo are the only usable ones(besides non-systemd forks of arch and Debian). These are the only ones maintaining enough packages, providing enough documentation, not being just poorly maintained forks of X distro.
Misconfiguration is possible in any software. It’s not specific to sysvinit or systemd-init. Selinux was created to solve this.
I deleted it. No need for two almost identical posts to exist.
the added difficulties of making it system agnostic did not compensated for the low user base
Looks like Red Hat makes everything they can systemd-dependent. Including Gnome.
Compare it to vulnerabilities found in SysVinit, which was as common as systemd-init is now. There were no similar bugs, that would allow crashing an entire system just by executing a single command.
Kavita, same as Komga requires too much RAM.
Komga can track ebook reading progress, by converting them to images.