Skip to content
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

Logged out of account everywhere and can not regain access, simply by logging in using this library. #4102

Closed
3 tasks done
diimdeep opened this issue May 4, 2023 · 1 comment

Comments

@diimdeep
Copy link

diimdeep commented May 4, 2023

  • 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 telethon

Code that causes the issue

from telethon import TelegramClient, events, sync

# These example values won't work. You must get your own api_id and
# api_hash from https://my.telegram.org, under API Development.
api_id = 
api_hash = 

client = TelegramClient('session_name', api_id, api_hash)
client.start()

Hello @Lonami

By simply logging into account by using this example code provided in the Readme, I have lost access to my personal account and was logged out everywhere and at the moment can not regain access to it.

Looks like you know about this possibility from numerous incidents #4051 #824

I urge you to put highly visible warning about very high possibility of losing access to account. Only briefly mentioning this in FAQ is simply not enough and does not provide adequate visibility for end users that could only read Readme and use provided example code.

Please put warning about this in:

  • Readme
  • In example files
  • In interactive routine start()

I hope you understand my concern.

Update:

  • I regained access by logging in from phone and receiving SMS code, but this was scary experience
  • SpamBot does not report anything
@Lonami Lonami closed this as completed in c4a41ad May 4, 2023
@Lonami
Copy link
Member

Lonami commented May 4, 2023

Please put warning about this in:

  • Readme
  • In example files
  • In interactive routine start()

Damn that's kinda extreme, don't you think? "Go away, this library will just ban your account" is not good advertising.

I've added a reminder that breaking the ToS can lead to account bans. That really should be obvious to anyone using third-party services, though. But hopefully more people will be aware of this reality with that change.

very high possibility of losing access to account

I'm also not sure where this number is coming from. I've been using the library for years (hell, even developing it, and doing a lot of unintended things), and have never experienced it myself. Sure, a lot of people complain about bans. But we don't see people complaining about it working just fine. There is selection bias here.

Jisan09 added a commit to TgCatUB/Telethon that referenced this issue May 28, 2023
* except and propagate TypeNotFoundError during update handling

* Better document breaking ToS will lead to bans

Closes LonamiWebs#4102.

* Fix KeyError when ID is in cache but queried without mark

Closes LonamiWebs#4084.

* Fix asyncio.CancelledError was being swallowed by inner except

Closes LonamiWebs#4104.

* Add check for asyncio event loop to remain the same

* Update FAQ with more common questions

---------

Co-authored-by: Lonami Exo <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants