You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
For a long time, Telegram used 32-bit identifiers for users, groups and channels. After it became apparent that the available identifiers are running out, it switched to using 64-bit identifiers. Currently, all existing identifiers still fit into 32 bits, but this is not going to be the case for long.
Describe the solution you'd like
Telegram Web K should update its TL-schema to layer 133, which uses 64-bit identifiers.
Additional context Pavel Durov's post that announces the migration to 64-bit IDs.
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
For a long time, Telegram used 32-bit identifiers for users, groups and channels. After it became apparent that the available identifiers are running out, it switched to using 64-bit identifiers. Currently, all existing identifiers still fit into 32 bits, but this is not going to be the case for long.
Describe the solution you'd like
Telegram Web K should update its TL-schema to layer 133, which uses 64-bit identifiers.
Additional context
Pavel Durov's post that announces the migration to 64-bit IDs.
The text was updated successfully, but these errors were encountered: