[Decim]

Hello.

I'm working on a program that would automatically keep trying to change your username on a particular website (yes, a "turbo").

The login and name change works fine, but I have another issue.
After around 50 tries, the website blocks any name changes for around 10 minutes.
How can this be bypassed?

It must be possible as I've seen applications that manage to do this over a thousand times.

I haven't tried using proxies but it would probably just end up raising more red flags since I'm trying to change the name of a single account.

Thanks for reading.

[Mr Kake]

Hello.

I'm working on a program that would automatically keep trying to change your username on a particular website (yes, a "turbo").

The login and name change works fine, but I have another issue.
After around 50 tries, the website blocks any name changes for around 10 minutes.
How can this be bypassed?

It must be possible as I've seen applications that manage to do this over a thousand times.

I haven't tried using proxies but it would probably just end up raising more red flags since I'm trying to change the name of a single account.

Thanks for reading.

try clearing cookies and relogging at 50 resets

[Odus]

Most turbos queue the username change and wait for it to become available, meanwhile it's viewing the target profile on loop.

[Decim]

Most turbos queue the username change and wait for it to become available, meanwhile it's viewing the target profile on loop.

I thought of that but it wouldn't work for banned/suspended usernames.
(While it may seem confusing that I would need it to work for banned usernames too, I do for what I'm trying to achieve. )

[Ninja]

Try finding different links for changing usernames, or proxies (and different usernames then).

[Odus]

I thought of that but it wouldn't work for banned/suspended usernames.
(While it may seem confusing that I would need it to work for banned usernames too, I do for what I'm trying to achieve. )

Ah. I know Twitter has a data-formatted URL but it also has throttling (180ish responses iirc). You'll probably need to introduce proxies to it then unless there's some bug which resets it each session or whatever. That isn't the case with IG anyway.

[Decim]

Ah. I know Twitter has a data-formatted URL but it also has throttling (180ish responses iirc). You'll probably need to introduce proxies to it then unless there's some bug which resets it each session or whatever. That isn't the case with IG anyway.

The website I'm working on also formats the URL based on the username, but again, it can't be used with banned usernames.

Try finding different links for changing usernames, or proxies (and different usernames then).

Not quite sure what you mean.

[+Haze]

You can't really bypass a server side restriction, what you should do is, finding another endpoint for checking to see if the username is available or not. Then only logging in and changing the username when you need to.

[Decim]

You can't really bypass a server side restriction, what you should do is, finding another endpoint for checking to see if the username is available or not. Then only logging in and changing the username when you need to.

I figured.

If anyone has a work around, I'm all ears.

Thanks for the help anyway.

[SL x TnT]

Unless you give the website, we can only give ideas that might work.

Some things to try.
- Multiple usernames.
- Different IPs.
- Different way to check if a name is available. Maybe they have an API call when creating an account that says if it's taken or not.
- Mobile API.

[Decim]

Unless you give the website, we can only give ideas that might work.

Some things to try.
- Multiple usernames.
- Different IPs.
- Different way to check if a name is available. Maybe they have an API call when creating an account that says if it's taken or not.
- Mobile API.

I had exhausted all those options before making this thread, thanks anyway.

---

I'm just going to have to skip some test cases.
Regardless, thanks for all the help.