mirror of
https://github.com/Mayuri-Chan/pyrofork.git
synced 2026-01-10 00:24:51 +00:00
Update Bot API diagram in docs
This commit is contained in:
parent
e30b9c5255
commit
b4467e82af
2 changed files with 2 additions and 2 deletions
|
|
@ -85,7 +85,7 @@ Requests against the official bot API endpoint are made via JSON/HTTP, but are h
|
||||||
application that implements the MTProto protocol -- just like Pyrogram -- and uses its own API key, which is always
|
application that implements the MTProto protocol -- just like Pyrogram -- and uses its own API key, which is always
|
||||||
required, but hidden to the public.
|
required, but hidden to the public.
|
||||||
|
|
||||||
.. figure:: https://i.imgur.com/C108qkX.png
|
.. figure:: https://i.imgur.com/WvwBoZo.png
|
||||||
:align: center
|
:align: center
|
||||||
|
|
||||||
Using MTProto is the only way to communicate with the actual Telegram servers, and the main API requires developers to
|
Using MTProto is the only way to communicate with the actual Telegram servers, and the main API requires developers to
|
||||||
|
|
|
||||||
|
|
@ -35,7 +35,7 @@ accounts that are authorized via tokens instead of phone numbers. The Bot API is
|
||||||
Telegram API, but runs on an intermediate server application that in turn communicates with the actual Telegram servers
|
Telegram API, but runs on an intermediate server application that in turn communicates with the actual Telegram servers
|
||||||
using MTProto.
|
using MTProto.
|
||||||
|
|
||||||
.. figure:: https://i.imgur.com/C108qkX.png
|
.. figure:: https://i.imgur.com/WvwBoZo.png
|
||||||
:align: center
|
:align: center
|
||||||
|
|
||||||
.. _Bot API: https://core.telegram.org/bots/api
|
.. _Bot API: https://core.telegram.org/bots/api
|
||||||
|
|
|
||||||
Loading…
Reference in a new issue