1. This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.

Tweet Limit through API, php script, on Aged Accounts?

Discussion in 'Social Networking Sites' started by c-a-w, Jun 15, 2013.

  1. c-a-w

    c-a-w Newbie

    Joined:
    Nov 15, 2012
    Messages:
    29
    Likes Received:
    4
    As an experiment I purchased 10 aged accounts (3+ years old). I set them all up with developer access, changed their names, passwords, and connected them to a little php script I made to test.

    I ran a simple search to find people tweeting about a certain topic (let's say, "nba finals") and began responding to some people (not an (at)reply, but in-line conversation reply).

    Here's an example conversation (not real accounts or tweets):

    (at)randomUser [doesn't follow me, i don't follow]:
    (at)nbaSuperFan [reply to tweet id of the above, not as general (at)reply]:
    The link wouldn't always be the same. But always nba(.)com.

    About 25% of the time I wouldn't link at all:

    (at)anotherRandomUser:
    (at)nbaSuperFan:
    After nearly 100 tweets in 24 hours (all sent manually, through simple php script using Twitter API on clean account and ip) Twitter sent me a message that my account was deactivated. But once I filled out a CAPTCHA I was back in action.

    But after another 25 or so I was blocked again, this time for at least 24 hours (still blocked). I expect they'll let me back in the next day or so, but I'd rather not get blocked at all.

    All of my tweets are unique. All of my links are unique. All of my tweets are human generated, in response to actual tweets in a natural way. Nothing looks like spam because it's all manually written by me.

    I'm not sure exactly what I want to do if this experiment works yet, but I'd like to be able to send 100-300 tweets a day without being sent to "Twitter Jail". Every tweet will always be conversational.

    Can you help me know what I'm doing wrong and how I might get around this?


    (please forgive the (at)'s. The at symbol keeps triggering BHW spam filter for some reason)