Signed out of my account on all my devices

[Mostalk]

Checklist

• The error is in the library's code, and not in my own.
• I have searched for this issue before posting it and there isn't a duplicate.
• I ran pip install -U https://github.com/LonamiWebs/Telethon/archive/v1.zip and triggered the bug in the latest version.

Code that causes the issue

from telethon.sync import TelegramClient
with TelegramClient("main", 123456, "token") as client:
    for message in client.iter_messages("https://t.me/channel"):
        if message.text:
            print(message.text")

I ran this code three times and each time it logged out all my devices from my phone, computer and telethon session. As a result, I was given a ban for 24 HOURS in any attempt to enter my telegram account. Thanks a lot. I will be without work and communication for a day....

[Lonami]

Thanks a lot

Thinking Telethon is intentionally telling Telegram to ban its users would be silly. The library wouldn't be as used nearly as much if that was the case.

You don't have to take my word for it though, if this is something you particularly care about, please by all means audit the library. To the best of my knowledge, Telethon doesn't do anything which would clearly direct to a ban. But maybe I'm wrong.

Regardless, this is even explained in the FAQ - My account was deleted/limited when using the library (permalink). So it's not like I'm trying to hide it.

Anyway, I'll be closing this as it's not really something actionable from my side (unless your audit brings up results). Telethon is unfortunately abused by many spammers, so it is very likely Telegram has learned to pick up on patterns to detect this library, and be more willing to hand out bans. See #824 for more resources.

[Belousov-Aleksandr]

When i use any telethon-metod, this leads to the same results. Disconnect from all device. After launching the TelegramClient, only the first method of the code is triggered, then the account is disconnected...

[Mostalk]

When i use any telethon-metod, this leads to the same results. Disconnect from all device. After launching the TelegramClient, only the first method of the code is triggered, then the account is disconnected...

I tried with VPN and different accounts - same, any use of telethon disconnect from all device. I had to temporarily switch to another library, I hope this problem will be fixed

[Belousov-Aleksandr]

When i use any telethon-metod, this leads to the same results. Disconnect from all device. After launching the TelegramClient, only the first method of the code is triggered, then the account is disconnected...

I tried with VPN and different accounts - same, any use of telethon disconnect from all device. I had to temporarily switch to another library, I hope this problem will be fixed

pyrogram...it works without failures and problems.

[Lonami]

The most likely unfortunate reason is that Telethon has been abused by many spammers in the past, and so Telegram has learnt some way to detect Telethon, and is more likely to ban or restrict accounts. I really don't think there's anything that can be done. Even if it was somehow "fixed", the library would be abused yet again and lead to the same problems.

[Belousov-Aleksandr]

May be need change "user-agent" string with name Telethon-library? ))

[Lonami]

You can try to configure the parameters used to initialize the connection in the TelegramClient constructor as documented. However there isn't really much point in me to try and "fix" that for everyone. Others will abuse it, and it will be caught again.

[viatcheslavmogilevsky]

The same happened yesterday, so I've subscribed to this issue.

I'm trying to use Telethon to automate backups my own scheduled messages - there is no "Export chat history" button for scheduled messages yet, so I ended up using my own script on top of Telethon.

Life would be more easier if Telegram devs add "claims" to App configuration, besides api_id, app_hash and titles, like: "messages:read-only:me" - which will indicate that app is only supposed to read owner's messages, no more - so definitely it is not for spam.

Thanks for the library, anyway.

[Lonami]

I appreciate the kind words and sympathize with those affected. It really sucks when your library essentially can't be used because Telegram decided so. With that said, I'd like to point out, this problem is not exclusive to Telethon, as demonstrated by https://github.com/pyrogram/pyrogram/issues/1236.

[Belousov-Aleksandr]

However, a solution to this problem has been found. Who is interested - ask me. Solution absolutely not obvious...

[Lonami]

This is a good time to remind everyone experiencing this issue to be wary of scams and people trying to sell solutions. The decision is always on Telegram. I'm sure people will find a way to delay this error. But do think twice before buying solutions.

[yourPersonalAccount-bot]

However, a solution to this problem has been found. Who is interested - ask me. Solution absolutely not obvious...

So what's the solution?

[Belousov-Aleksandr]

However, a solution to this problem has been found. Who is interested - ask me. Solution absolutely not obvious...

So what's the solution?

You need to run the client with the following parameters - client = TelegramClient('my_session', api_id, api_hash, system_version="4.16.30-vxCUSTOM")
Just need add a parameter 'system_version' as is, but 'CUSTOM' can be changed to any other string.
Don't ask me why it works ) I don't know ))

Let the author of the Telethon-library tell us why it works...