Thanks for letting us know that setting your computer's clock fixed the problem for you.
It has to do with some arcane "handshaking" that goes on between NodeXL and Twitter during the authorization process. The current time is one part of the handshake, and if your computer's current time is too far off from Twitter's current time, then Twitter stops the handshake and prevents authorization.
Translation: Make sure your computer's clock is set correctly before using NodeXL's Twitter importers.
-- Tony
https://dev.twitter.com/discussions/3612
It has to do with some arcane "handshaking" that goes on between NodeXL and Twitter during the authorization process. The current time is one part of the handshake, and if your computer's current time is too far off from Twitter's current time, then Twitter stops the handshake and prevents authorization.
Translation: Make sure your computer's clock is set correctly before using NodeXL's Twitter importers.
-- Tony
https://dev.twitter.com/discussions/3612
