A forwarded batch used to lose everything after the first file — the flood guard quietly ate the rest. The bot now treats a batch as a batch and answers in a single conversation.
The bot waits for the stream of files to go quiet and takes everything in one pass: one album, three albums of ten, or thirty separate forwards — it makes no difference.
The flood guard no longer touches files. It was meant to stop chatter but hit forwarding instead; the upload queue handles the load on its own.
One answer comes back: a counter, «Uploading 12/30», then the list of links. Too many for one message — the rest follow in the next one, and none go missing.
The daily limit no longer rejects a whole batch because of one file too many: whatever fits goes up, and the bot names the rest.
Without a connected cloud a file now lives a week instead of a month — and in exchange the storage accepts everything Telegram is willing to hand over.
The server used to refuse anything heavier than a couple of megabytes while the person read «storage unavailable». The ceiling is now 20 MB, and when a file still does not fit, the bot states the real reason.
Expired files are swept on a schedule rather than by somebody else’s random upload: a week means a week.
A dropped connection no longer kills an upload — the bot quietly tries again.
Need it kept for good? /connect: in your own cloud the link lives until you delete it yourself.
Russian, English, German, Spanish and Arabic — with the writing direction it deserves. The language picks itself: your choice first, then the browser, and only then the country.
A choice in the switcher is remembered for a year, so you only switch once.
The Arabic version is not a mirror image but its own layout: RTL, its own typeface, its own spacing.
The country comes from a range database built into the site, with no calls to anyone else’s service.
The cloud sign-in page moved to the site as well: the bot needs neither a domain of its own nor a public IP.
Forward a file to the bot — it puts the file into your Google Drive or Yandex Disk and answers with a download link. Not onto some shared service drive: into your account.
One /connect per cloud: the provider’s consent page, about forty seconds — after that there is only forwarding.
In Google Drive the bot works in drive.file mode and can physically see nothing but what it put there itself. On Yandex Disk it keeps to its own folder.
/my lists recent uploads with a «Delete» button: the file leaves the cloud and the link stops opening.
Tokens are stored encrypted and refresh themselves. You can revoke access at any moment — the files stay with you.