retry failed/cancelled download about archivebot HOT 11 CLOSED

Did you do /allow_duplicates@username true?
Try /info@username to see the current settings for a chat

from archivebot.

I didn't do (I miss the @username part on the commands) but I did just now. Still seems to not to download already downloaded files.

Current settings:

Name: 19338....
Active: True
Accepted Media: document
Verbose: True
Allow duplicates: True
Sort files by User: True

from archivebot.

Allow duplicates is basically a flag, which enable downloading of files that have the same download.
If you want to download files that actually failed to download, you need to start a /scan_chat
This will go through the whole chat history and download files (if they haven't been downloaded yet)

from archivebot.

I have this on my history chat

But it doesn't donwload anything

I'm on my own chat (Saved Messages), can be this perhaps? (I don't know if/how I can download to a bot). I cannot see either a verbosed ouput nor in the chat neither in the command line output

from archivebot.

That's because this is probably a photo.
As you can see, your accepted media is set to documents, which only includes file uploads.
Type /accept@user document photo

It's obvious, that some things in the current documentation are unclear. It would be awesome, if you could adjust the documentation text, remove any uncertainties and create a PR :)

from archivebot.

Verbose:
This is from the docs:
/verbose ['true', 'false'] The bot will complain if there are duplicate files or uncompressed images are sent, whilst not being accepted.

from archivebot.

Just tested the verbose output. Seems to be silently ignored.
Feel free to debug and create a PR :) Shouldn't be too hard, the code base is pretty straight forward.

from archivebot.

That's because this is probably a photo.
As you can see, your accepted media is set to documents, which only includes file uploads.
Type /accept@user document photo

It's obvious, that some things in the current documentation are unclear. It would be awesome, if you could adjust the documentation text, remove any uncertainties and create a PR :)

Still doesn't work, and as verbose tells nothing, it's quite hard to know what's happening.
I can PR the changes to de documentation to be a bit more clear, and perhaps after the tests, if I can create a systemd unit file to autostart the bot on boot.

Just tested the verbose output. Seems to be silently ignored.
Feel free to debug and create a PR :) Shouldn't be too hard, the code base is pretty straight forward.

I can't take a look, yet I do not know anything about telegram bots, to see at least why verbose isn't working.

from archivebot.

A few lines in the documention would be very much appreciated, though ;)

from archivebot.

The /clear_history@username did the trick.
I'm gonna PR some suggestions to the README, so command won't be ambiguous.

from archivebot.

Nice. Thanks a lot! 👍

from archivebot.