You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I would like to approve integrating autobrr into ruTorrent, once we start development of version 6. It is the modern replacement for autodl-irrsi, which many people used when it was supported. My vision for ruTorrent v6 is to have a single unified interface for modern tools like the arr suite. Their API docs are located here which returns a JSON response we can easily parse: https://autobrr.com/api
It's required to use curl (which we already support). The recommended implementation is to ask the user for their API key in the settings menu (on the developers tab), then save it to autobrr.dat. We can add a autobrr submenu to the plugin menu on the navigation bar. A custom plugin would need to be created, which the user can enable/disable.
Opening the autobrr menu would allow the user to:
List all filters from the autobrr instance.
Add new filters to the autobrr instance.
Update existing filters on the autobrr instance.
Delete existing filters from the autobrr instance.
There are more features on autobrr. If we start with this simple implementation, it would greatly improve the time and success of the project. We can build onto the implementation afterwards with abstraction layers, in the form of multiple successful pull requests.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
I would like to approve integrating autobrr into ruTorrent, once we start development of version 6. It is the modern replacement for
autodl-irrsi
, which many people used when it was supported. My vision for ruTorrentv6
is to have a single unified interface for modern tools like thearr
suite. Their API docs are located here which returns a JSON response we can easily parse: https://autobrr.com/apiIt's required to use
curl
(which we already support). The recommended implementation is to ask the user for their API key in the settings menu (on the developers tab), then save it toautobrr.dat
. We can add a autobrr submenu to the plugin menu on the navigation bar. A custom plugin would need to be created, which the user can enable/disable.Opening the autobrr menu would allow the user to:
There are more features on autobrr. If we start with this simple implementation, it would greatly improve the time and success of the project. We can build onto the implementation afterwards with abstraction layers, in the form of multiple successful pull requests.
Beta Was this translation helpful? Give feedback.
All reactions