Hello, Pat:
NodeXL uses Twitter's "GET friends/ids" API to get one block of 5,000 IDs for one user's followers. That API can be called once per minute. Thus, NodeXL can get one block of followers for approximately 60 users per hour. If you uncheck the "Limit to" box, it might make multiple calls per user, so the performance will be even worse. (There is a "Limit to" box, right? I ask because you're using an old version that I don't have in front of me.)
If your target has 79,000 followers and you request a 1.5-degree network, then NodeXL has to get the followers for 79,001 users. That will take roughly two months.
In the latest version of NodeXL, the Twitter dialog boxes strongly discourage you from requesting follow relationships. In all but the smallest networks, Twitter rate limits make this intolerably slow.
-- Tony
NodeXL uses Twitter's "GET friends/ids" API to get one block of 5,000 IDs for one user's followers. That API can be called once per minute. Thus, NodeXL can get one block of followers for approximately 60 users per hour. If you uncheck the "Limit to" box, it might make multiple calls per user, so the performance will be even worse. (There is a "Limit to" box, right? I ask because you're using an old version that I don't have in front of me.)
If your target has 79,000 followers and you request a 1.5-degree network, then NodeXL has to get the followers for 79,001 users. That will take roughly two months.
In the latest version of NodeXL, the Twitter dialog boxes strongly discourage you from requesting follow relationships. In all but the smallest networks, Twitter rate limits make this intolerably slow.
-- Tony