In the rqbit web UI, the download interface offers a destination path which defaults to the download directory.

As a user, I try to keep an organization system - there is /home/rqbit/downloads/audio and /home/rqbit/downloads/other and /home/rqbit/downloads/video, and within these I have more subdirs for more specific filing.

When adding a torrent, I may not always know the exact folder I want to put it in, but I know there is some folder and I currently need to go look up my directory structure elsewhere.

I'm interested in adding support for "suggested directories" and a few other quality-of-life improvements around destinations, and wanted to check if these are worth pursuing to get them upstreamed here.

I started on an implementation in this branch that adds another API called dirPreview currently, and it returns the current destination and a few directories with it.

The UI is still a bit rough so I definitely have some work to do there, and I don't love the naming dirPreview for the API, but wanted to check and see what appetite there is for this change.