The scale of this takedown is pretty staggering:
- What happened?
MangaDex received a takedown request that affected approximately 7,000 titles.
The scale of this takedown is pretty staggering:
- What happened?
MangaDex received a takedown request that affected approximately 7,000 titles.
TIL about suwayomi. I just set it up now and it is interesting. Basically, it is like a hosted version of mihon that lives on a server (it uses the same extensions and can even import a backup from mihon). It works exactly like mihon and many of the menus/settings are exactly the same. Chapters are downloaded and the library is periodically updated exactly like in mihon. You could basically put this on something like a NAS at home and use it like a web version of mihon. Optionally, you can figure out the hosting side of things and have it live at a domain you own, like manga.yourdomain.com behind basic auth.
The most interesting part of hosting it on the web is that you can install a suwayomi extension in mihon on your mobile device. Then, your mobile device can browse your suwayomi library just like it does any other extension. Reading chapters on either your mobile device or on the suwayomi web ui will mark them as read. Additionally, it means that you can exclusively use the suwayomi extension on your mobile device and leave all the other extension management to the suwayomi install, migrating as needed when sources appear/disappear. All of that would be completely transparent to mihon because it is still just pointing to the same title on suwayomi.
I am going to be messing around with this. There are some rough edges I have run into. The main issue I am having is that chapter downloads are really slow and the web ui isn’t the most responsive at updating things like download percentages or library updates. I also couldn’t get flaresolverr to work. Disabling that part of the docker compose file got downloads working again (just slow).
Alright, updates to my experience with Suwayomi for those that might stumble upon this in the future. Turns out a lot of my problems were solvable.
The biggest fix I made was running it from SSD rather than straight from my HDD array. This fixed a lot of the slowness. My SSD cache drive on my NAS isn’t the biggest, so I was able to use docker volume mappings to stick the downloads folder onto the array while leaving the rest of the app files on the cache SSD. This has dramatically helped speed things up.
The other main thing that helped was enabling websockets in my reverse proxy. It turns out that the main reason the web ui was so unresponsive is that it heavily uses websockets to do things like update progress bars and the like. I have to deal with CGNAT, so it is a bit involved to set up (some extra lines in a couple nginx config files), so it isn’t something I do by default for each of my services. It helps dramatically with Suwayomi.
Since making these improvements, it has been much nicer to use.