flood VS paperless-ngx

Why bake libtransmission into the app instead of just using the transmission daemon's RPC?

What you've done actually makes it harder to use, because in order to configure any of transmission's settings (ports, connection/torrent connection limits, bandwith limits, etc) the user needs to dig around to find the transmission config folder and then manually edit JSON with a text editor - because your client doesn't expose any of transmissions numerous settings [1] to the user except for choosing the download folder.

I'm not sure why anyone would want to use this instead of Flood [2] or even old Transmission Web Control [3]

1: https://github.com/transmission/transmission/blob/main/docs/...

1: https://github.com/jesec/flood

2: https://github.com/ronggang/transmission-web-control

Only one that I'm aware of is Flood: https://github.com/jesec/flood

If you haven't seen the https://flood.js.org project before. It has subjectively a nicer ui and works with qbittorent.

You can install alternate web UIs very easy. I’m a big fan of Flood, which is mobile friendly: https://flood.js.org/

One note: I lean heavily on an API to manage it so I'd love to continue using flood, I tested qbittorrent with it briefly and it didn't go well.

You mean a torrent client? I’m using rTorrent with Flood (the new jesec fork that’s actually active) and it works brilliantly on mobile

https://flood.js.org/ ?

If it's just the web ui you're worried about perhaps look into installing Flood & see if it helps? It's going to be a better web ui overall. (I've never needed to use it personally but it's been recommended in the pat)

qbitorrent-nox with flood-ui

Impressive. But I dont get why they would rebuild the web client when there are existing options like: https://github.com/jesec/flood

I steered a friend towards Paperless (and away from an LLM solution) as a way of searching/accessing GBs of architectural PDFs recently - so far, it’s apparently working well for them.

https://github.com/paperless-ngx/paperless-ngx

Paperless-ngx is a document management system that transforms your physical documents into a searchable online archive so you can find your physical documents easier. With features such as tags, full text search, multi-user permissions system, this is a dream for those who like to keep an organized folder of files and documents.

Since last year I’ve been configuring and maintaining my homelab setup and it is just amazing.

I’ve learned so much about containers, virtual machines and networking. Some of the self hosted applications like paperless-ngx [1] and immich [2] are much superior in terms of features than the proprietary cloud solutions.

With the addition of VPN services like tailscale [3] now I can access my homelab from anywhere in the world.

The only thing missing is to setup a low powered machine like NUC or any mini PC so I can offload the services I need 24/7 and save electricity costs.

If you can maintain it and have enough energy on weekends to perform routine maintenance and upgrades. I would 100% recommend setting up your own homelab.

[1] https://docs.paperless-ngx.com/

This has been posted a few times already, but I cannot tell you how life changing Paperless NGX is for organizing PDFs. As someone who wrangles all of the insurance and bills for my house, this open source software is so damn good.

https://docs.paperless-ngx.com/

I maintain Bash script to quickly set it up locally on Linux with Podman. Give it a spin if you want to kick the tires.

https://github.com/jdoss/ppngx

Personally, I use https://github.com/joeyates/imap-backup to archive all my emails and then only keep them on the remote server for as long as I need to (basically until I read them and respond or download an attachment into https://docs.paperless-ngx.com )