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
I compiled the tdlib example application to test it out. Initially I thought I'll just send messages between my number and my wife's number, so I got an api_key and hash with my account and logged in with her number on the example app and her number was banned immediately.
Then I though maybe I shouldn't have used the api_key and hash from my account, so then I went out and got a dedicated mobile number (South African since that is where I live) and inserted it into an old unused phone.
I left the "test" api_key and hash unchanged and authenticated with this new number.
It said "authorization is completed" but when I pressed [m] to send a message the number was banned again.
Note that there is not a single line of my own code running there - it is THEIR code that causes legitimite numbers to be banned immediately without any reason or explanation.
If they want to encourage 3rd parties to do development on tdlib why do they make it impossible for them to actually get it working!
If I'm going to write code based on tdlib that will be used on thousands of products I need more reliability and predictability than this. Can someone from tdlib please respond?
The text was updated successfully, but these errors were encountered:
If your account was mistakenly banned, please try to log in from an official app and send a email to recover the account following instructions provided by the app. See https://tginfo.me/phone-number-is-banned-en/ for some additional details.
Thank you @levlam , but those don't tell me something I don't know yet and they're not specific enough so I can understand what in my process caused my numbers to be blocked before even sending a single message.
This is a bad start for basing a new product on because Telegram's banning algorithm is highly inconsistent and unpredictable. They must explain how you can be a spammer if you only send messages to a few numbers and only a few messages a day. I will not look for other solutions which does not involve Telegram and take my business with me.
I compiled the tdlib example application to test it out. Initially I thought I'll just send messages between my number and my wife's number, so I got an api_key and hash with my account and logged in with her number on the example app and her number was banned immediately.
Then I though maybe I shouldn't have used the api_key and hash from my account, so then I went out and got a dedicated mobile number (South African since that is where I live) and inserted it into an old unused phone.
I left the "test" api_key and hash unchanged and authenticated with this new number.
It said "authorization is completed" but when I pressed [m] to send a message the number was banned again.
Note that there is not a single line of my own code running there - it is THEIR code that causes legitimite numbers to be banned immediately without any reason or explanation.
If they want to encourage 3rd parties to do development on tdlib why do they make it impossible for them to actually get it working!
If I'm going to write code based on tdlib that will be used on thousands of products I need more reliability and predictability than this. Can someone from tdlib please respond?
The text was updated successfully, but these errors were encountered: