But, there is one nuance, which is very important. We will describe it briefly, for example, on the link we see "mk-MK", we need to change it to "mk-mk".
Why, you ask? The point is that the whole system transmits the original encoding in one kind of format, and then converts it into the one needed by Telegram itself. This format is exactly "mk-mk".
Conversion
The principle with registration is the same, conversion during registration - immediately a second session on other parameters is created (which you can also specify) or conversion via reauthorizer (json+session json+session).
The big advantage of conversion is that you can create a session on any parameters (TDesktop / unofficial parameters, etc.).
The only difference is in TDesktop, because the parameters there need to be slightly different, namely: