diohub VS AriaNg

I've been using DioHub for a long time now and I love it, even though it hasn't been updated in who knows how long (actually just a year), the dev really just dropped a banger and left. That said, it's missing some features and it doesn't handle all link types, for example it's pretty annoying when I get an email notification for an issue and if I say to open it in-app, it just won't work because it doesn't understand links with the issue-comment specified (example). So if you want something just to browse and being able to perform some simple interactions, this app is great and buttery smooth, but if you need all the features you're better off using the official app and blocking the trackers.

Diohub is going to do that probably once it gets out of beta

The repository for the project can be found here: https://github.com/NamanShergill/diohub

if you use a rss reader,you can try [rsshub](rsshub.app/). for example,you can subscribe "https://github.com/mayswind/AriaNg/releases.atom" in your rss reader,when AriaNG is released,you will be noticed in your reader.

I'm using Aria2 on my server: https://aria2.github.io/ and add the GUI from here: https://github.com/mayswind/AriaNg/releases Actually this is working for a long time and I'm pretty happy with this combination...

Another one is AriaNG, pretty nice interface to your aria2 instance. You can export your configuration so you don't need to log-in on a new device every time. If you're using an Android phone, you can try Aria2App to control your download server remotely.

On your host machine (RPi, desktop, old laptop), you would need to run your services (paperless-ng, anything else you feel like, e.g. filebrowser, navidrome, Jellyfin, qBittorrent, Aria2Ng) which (best practice) is to serve to localhost/127.0.0.1 and then you use nginx to connect localhost:port to sensible addresses on LAN or a small homepage, which are then forwarded to your router, which is then connected to dyndns.