-
Top Commenters
-
Community
-
Popular Threads
-
Recent Comments
- Thanks for the report. I just had an idea that allows me to stress-test that thing properly when developing. Here's hoping I'll find what's causing your slowdowns. I'll keep you posted (naturally). C. ...
- Twerp Scan took about 8 minutes to run against an account with almost 500 followers. I noticed that there were 5 followers that came back with no value on Followers and a value of NaN on Ratio. Maybe ...
- Hi mdy, thanks for the comments! Re timeouts: I've just pushed a new release live which should deal with that particular problem. In short, the scripts now make 10x less requests, which should help ...
- Hi there. I've currently got 1,263 followers and Twerpscan was able to load and analyze over half of them before it finally hanged with 532 followers to go. I suspect it couldn't go further because ...
Release 2008-04-24
- new home! TwerpScan.com. Awesome!
- Support for followers list with more than 100 entries. Should work, don't know, please test.
- Numeric Twitter ID is shown in the table, thanks to @joshr for the idea. Should make it a bit easier to find newly registered followers.
If you have suggestions, bug reports or anything else, sound off.
Anonymous comments are allowed, oiy!
2 comments
-
mdy 3 weeks ago with 1 point
Hi there.
I've currently got 1,263 followers and Twerpscan was able to load and analyze over half of them before it finally hanged with 532 followers to go. I suspect it couldn't go further because it has no doubt hit the Twitter API limit of 70 requests per hour.
So bottomline, you'll be happy to know it works for folks with over 100 followers! 8-)
My feedback:
1) Is it possible to download the results table as a .csv file?
2. Is it possible to make the results available as a web page for 5 days after I initiate the scan, so I can come back to it and not have to wait until it finishes? I'll be happy to supply an email address where I can be contacted.
3) Can the verdict column be moved to the left most part of the table? I keep having to scroll left and right to see which follower it was that got a BLOCK verdict.
4) An alternative to #3 above would be to let me resize the width of the columns, so they can all fit on my screen.
5) Allow me to filter the followers that you'll analyze by specifying a cut-off for the join date (e.g., analyze only followers who joined after Oct 1, 2007). That way, if I use this service in October, we won't have to re-scan all the old followers again when I use the service again a few months later.
6) An alternative is to let me filter the followers that you'll analyze by specifying a cut-off date for the following relationship (i.e, when they started following me). I know this one may be tricky since the start of the following relationship does not seem to be available through the API.
7) Given the API limits, can we make it possible to resume a suspended or interrupted scan?
That's all from me for now. 8-) Thanks for this innovative service!
Cheers,
~ mdy -
Hi mdy,
thanks for the comments!
Re timeouts: I've just pushed a new release live which should deal with that particular problem. In short, the scripts now make 10x less requests, which should help processing and stability quite a bit (I hope). Would be nice if you could test it.
To answer your questions:
1. No CSV export at the moment, sorry. Interesting idea, tho. :)
2. Not at the moment, as the script contains NO server component at all. If there's enough demand, I might add something like this, tho.
3. I'm currently playing around with customisable tables -- which would include column reordering. Give me a few days.
4. How big/small is your screen, if I might ask?
5 + 6. I'm currently evaluating some options for a feature like this.
7. Unsure. Maybe.
Cheers,
C.


