From c8b4f3dac9b6c23cdb9814150c44c82120b54863 Mon Sep 17 00:00:00 2001 From: Dan <14043624+delivrance@users.noreply.github.com> Date: Wed, 12 Jun 2019 14:05:59 +0200 Subject: [PATCH] Add FAQ about Pyrogram stability and reliability --- docs/source/faq.rst | 16 ++++++++++++++++ 1 file changed, 16 insertions(+) diff --git a/docs/source/faq.rst b/docs/source/faq.rst index f08da03f..0d56451a 100644 --- a/docs/source/faq.rst +++ b/docs/source/faq.rst @@ -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 `_ 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 ` 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? ------------------------------------------