Jesse Chan

Flood has a documented, easy-to-use JSON API interface, normalizing the API of all clients supported by Flood. See https://github.com/jesec/flood#integrating-with-flood and https://flood-api.netlify.app/#tag/Torrents.

Totally agree. Weblate already has the feature: https://github.com/firewalld/firewalld/pull/697, https://github.com/Radarr/Radarr/commit/aafd82ba739541f1a48ba20c3bf13b7ffb8d94f6. Translators from the community are entitled to be properly recognized and attributed. Without such a feature, a human would be needed...

I don’t think `flood-git` is a supported package. Please follow the README and use supported channels. Try rolling build first.

Solution and VC project files are **not** difficult IMO. Actually I think they are quite simple. Check #331. It is also important to note that to include libass in other...

I am not able to reproduce the issue on the latest version of Flood. Try to upgrade to the latest version of Flood. If the issue is no longer relevant,...

Implemented in a93c4f6ebf64890cd40251be771774a87999183f. Feel free to close the issue if it is no longer relevant.

`/api/auth/authenticate` does not involve Transmission. It is authentication into Flood. Flood has its own user accounts and authentication. Did you type the wrong password?

I made the change to filter out stuff like `/var/snap/microk8s/common/run/containerd/cffbf286-d8b7-46f4-8088-9eb041f13bc1`. More often than not, those super long mount points are not useful, and the frontend has troubles with those.

It is unnecessarily complicated. I think a better option would be to simply use the paths of `--allowedpath`.

Flood 4.x adds torrents to rTorrent by local file path, which should resolve this issue. Please try the latest version. Feel free to close the issue if it is no...