mirror of
https://github.com/Mayuri-Chan/pyrofork.git
synced 2025-12-29 12:04:51 +00:00
Add FAQ about Pyrogram stability and reliability
This commit is contained in:
parent
93082ce894
commit
c8b4f3dac9
1 changed files with 16 additions and 0 deletions
|
|
@ -53,6 +53,22 @@ Why Pyrogram?
|
|||
|
||||
.. _TgCrypto: https://github.com/pyrogram/tgcrypto
|
||||
|
||||
How stable and reliable is Pyrogram?
|
||||
------------------------------------
|
||||
|
||||
So far, since its first public release, Pyrogram has always shown itself to be quite reliable in handling client-server
|
||||
interconnections and just as stable when keeping long running applications online. The only annoying issues faced are
|
||||
actually coming from Telegram servers internal errors and down times, from which Pyrogram is able to recover itself
|
||||
automatically.
|
||||
|
||||
To challenge the framework, the creator is constantly keeping a public
|
||||
`welcome bot <https://github.com/pyrogram/pyrogram/blob/develop/examples/welcomebot.py>`_ online 24/7 on his own,
|
||||
relatively-busy account for well over a year now.
|
||||
|
||||
In addition to that, about six months ago, one of the most popular Telegram bot has been rewritten
|
||||
:doc:`using Pyrogram <powered-by>` and is serving more than 200,000 Monthly Active Users since
|
||||
then, uninterruptedly and without any need for restarting it.
|
||||
|
||||
What can MTProto do more than the Bot API?
|
||||
------------------------------------------
|
||||
|
||||
|
|
|
|||
Loading…
Reference in a new issue