mir/pyrogram
2
0
Fork 0
mirror of https://github.com/pyrogram/pyrogram synced 2025-08-31 06:16:06 +00:00
Code Issues Releases Wiki Activity

Many minor documentation enhancements

Browse Source
This commit is contained in:
Dan
2019-06-27 23:16:21 +02:00
parent 9f231bb880
commit b6f508711a
9 changed files with 19 additions and 16 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
docs/source/topics/storage-engines.rst
View File

@@ -95,5 +95,5 @@ engine to properly work as intended.
But, why is the session string so long? Can't it be shorter? No, it can't. The session string already packs the bare
minimum data Pyrogram needs to successfully reconnect to an authorized session, and the 2048-bits auth key is the major
contributor to the overall length. Needless to repeat that this string, as well as any other session storage, represent
contributor to the overall length. Needless to say that this string, as well as any other session storage, represent
strictly personal data. Keep them safe.

4
docs/source/topics/use-filters.rst
View File

@@ -1,8 +1,8 @@
Using Filters
=============
So far we've seen how to register a callback function that executes every time a specific update comes from the server,
but there's much more than that to come.
So far we've seen :doc:`how to register a callback function <../start/updates>` that executes every time a specific update
comes from the server, but there's much more than that to come.
Here we'll discuss about :class:`~pyrogram.Filters`. Filters enable a fine-grain control over what kind of
updates are allowed or not to be passed in your callback functions, based on their inner details.