-
-
Notifications
You must be signed in to change notification settings - Fork 329
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
The user has been deleted/deactivated (caused by GetLocatedRequest) #22
Comments
I don't know guys - it's better to ask TG about it. I may suggest they started banning accounts. |
Yeah... you probably should put a HUGE warning in the README. I used your tool for literally 20 seconds, and now I don't get to use Telegram any more. I'm not the only one. |
May I ask what kind of number did you use? As I can see on the other repository's issue - LonamiWebs/Telethon#297 - TG bans only VOIP/virtual numbers and almost never physical ones. |
My personal physical number |
sorry to hear that, man. but yeah, will update README definitely |
try to use this bug LonamiWebs/Telethon#4051 (comment) to avoid bans, my accouns live longer after this |
Just to make it clear. Please correct me if I'm wrong.
Also. Just several rhetorical questions:
|
Maybe its unrelated, but when i used telethon before, telegram always logged me out from all devices. No matter what script did (i was just sending automated messages to bot), even with this params. So its most probably impossible to use telethon without risk of ban. Not only that, after logging in, all my messages that I send in 24 hours were deleted for everyone! Even messages that i sent manually. And with some chance, new messages just after loggin in are also being auto deleted for everyone. Imagine how you would explain this to people that thought you got hacked by phishing :) Maybe I'm very lucky that it just logged me out, not banned... Maybe its because of premium... We will never know this. |
[ * ] Start harvesting data: |
I tried your code with several TG account. |
It’s your solving :) |
one question,,, did you sccuess in this code? |
? |
It will ban you with a 100% legit phone number in your own country too... |
thanks.. |
one of the possible solution, as i can see: |
don't understand well |
this code is working fine in your side? |
what's your email? |
you should consider increasing the default to something longer, and instructing users that feel safe to decrease it. That way more people don't wind up on this post.... with a banned account. Seems like a better default would be responsible |
You know, that could be a race between us and TG - we are increasing the time to avoid banning - they set another bottom line... repeat :) at the end - they will remove that feature and set it up as a bug (if it ever happen). but they can't set a huge time as it will brake the "find people nearby" feature |
https://github.com/wiz0u/WTelegramClient/blob/master/FAQ.md#prevent-ban from what I understand all accounts issued an API key are placed under immediate scrutiny. New or reused phone numbers even more. The current construction of the tool basically floods the TG API with repetitive requests at a constant interval. This type of behavior is incredibly detectable and conspicuous. CCTV is very public so it is likely telegram devs are monitoring the exploit as we speak. You could try to send requests at a randomized interval. Perhaps the GPS coordinates could be altered within a reasonable tolerance between requests to mimic real traffic. Sending requests from a frequented location/IP and including your own location in your request may help as well. Anything to camouflage the traffic and make it look realistic will decrease your chance of ban. Ultimately Telegram accounts with API access are very temperamental. The ideal vector for this would be to use 25 unique, aged accounts sending an individual request ( instead of one account sending 25 identical requests ). |
Man, if you watch Pavel's interview to Taker, he told he had around 30 people in his team and almost 1B users. Hence it's quite tough to manage customers when you have so few team members |
I did watch it. But the thing is, they DO ANSWER some questions in Twitter. But not all. Its very strange. I asked them like 10 times about why my account isnt shown in search, no reply. I also saw some people asked about telethon bans, also no reply. But when somebody ask stupid question that can be googled, instant reply. I understand its very hard to help people with such small team. But they totally ignore some questions. Thats why i think they dont actually care about users. Now, instead of optimizing their app, they add pointless features. |
in that case, we are showing them flaws in a hard way, so the whole World knows about it ;) |
Спасибо за скрипт! В контексте треда: Сейчас ввожу номер и код, после этого скрипт не вываливается но и не продолжает работать - просто ничего не происходит (ранее, с другим номером, всё работало). Если остановить и запустить заново, то между номером и кодом выскакивает "Telegram is having internal issues AuthRestartError: Restart the authorization process (caused by SendCodeRequest)". Ввод кода снова не приводит ни к какому результату - скрипт не работает но и не вываливается. Как бороться? В копилку кейсов - на свежем аккаунте, зарегистрированном на номер виртуального оператора, дал выполнить только одну задачу, при втором запуске сообщил что номер забанен. |
с ботом тоже не получилось: |
Hey keyreel. |
I've used a number of accounts, just 1 was banned - the number of a VOIP operator. The last one account not banned but do not work. I think that Ivan will find the proper way :) |
финита ля комедия |
@IvanGlinkin any chance to avoid blocking? |
у всех всё работает? есть статистика или рекомендации чтобы блока избежать? |
Ребят, я иногда поражаюсь вашей наивности. Неужели вы думаете, что в телеграме сидят дураки и оставляют дыры открытыми? Основной обход блокировки который реализован - задержка по времени между запросами. Второй обход (он не реализован, если есть желание - велкам в конрибюторы) - сделать несколько аккаунтов и в несколько treads в параллель делать запросы. Пока телега не сделала капчу или что-то похожее - все это работает. |
Понял, спасибо! и респект за труды :) |
Есть ещё один вариант, поменять библиотеку c telethon на pyrogram. С telethon замечены многочисленные проблемы при работе с API: выкидывает сессию, банит аккаунты. Через pyrogram я парсил 50к аккаунтов без задержек, без банов. Как ты отметил ранее, мы используем официальные инструменты телеграм: люди рядом и апи методы. Банить не за что. |
pyrogram банится так же часто, как telethon |
Изучал сейчас варианты использования нескольких аккаунтов. Правильно ли понимаю что многопоточность в данном случае предпочтительнее асинхронности только потому что легче интегрировать в синхронный код и не придётся переписывать весь код на аснхронный, или есть ещё какие-то подводные камни при использовании asyncio в этом контексте? |
Traceback (most recent call last):
File "/Users/x/Desktop/CCTV/start.py", line 144, in
result = client(functions.contacts.GetLocatedRequest(
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/opt/homebrew/lib/python3.12/site-packages/telethon/sync.py", line 39, in syncified
return loop.run_until_complete(coro)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/opt/homebrew/Cellar/[email protected]/3.12.3/Frameworks/Python.framework/Versions/3.12/lib/python3.12/asyncio/base_events.py", line 687, in run_until_complete
return future.result()
^^^^^^^^^^^^^^^
File "/opt/homebrew/lib/python3.12/site-packages/telethon/client/users.py", line 30, in call
return await self._call(self._sender, request, ordered=ordered)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/opt/homebrew/lib/python3.12/site-packages/telethon/client/users.py", line 87, in _call
result = await future
^^^^^^^^^^^^
telethon.errors.rpcerrorlist.UserDeactivatedBanError: The user has been deleted/deactivated (caused by GetLocatedRequest)
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/Users/x/Desktop/CCTV/start.py", line 151, in
except FloodWaitError as e:
^^^^^^^^^^^^^^
NameError: name 'FloodWaitError' is not defined
The text was updated successfully, but these errors were encountered: