Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Feature Request: selectively download per server, or delete downloads from server #212

Open
SpongebobSquamirez opened this issue Feb 21, 2023 · 1 comment

Comments

@SpongebobSquamirez
Copy link

There are a couple servers I want the chats from, but whose attachments have completely bloated my database, taking up like half of the total downloads from across my servers (like 100-150GB).

If there were a way to exclude certain servers when starting an attachment download, and preferably a simple view of total downloads size per server (it can be text-based - I don't need graphs), ideally along with a way to remove downloads (perhaps to be redownloaded later - so just removing them from your device, not removing from your database the means to download them/the links b/t them and messages), that would be AMAAAZING.

Thank you for your continued service to the cause

@chylex
Copy link
Owner

chylex commented Feb 21, 2023

There's already a way to limit downloads by attachment size, so adding another filter by server could make sense.

Any sort of more advanced download management, like calculating size per server, deleting downloaded files, or marking them as not-for-download, can be done in any SQLite database viewer or editor, but there's no GUI for them in the app itself. It could be done, but I don't really enjoy programming DHT's GUI and don't want to spend time on it right now :P if someone more experienced wants to take a look at DHT's architecture and has some tips on how to improve the GUI and database model code, feel free to open a discussion.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants