Changes in NodeXL's Twitter Importers

Mar 25, 2013 at 2:21 AM
Edited Jun 18, 2013 at 1:48 AM
If you use NodeXL to import networks from Twitter, you'll notice some importer changes starting in NodeXL version Twitter recently changed the way that programs like NodeXL must request information from Twitter, and we had to modify NodeXL to meet Twitter's requirements.

The Twitter importers in earlier versions of NodeXL stopped working on Tuesday, June 11, 2013. If you import networks from Twitter, you will need to install a recent version of NodeXL. If you try to use a version of NodeXL earlier than, you will get a cryptic "Gone" error message from each importer.

Here are the Twitter-related changes in NodeXL version
  1. You can no longer import Twitter data into NodeXL without authorizing NodeXL to use your Twitter account. This used to be optional; now it's required.
  2. Specifying any NodeXL option that involves Twitter "follow" relationships will result in it taking a long time--hours, if not days--to import the network. Twitter has severely limited the rate at which programs like NodeXL can request these relationships, and NodeXL is forced to pause for fifteen minutes every time a limit is reached.
  3. In the Twitter search network (NodeXL, Data, Import, From Twitter Search Network), you now specify how many tweets you want to get from Twitter, up to a maximum of 18,000 tweets. You used to specify how many unique tweeters to get, up to a maximum of 1,500 tweeters.
  4. If Twitter whitelisted you before, your whitelisting is discontinued. (Whitelisting was where Twitter granted higher rate limits to some people.) All NodeXL users now have the same Twitter rate limits.
We may revise NodeXL's Twitter importers in future releases, given how some of the current features are no longer as useful as they were before Twitter made these changes.