I've also added some features to the API (see https://github.com/pwrtelegram/pwrtelegram).

As usual feel free to suggest new features by writing to @pwrtelegramgroup and debug existing ones using the main (api.pwrtelegram.xyz) or the beta (beta.pwrtelegram.xyz) API endpoints or the official @pwrtelegrambot.
If you find a bug create an issue in the github repository (or even better submit a pull request with a fix) or write to @pwrtelegramgroup or to @danogentili (in case of security issues).

P.S. Thanks to @spteit for linking to this channel.

Thanks to @bothosting for hosting the PWRTelegram API and for featuring us on their channel!

Today the biggest update of the @pwrtelegram bot API is released!

Here are the features of the PWRTelegram API:
- All of the official telegram bot API features plus:
- Downloading of files up to 1.5 GB in size
- Anonymous file storage (the URL of downloaded files does not contain your bot's token)
- Uploading of files up to 1.5 GB in size
- Uploading of files using an URL
- Reuploading of files using a file ID and different file type or file name.
- Uploading of any file/URL/file ID with automagical type recognition.
- Uploading of any file/URL/file ID without sending the file to a specific user.
- Automagical metadata recognition of sent files/URLs/file IDs.
- Deleting of text messages sent from the bot
- Uploading of files bigger than 5 megabytes with inline queries (supports both URLs and direct uploads)
- Automatical type recognition for files sent using answerinlinequery
- Both webhooks and getupdates are supported.
- webhook requests can be recieved even on insecure http servers.
- It is open source!
- It can be installed on your own server!
- You tell me!

This API is written and maintained by danog (@danogentili on telegram) with the help of the folks over @BotDevelopment, especially itskenny0 (@shitposting on telegram) and Rondoozle (@POTUS on Telegram).

It is hosted and promoted by the awesome Bothosting.

The new PWRTelegram logo was created by @BayernPars.

To use it simply subsitute the url of the bot telegram api (https://api.telegram.org) with the url of the pwrtelegram api (https://api.pwrtelegram.xyz) in your telegram client.

You can use this command to do it:
sed -i 's/api\.telegram\.org/api\.pwrtelegram\.xyz/g' client.py

All clients are supported, not just python clients.

Visit https://pwrtelegram.xyz for the full documentation!

There are lots of new features cooking such as the joining of groups using invite links (or in certain cases even the username of the group), the resolving of any username to user ids and much more!

You can help by doing the following things:
- Suggesting new features or reporting bugs by opening a new issue or contributing directly with pull requests @ the repos of the pwrtelegram github organization.
- Peer reviewing the source code of the API.
- Subscribing to the official pwrtelegram channel.
- Subscribing to the @BotHosting channel.
- Joining the official pwrtelegram development group.
- Following the official pwrtelegram twitter account
- Starring the repos of the pwrtelegram github organization.
- Sharing this message with all of your friends, your groups and forwarding it to your channels!

Thanks for nearly 120 members!
To help even more bot developers share this channel on your groups, channels and bots!
:)

I've set up load balancing on the main API endpoint (api.pwrtelegram.xyz).
This should speed up requests.

I've seen a lot of people intrested in my API, but most were reluctant to implement it in their bots because they were afraid of it stealing or leaking their token.

Well, I got good news for you: the @pwrtelegram API never stores your bot's token in any database or file, neither in plain text nor as a hash.
There is no way I can see your bot's token.

If you're still worried about security breaches or if you're just being paranoid (good for you), you can take a look at the source code of the API (https://github.com/pwrtelegram) to confirm my words or even install it on your own server with https://github.com/pwrtelegram-backend

If you encounter problems while installing or using the API don't hesitate and write to @pwrtelegramgroup!

A tutti gli italiani che sono iscritti a questo canale: vi invito a iscrivervi e a condividere la versione italiana di questo canale, @pwrtelegramita, e a unirvi al gruppo di supporto italiano, @pwrtelegramgroupita.
To all the italians in this channel: please subscribe and share the italian version of this channel, @pwrtelegramita, and join the italian support group, @pwrtelegramgroupita.

P.S. Thanks for 132 members! :)

If you are encountering problems while sending big files trough the API please note that this API won't be able to send big files if getUpdate or webhook requests aren't proxied through it. This is because when the API uploads these files using tg-cli it must then obtain a file_id using the official bot API, and that can be done only by intercepting the incoming update with the file.

I recommend using webhooks instead of long polling with the PWRTelegram API.
Long polling requests tend to overload my servers 😁

I've just implemented the resolving of usernames in the @pwrtelegram API.
Thanks to this feature you will be able to use not only usernames of channels and groups, but also usernames of bots and normal users in the chat_id parameter.
This also means that you will be able to get info about any user or bot using the getChat method.

🔨 1 new commits to pwrtelegram:master:

c48a564: Cleaned up and optimized code, made getchat work even if user has never contacted the bot or if the user in question is a bot. by Daniil Gentili

Hey guys! If you feel that some features are missing feel free to create feature requests @ https://github.com/pwrtelegram/pwrtelegram/issues

Hey guys!
I want you to know that I'm sorry for the recent problems with the API, everything should work now.
I also want to let you know that I'm working on an enormous update for the API that will speed it up and simplify a lot of tasks!

Here are some news regarding the upcoming update of the API:
I've just finished writing a PHP implementation of python's struct module (https://docs.python.org/3/library/struct.html) called PHPStruct: https://github.com/danog/PHPStruct
This library can be used to pack/unpack strings, ints, floats, chars and bools into bytes.
It has lots of advantages over PHP's native implementation of pack and unpack, such as:
- Custom byte endianness.
- Lots of useful formats that aren't present in the native implementation.
- The syntax of the format string of pack and unpack is the same as in python's struct module.
- The result of unpack is normal numerically indexed array that starts from 0 like it should.
- The result of unpack has type casted values (int for integer formats, bool for boolean formats, float for float formats and string for all of the other formats).
- Pack is more strict about the type of input formats.
- The calcsize function is implemented.

For more info visit the official github repo of the library: https://github.com/danog/PHPStruct (do not forget to star it!).
And the documentation of the struct module: https://docs.python.org/3/library/struct.html

This library will be used in a PHP implementation of mtproto that I will integrate into the API: https://github.com/danog/MadelineProto

Share this message with your friends!

Hello.
Please reset the webhooks of all of your bots, because they were all reset by the telegram bot API.
This request applies both to bots that use the official bot API and bots that use the PWRTelegram bot API. You do not need to reset the webhook if you are using long polling (getUpdates).
The webhooks were probably reset because Telegram's making some server side changes or simply messed up the webhook database.

Share this message around to all of your groups and channels, please.

Hello.
The PWRTelegram API is now hosted on a shiny new vps with blazing fast network connection and high end specs.
Enjoy the speed.

Hello.
I just wanted you to know that I am developing a PHP client for the telegram MTProto protocol.
I have managed to implement TL serialization/deserialization, tcp abridged/full connections and partial support for tcp intermediate connections.
I have also successfully implemented a method_call function that can be used to call mtproto methods, a prime generation module based on Python or wolfram alpha and I am currently trying to make the generation of the authorization key to work.
Once I finish writing it I will be able to implement it into the PWRTelegram API.

But since this is a very big project, I would really appreciate your help with it: if we all collaborate MadelineProto will be completed a lot sooner and the PWRTelegram API will have a lot more features.

To contribute, check out the TODO list in the readme of the repo: https://github.com/danog/MadelineProto
Choose an objective from the todo list, fork the repo, make the needed changes and submit a pull request.
I will accept it as fast as possible.
If you want to discuss about the code you can also open an issue.

I'm eagerly awaiting contributors :)

Share this message around to all of your groups and channels and to people that might want to help, please.