2023-09-13 20:01:16 +03:00
|
|
|
Glossary
|
|
|
|
|
========
|
|
|
|
|
|
|
|
|
|
.. currentmodule:: telethon
|
|
|
|
|
|
|
|
|
|
.. glossary::
|
|
|
|
|
:sorted:
|
|
|
|
|
|
2024-03-18 20:55:23 +03:00
|
|
|
peer
|
2023-09-13 20:01:16 +03:00
|
|
|
A :class:`~types.User`, :class:`~types.Group` or :class:`~types.Channel`.
|
|
|
|
|
|
2024-03-18 20:55:23 +03:00
|
|
|
.. seealso:: The :doc:`../concepts/peers` concept.
|
2023-09-13 20:01:16 +03:00
|
|
|
|
2023-09-14 22:17:24 +03:00
|
|
|
yourself
|
|
|
|
|
The logged-in account, whether that represents a bot or a user with a phone number.
|
|
|
|
|
|
2023-09-13 20:01:16 +03:00
|
|
|
Raw API
|
|
|
|
|
Functions and types under ``telethon._tl`` that enable access to all of Telegram's API.
|
|
|
|
|
|
|
|
|
|
.. seealso:: The :doc:`../concepts/full-api` concept.
|
|
|
|
|
|
|
|
|
|
access hash
|
|
|
|
|
Account-bound integer tied to a specific resource.
|
|
|
|
|
Users, channels, photos and documents are all resources with an access hash.
|
|
|
|
|
The access hash doesn't change, but every account will see a different value for the same resource.
|
|
|
|
|
|
|
|
|
|
RPC
|
|
|
|
|
Remote Procedure Call.
|
|
|
|
|
Invoked when calling a :class:`Client` with a function from ``telethon._tl.functions``.
|
|
|
|
|
|
|
|
|
|
RPC Error
|
|
|
|
|
Error type returned by Telegram.
|
|
|
|
|
:class:`RpcError` contains an integer code similar to HTTP status codes and a name.
|
|
|
|
|
|
|
|
|
|
.. seealso:: The :doc:`../concepts/errors` concept.
|
|
|
|
|
|
|
|
|
|
session
|
|
|
|
|
Data used to securely connect to Telegram and other state related to the logged-in account.
|
|
|
|
|
|
|
|
|
|
.. seealso:: The :doc:`../concepts/sessions` concept.
|
|
|
|
|
|
|
|
|
|
MTProto
|
|
|
|
|
Mobile Transport Protocol used to interact with Telegram's API.
|
|
|
|
|
|
|
|
|
|
.. seealso:: The :doc:`../concepts/botapi-vs-mtproto` concept.
|
2023-09-16 20:13:00 +03:00
|
|
|
|
2023-10-01 14:37:28 +03:00
|
|
|
Bot API
|
2023-09-30 18:13:24 +03:00
|
|
|
HTTP Bot API
|
|
|
|
|
Telegram's simplified HTTP API to control bot accounts only.
|
|
|
|
|
|
|
|
|
|
.. seealso:: The :doc:`../concepts/botapi-vs-mtproto` concept.
|
|
|
|
|
|
2023-09-16 20:13:00 +03:00
|
|
|
login
|
|
|
|
|
Used to refer to the login process as a whole, as opposed to the action to :term:`sign in`.
|
|
|
|
|
The "login code" or "login token" get their name because they belong to the login process.
|
|
|
|
|
|
|
|
|
|
sign in
|
|
|
|
|
Used to refer to the action to sign into either a user or bot account, as opposed to the :term:`login` process.
|
|
|
|
|
Likewise, "sign out" is used to signify that the authorization should stop being valid.
|
|
|
|
|
|
|
|
|
|
layer
|
|
|
|
|
When Telegram releases new features, it does so by releasing a new "layer".
|
|
|
|
|
The different layers let Telegram know what a client is capable of and how it should respond to requests.
|
|
|
|
|
|
|
|
|
|
TL
|
|
|
|
|
Type Language
|
|
|
|
|
File format used by Telegram to define all the types and requests available in a :term:`layer`.
|
|
|
|
|
Telegram's site has an `Overview of the TL language <https://core.telegram.org/mtproto/TL>`_.
|
2023-10-08 16:07:18 +03:00
|
|
|
|
|
|
|
|
.. seealso:: :ref:`Type Language brief <tl-brief>`.
|
