Twitter and Banning?

[tggecko]

Hello all.
So it's pretty obvious that twitter bans newly created accounts based on the ip address that they were created with. However, can you authenticate (OAuth) a large number of accounts on the same ip address without twitter catching on?
Also, does twitter seem to flag accounts that haven't been verified through email?

Any input based on personal experience would be appreciated.
Thanks,
Chris

 

[Autumn]

Yes, if you are using the API (ie verifying using OAuth) then you will get banned a lot faster than going through the web interface; that's aside from the hassles of setting up API accounts. It does appear that IP re-use is an issue with the API as well, perhaps even more of an issue - there should be little reason for an IP to be using multiple API accounts unless they're a spammer.

API sucks - take the time to automate the web interface. I wasted a lot of time fucking around with the API first before I learnt my lesson.

Yes, accounts that aren't email verified get banned a lot quicker.

 

[tggecko]

Thanks for the information. Unfortunately, nearly all external services use the api to verify account information (ie. twitterfeed). Guess I'll have to use proxies for everything.

- Chris

 

[Krazy Kitty]

Yes, if you are using the API (ie verifying using OAuth) then you will get banned a lot faster than going through the web interface; that's aside from the hassles of setting up API accounts. It does appear that IP re-use is an issue with the API as well, perhaps even more of an issue - there should be little reason for an IP to be using multiple API accounts unless they're a spammer.

API sucks - take the time to automate the web interface. I wasted a lot of time fucking around with the API first before I learnt my lesson.

Yes, accounts that aren't email verified get banned a lot quicker.

I know I'm a dumbass, but could you please elaborate, Autumn? I'm not familiar with the terms.

I use proxies to create Twitter accounts and confirm them in the usual way via email link.

Should I be doing it a different way?

 

[Autumn]

No you're doing it the right way.

You can also sign up for an API account and use the Twitter API to post, follow / unfollow etc. It's much easier to use the API in an automated fashion than to go through the regular web interface, where you have to jump over various javascript hurdles.

The only stumbling block when using the API is that you have to use OAuth to login, which is a new type of authentication. You also have to sign up for an API account in addition to your regular Twitter account, and set up a new application with its own unique key, which is more steps to go through for each new account.

However, IMHO using the API is a big red flag for automated bot activity and API accounts will get banned for spammy behaviour faster than accounts that appear to be regular web users with a browser, going through the web interface.

 

[gsf134]

No you're doing it the right way.

You can also sign up for an API account and use the Twitter API to post, follow / unfollow etc. It's much easier to use the API in an automated fashion than to go through the regular web interface, where you have to jump over various javascript hurdles.

The only stumbling block when using the API is that you have to use OAuth to login, which is a new type of authentication. You also have to sign up for an API account in addition to your regular Twitter account, and set up a new application with its own unique key, which is more steps to go through for each new account.

However, IMHO using the API is a big red flag for automated bot activity and API accounts will get banned for spammy behaviour faster than accounts that appear to be regular web users with a browser, going through the web interface.

which process does tweetattacks use?

 

[EddyD]

Tweetattacks uses web interface. It mentions it on the software in about 1000 different places