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
{{ message }}
This repository has been archived by the owner on Apr 27, 2020. It is now read-only.
I'm getting a lot of 0 bytes *.jpg.downloading files when running TBJAVA lately, plus a FLOOD_5 error everytime I download a single piece of media.
Did they change something server-side?
TYIA
The text was updated successfully, but these errors were encountered:
Can confirm this occuring for me too, but also for mp4, pdf and ogg files.
Strangely enough, between consecutive runs of telegram_backup this behavior sometimes does not appear and not every file seems to trigger it but the failing ones will need to be redownloaded and keep triggering th FLOOD error.
I'd use the built-in Export function, but unlike this nice piece of software, it just redownloads everything everytime.
With ~9GB of stuff, it's annoying.
Hello,
an idea here: could tgbackup download medias starting from the end?
Like check for presence in order, put missing files in a list, then download medias starting by the end of that list.
I've been trying to archive an account for days and so far I've only retrieved 5 files, the flood error appear from the first media, even after 1d or pause, even when continuously restarting tgbackup :/
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
I'm getting a lot of 0 bytes *.jpg.downloading files when running TBJAVA lately, plus a FLOOD_5 error everytime I download a single piece of media.
Did they change something server-side?
TYIA
The text was updated successfully, but these errors were encountered: