If anyone’s wondering why Mihon looks slightly different than Tachiyomi, the reason is this is a fork of TachiyomiSY, which has some changes/features over Tachiyomi (e.g. a predicted next chapter release date).
What I wrote is all wrong. I’ve just looked through the commit history and Mihon is a fork of Tachiyomi and currently it doesn’t have any changes besides branding and being Android 8+.
I don’t know why I believed otherwise, but it might be F-Droids 3 months old Tachiyomi build, which lacked many features compared to up-to-date TachiyomiSY.
During setup there will be a page that asks if you want to create or restore from backups. If you hit “restore”, it’ll ask you to point it to the backups folder inside the Tachiyomi folder. Tachiyomi has backups set up by default, but if it’s disabled you can go to the settings to create a backup
Kakao (or whatever they’re called) were going after everyone involved, so Tachiyomi has been deprecated, one of the devs forked it and will continue development.
A long time Tachiyomi developer made the commits making branding changes to Mihon, so they might work together. But as they didn’t fork TachiyomiSY, its dev might continue work on it too.
I have read that the SY devs will now fork from mihon, and that they will develop both I think. No idea about the tachi dev. If that’s the case then I guess that that dev also worked on SY, or they talked or whatever. I’ll keep an eye on the commits and repo.
The devs just said fuckit afterwards, as you do when you get a lawsuit saying your about to be so far in debt because of your side project that your whole life will be turned up side down.
I use helium314/openboard on day to day basis, but the few times I use termux or have to ssh a linux box from my phone, unexpected keyboard is really awesome.
I couldn’t possibly care less about Docker Desktop. Portainer is a much better solution when graphical administration becomes necessary. (Which should be never)
This is interesting to me for my use case scenario, specifically SteamOS.
What I’m trying to do is run an emulated Everquest server (lookup EQEmu). The community there has several methods of installation of the server, Windows, Linux, and Docker. The hurdle to overcome is the immutable file system, specifically when it comes to the database (MariaDB). I think I may have found a work around via Linux brew and installing MariaDB through that (which I’ve done, I just have to make the final connection). However the Docker setup, when running it on a separate distro is stupid easy. If they make this a Flatpak, it can potentially be the solution I’m looking for.
Really the end goal is creating a Single player Everquest. I have a dual boot with it operating via Windows, but would much prefer to have it on the SteamOS side of the house.
Docker Desktop ≠ Docker Engine, and I think what you (and several in this thread) are thinking is actually Docker Engine. Docker Desktop ultimately includes a Docker Engine inside, but it does not appear you need that virtual machine (e.g. running non-Linux code). See: docs.docker.com/desktop/faqs/linuxfaqs/#what-is-t…
Docker Desktop is based on KVM, which already works with Flatpak. So this is not something new. For example, GNOME Boxes is available as Flatpak and provides a way to run KVM guests in SteamOS.
Starting with version 3.5 (the current stable) SteamOS already includes Podman with the default installation. And running the daemon-y Docker Engine “bare metal” is not going to be any easier with the immutable filesystem. While Docker Desktop solves this by using KVM, it adds another layer with performance loss, vs. just running Podman containers.
So what you want is already available, and no Docker Desktop is actually needed.
But so if Docker Desktop does include Docker Engine, does that mean I wiill now be able to run Docker (with a some performance loss) simply by installing a Flatpak, i.e. I won’t even need to touch the CLI?
Yes. If you mean “CLI” as for e.g. pacman install, it is a GUI (Electron) application, so I expect will install straight from e.g. KDE Discover and then run without you touching the shell.
Installing podman-compose with the immutable filesystem is fairly straight forward, since it is just a single Python file (github.com/containers/…/podman_compose.py), which you can basically install anywhere in your path. You can also first bootstrap pip (python3 get-pip.py --user with get-pip.py from github.com/pypa/get-pip) and then do pip3 install --user podman-compose.
github.com
Newest