very interesting thread, dont see much talk about the Telegram sphere. Would love to delve into it more
thanks for the notification
Hi. It's been a while and I'm not really active on this forum, I'm way more active on telegram, and this forums looks a bit old.
Sad I missed so many threads, it seems that this forum is actually pretty good.
The problem is that because it's public, everyone can see what we are trying to do & replicate our techniques.
which geo do you use ? i was using + 62 for light actions but now i am focusing on more heavy activities suchas 1:1 dm or inviting. +62 seems a little weak.
Concerning geo, I have a personal emphasis with +31 and +44 numbers. +44 are the best price/quality ratio in my opinion.
And I'm not the only one: for instance +44 are used by company like Navy Deep for their aged accounts.
When I was saying that Telegram does not care about your IP, that is partly true. But not in the beginning.
When you start warming up your accounts, you need *isolated residential proxies*. 1IP per account, in the country of the phone
number.
Then, you start your warmup tasks. 2 weeks is enough in my opinion.
For warmup take inspiration of other Telegram software(lot of them) aimed for large scale advertising and scraping/adding(don't want to make a free ad lmao)
Concerning the API ID and API Hash that I was talking in the earlier post, it was pretty simple: its the official API ID and API Hash of the Android Telegram Application.
Don't forget to set the "lang_pack" parameter in DeviceConfig if you do so! Otherwise Telegram will ban you.
I was having trouble with that when buying account. Keep the same geo as the phone number for residential proxies,
and adapt the .json file containing the session information you bought(most of the time it's an android device) to the good
lang_pack(most of the time "android").
Then, you might want to use official API_ID and API_HASH, they are provided for free by opentele, I also found a couple of good
sustainable one online. They allow you to act like a real client. (Don't forget about `lang_pack`!!!!)
Opentele does that for you if you use Python and Telethon library, but its quite easy to port to another library/language anyway.
If you use Golang:
I added support for TDATA to the library https://github.com/celestix/gotgproto in Golang if you need to.
(following commit: https://github.com/celestix/gotgproto/commit/39fd6967a98abd22c7c78e5117c4288a363d90fb)
why not use the better quality 4g proxys
Not needed and expensive. Telegram doesn't care.
When I warmup my account, each account will costs me around 30-40MB of bandwidth.
After warm up, I use VPN(since Telegram is privacy oriented they don't ban users using VPN, since it represents a lot of their user base), but you need to warmup first.
I create 500 accounts/month. 35*500=17500MB=17.5GB per month... That's already a lot, and mobile proxies are even more expensive.
So that was for the "cheap" account, usually for Mass DMs, or scraping/adding.
You don't want aged account like from 2014 for that, as Telegram will still bans them(they are reported as spam by user)
For Mass Forwards, you aim at good aged accounts.
I have 2014 aged accounts, I buy them premium, and I can send my ad to a bit less that 500 chats without getting banned.
It costs a lot but they are worth it.
I'm collecting data on the number of messages/mass dms that gets your account banned.
Same for the name of competitors... I also have more information to share about how to imitate the official API.
I'm not checking this forum often cause its too public..
But this place is too public in my opinion, why not creating a tg private group for further discussion?
I don't know if we can do that according to the rule so don't want to get banned.
100 account for instance is already 150MB.
Am I stupid?
My mistake, I'm re-reading it...
That's 15MB....