Twitter suspends BraveNewCode’s OAuth token for the WordTwit plugin


Late Wednesday Twitter suspended BraveNewCode’s OAuth token for their WordTwit plugin, which allows users to send out tweets when they publish posts and at scheduled intervals. In plain English, this means that the default settings for WordTwit would no longer function, and anyone using WordTwit would soon realize none of their post tweets were going out anymore.

Twitter suspended the OAuth token without warning, according to BraveNewCode, and cited the following as their reason for the decision:

“[WordTwit Pro] facilitates serial posting across multiple accounts, tweet/retweet automation, tweet branding and automated affiliate advertising.”

At the moment BraveNewCode doesn’t see a way to resolve the issue, so they are directing users to use the second setup option WordTwit offers. It involves setting up a Twitter app that will handle the tweeting of posts (instead of using BraveNewCode’s you use your own). The setup process is a bit more complicated, but then again it works where the old way no longer does.

WPCandy was hit by this particular issue last week, since we use WordTwit Pro to tweet out posts as they are published (which probably means I should update this post). I was able to use the documentation BraveNewCode provided to roll out our own Twitter app and get everything back on track in less than an hour, so kudos to them for handling the situation well.

11 thoughts on “Twitter suspends BraveNewCode’s OAuth token for the WordTwit plugin

  1. Unfortunately it looks like Twitter’s customer service is really lacking when it comes to blocking valid users. I work with a host who has been blocked by Twitter with no explanation, and according to the host they have ignored repeated requests for an explanation on what why this happened and how they could fix the situation.

    This was discovered after repeated customer contacts regarding really slow site load times and it was tracked down to those users using a variety of Twitter plugins and other tools.

  2. Well I rolled my own auto tweeting on top of an auto poster script.

    BTW, I dumped brave whateveh’s mobile plugin (which I bought) in favor of the free BAAP which I think is very good.

  3. ya we had to do this as well, they sent an email out, not sure if you guys at wpcandy got it last week.

    • I did receive it, but it was after discovering the problem myself and then fixing it. Still, we noticed the problem at WPCandy a bit earlier than the average users probably would.

  4. How can you guys think this is Twitter’s fault? The point of oAuth is security and having the keys be public (in open source code like a plugin) is a big limitation but it’s not an option. It’s something Duane (from WordTwit) and Alex have discussed in public before since we at Crowd Favorite run into the same issues with the Twitter Tools plugin and Social plugin:

    Luckily MailChimp is forward thinking enough and has set up a proxy (or relay) as Otto noted requiring here:

    Keep in mind this was all discussed back in June 2010…

  5. Wait, they made the secret public? *headdesk*

    Anybody who authorized their app should go deauthorize it immediately. Otherwise, you might have evil people start posting as you on twitter.

    • BTW, Simple Twitter Connect has required you to create your own Twitter Application from version 0.1. This may be slightly less than user friendly, but in the long run, it’s just a requirement for security and sanity reasons.

      Advantages to using your own Application:
      – It’s secure
      – Branding is your own on your tweets
      – It doesn’t get you banned or blocked for no obvious reason

      – You may have to learn something
      – Some people think that copy-paste of a couple of strings is hard


Comments are closed.