telegram-upload
Telegram-upload uses your personal Telegram account to upload and download files up to 2GiB (bots are limited to 50 MiB). Turn Telegram into your personal cloud!
To install telegram-upload, run this command in your terminal:
$ sudo pip3 install -U telegram-upload
This is the preferred method to install telegram-upload, as it will always install the most recent stable release. More info in the documentation
To use this program you need an Telegram account and your App api_id/api_hash (get it in my.telegram.org). The first time you use telegram-upload it requests your telephone, api_id and api_hash. Bot tokens can not be used with this program (bot uploads are limited to 50MB). To send files (by default it is uploaded to saved messages):
$ telegram-upload file1.mp4 /path/to/file2.mkv
Credentials are saved in ~/.config/telegram-upload.json and ~/.config/telegram-upload.session. You must make sure that these files are secured. You can copy these files to authenticate telegram-upload on more machines, but it is advisable to create a session file for each machine. Upload options are available in the documentation.
You can download the files again from your saved messages (by default) or from a channel. All files will be downloaded until the last text message.
$ telegram-download
The --delete-on-success option allows you to delete the Telegram message after downloading the file. This is useful to send files to download to your saved messages and avoid downloading them again. You can use this option to download files on your computer away from home.
Read the documentation for more info.
Interactive mode
The interactive option (--interactive) allows you to choose the dialog and the files to download or upload with a terminal wizard. It even supports mouse!
$ telegram-upload --interactive # Interactive upload
$ telegram-download --interactive # Interactive download
Features
Upload multiples files (up to 2GiB per file)
Download files.
Add video thumbs.
Delete local or remote file on success.
… And more.
Docker
Run telegram-upload without installing it on your system using Docker. Instead of telegram-upload and telegram-download you should use upload and download. Usage:
docker run -v <files_dir>:/files/
-v <config_dir>:/config
-it nekmo/telegram-upload:master
<command> <args>
<files_dir>: upload or download directory.
<config_dir>: Directory that will be created to store the telegram-upload configuration. It is created automatically.
<command>: upload and download.
<args>: telegram-upload and telegram-download arguments.
For example:
docker run -v /media/data/:/files/
-v $PWD/config:/config
-it nekmo/telegram-upload:master
upload file_to_upload.txt
Metadata
Release files for telegram-upload 0.6.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| telegram-upload-0.6.1.tar.gz | 90.2 kB | Without provenance | Details for telegram-upload-0.6.1.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| telegram_upload-0.6.1-py2.py3-none-any.whl | Python 3, Python 2 | none | any | Details for telegram_upload-0.6.1-py2.py3-none-any.whl |
Total release size: 119.2 kB
Release files / telegram-upload-0.6.1.tar.gz
| Download URL | telegram-upload-0.6.1.tar.gz |
|---|---|
| Size | 90.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
0e24aa3eb8369a3f64a6ba1e87599c25121d29a8732cb5ce5894b92d5ec93d2b
|
|
BLAKE2b-256 checksum How to use checksums |
77953cd548e4da45f4ea18adf119b001582333947eafee54236e90716b230f1d
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.9.17
|
Release files / telegram_upload-0.6.1-py2.py3-none-any.whl
| Download URL | telegram_upload-0.6.1-py2.py3-none-any.whl |
|---|---|
| Size | 29.0 kB |
| Tags | Python 2 Python 3 |
|
SHA-256 checksum How to use checksums |
594d203da861b2dc0b15c1c257f8adf36934dc01942294c3068b4775bdac9b7b
|
|
BLAKE2b-256 checksum How to use checksums |
82c313511d5cbb13a6945bb73d5d1bc429fc329200283cc7cbd51ee343e08282
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.9.17
|
Security for telegram-upload 0.6.1
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.