mirror of
https://github.com/LonamiWebs/Telethon.git
synced 2024-11-10 19:46:36 +03:00
67 lines
5.6 KiB
Plaintext
67 lines
5.6 KiB
Plaintext
# These are comments. Spaces around the = are optional. Empty lines ignored.
|
|
#CODE=Human readable description
|
|
|
|
FILE_MIGRATE_X=The file to be accessed is currently stored in DC {}
|
|
PHONE_MIGRATE_X=The phone number a user is trying to use for authorization is associated with DC {}
|
|
NETWORK_MIGRATE_X=The source IP address is associated with DC {}
|
|
USER_MIGRATE_X=The user whose identity is being used to execute queries is associated with DC {}
|
|
API_ID_INVALID=The api_id/api_hash combination is invalid
|
|
BOT_METHOD_INVALID=The API access for bot users is restricted. The method you tried to invoke cannot be executed as a bot
|
|
CDN_METHOD_INVALID=This method cannot be invoked on a CDN server. Refer to https://core.telegram.org/cdn#schema for available methods
|
|
CHANNEL_INVALID=Invalid channel object. Make sure to pass the right types, for instance making sure that the request is designed for channels or otherwise look for a different one more suited
|
|
CHANNEL_PRIVATE=The channel specified is private and you lack permission to access it. Another reason may be that you were banned from it
|
|
CHAT_ADMIN_REQUIRED=Chat admin privileges are required to do that in the specified chat (for example, to send a message in a channel which is not yours)
|
|
CHAT_ID_INVALID=Invalid object ID for a chat. Make sure to pass the right types, for instance making sure that the request is designed for chats (not channels/megagroups) or otherwise look for a different one more suited\nAn example working with a megagroup and AddChatUserRequest, it will fail because megagroups are channels. Use InviteToChannelRequest instead
|
|
CONNECTION_LANG_PACK_INVALID=The specified language pack is not valid. This is meant to be used by official applications only so far, leave it empty
|
|
CONNECTION_LAYER_INVALID=The very first request must always be InvokeWithLayerRequest
|
|
DC_ID_INVALID=This occurs when an authorization is tried to be exported for the same data center one is currently connected to
|
|
FIELD_NAME_EMPTY=The field with the name FIELD_NAME is missing
|
|
FIELD_NAME_INVALID=The field with the name FIELD_NAME is invalid
|
|
FILE_PARTS_INVALID=The number of file parts is invalid
|
|
FILE_PART_X_MISSING=Part {} of the file is missing from storage
|
|
FILE_PART_INVALID=The file part number is invalid
|
|
FIRSTNAME_INVALID=The first name is invalid
|
|
INPUT_METHOD_INVALID=The invoked method does not exist anymore or has never existed
|
|
INPUT_REQUEST_TOO_LONG=The input request was too long. This may be a bug in the library as it can occur when serializing more bytes than it should (likeappending the vector constructor code at the end of a message)
|
|
LASTNAME_INVALID=The last name is invalid
|
|
LIMIT_INVALID=An invalid limit was provided. See https://core.telegram.org/api/files#downloading-files
|
|
LOCATION_INVALID=The location given for a file was invalid. See https://core.telegram.org/api/files#downloading-files
|
|
MD5_CHECKSUM_INVALID=The MD5 check-sums do not match
|
|
MESSAGE_EMPTY=Empty or invalid UTF-8 message was sent
|
|
MESSAGE_ID_INVALID=The specified message ID is invalid
|
|
MESSAGE_TOO_LONG=Message was too long. Current maximum length is 4096 UTF-8 characters
|
|
MESSAGE_NOT_MODIFIED=Content of the message was not modified
|
|
MSG_WAIT_FAILED=A waiting call returned an error
|
|
OFFSET_INVALID=The given offset was invalid, it must be divisible by 1KB. See https://core.telegram.org/api/files#downloading-files
|
|
PASSWORD_HASH_INVALID=The password (and thus its hash value) you entered is invalid
|
|
PEER_ID_INVALID=An invalid Peer was used. Make sure to pass the right peer type
|
|
PHONE_CODE_EMPTY=The phone code is missing
|
|
PHONE_CODE_EXPIRED=The confirmation code has expired
|
|
PHONE_CODE_HASH_EMPTY=The phone code hash is missing
|
|
PHONE_CODE_INVALID=The phone code entered was invalid
|
|
PHONE_NUMBER_BANNED=The used phone number has been banned from Telegram and cannot be used anymore. Maybe check https://www.telegram.org/faq_spam
|
|
PHONE_NUMBER_INVALID=The phone number is invalid
|
|
PHONE_NUMBER_OCCUPIED=The phone number is already in use
|
|
PHONE_NUMBER_UNOCCUPIED=The phone number is not yet being used
|
|
PHOTO_INVALID_DIMENSIONS=The photo dimensions are invalid
|
|
TYPE_CONSTRUCTOR_INVALID=The type constructor is invalid
|
|
USERNAME_INVALID=Nobody is using this username, or the username is unacceptable. If the latter, it must match r"[a-zA-Z][\w\d]{3,30}[a-zA-Z\d]"
|
|
USERNAME_NOT_MODIFIED=The username is not different from the current username
|
|
USERNAME_NOT_OCCUPIED=The username is not in use by anyone else yet
|
|
USERNAME_OCCUPIED=The username is already taken
|
|
USERS_TOO_FEW=Not enough users (to create a chat, for example)
|
|
USERS_TOO_MUCH=The maximum number of users has been exceeded (to create a chat, for example)
|
|
USER_ID_INVALID=Invalid object ID for an user. Make sure to pass the right types, for instance making sure that the request is designed for users or otherwise look for a different one more suited
|
|
ACTIVE_USER_REQUIRED=The method is only available to already activated users
|
|
AUTH_KEY_INVALID=The key is invalid
|
|
AUTH_KEY_PERM_EMPTY=The method is unavailable for temporary authorization key, not bound to permanent
|
|
AUTH_KEY_UNREGISTERED=The key is not registered in the system
|
|
INVITE_HASH_EXPIRED=The chat the user tried to join has expired and is not valid anymore
|
|
SESSION_EXPIRED=The authorization has expired
|
|
SESSION_PASSWORD_NEEDED=Two-steps verification is enabled and a password is required
|
|
SESSION_REVOKED=The authorization has been invalidated, because of the user terminating all sessions
|
|
USER_ALREADY_PARTICIPANT=The authenticated user is already a participant of the chat
|
|
USER_DEACTIVATED=The user has been deleted/deactivated
|
|
FLOOD_WAIT_X=A wait of {} seconds is required
|
|
FLOOD_TEST_PHONE_WAIT_X=A wait of {} seconds is required in the test servers
|