hold shift or ctrl, highlight the entries that you do not want, and then click on any of the checkboxes you've highlighted...

I feel bad for you knowing you've been clicking 100s of times :(

Sure no problem. If the project was still actively maintained I'd submit a PR for the README, but it doesn't appear to be.

It still works, though. So hooray for that :)

LordAnimity wrote: ↑Tue Apr 16, 2024 3:07 pm
Thanks for this, sadly the program is 2 years old since it's last commit and doesn't support Deluge.

Literally says it supports Deluge on the documentation.

https://autoremove-torrents.readthedocs ... ed-clients

README is probably just outdated.

It's not a plugin, but it can do what you are describing and much more...

https://github.com/jerrymakesjelly/autoremove-torrents

I use it on a scheduled cron, and it works for me.

Your web instance is not connected to the RPC/deluge daemon. It is not "accepting" anything. It has no daemon to speak to...this is something we've seen before.

I don't have any personal experience with deluge-console. Sorry. @mhertz will be able to comment on that I'd expect.

This is an interesting thought, and I'm not entirely sure what, if any, consequences may come from this, as I'm not fully sure of the extent in which this is a necessary piece of the puzzle in some other aspect of Deluge or libtorrent. My first thought is that there _COULD_ be some reason that this ...

As an additional note, you have to edit the connection, you can't just use the prompt that happens when you connect.

You probably need to click on connection manager and connect it to the RPC daemon.

I'll PM you something that might help.

You are telling me that you think that Nord does not support port forwarding, but that your SOCKS5 circumvents their policy entirely? The RFC supports a very convoluted and historically unimplemented method for accepting connections, yes. I have yet to see any clients or SOCKS5 daemons implement thi...