Accounts with more followers will naturally take you longer to process. The
majority of users on Twitter do not have exceptionally large follower counts
(though your user base may reflect different demographics).
You can do analysis for users with low follower counts within an hour. For
users with
On 21 Feb., 06:50, "Orian Marx (@orian)" wrote:
> I don't know what the current state of this is but it looks like Site
> Streams will support unfollow events for this
> purpose:http://groups.google.com/group/twitter-development-talk/browse_thread...
>From the mentioned thread:
"I'm only seeing
I don't know what the current state of this is but it looks like Site
Streams will support unfollow events for this purpose:
http://groups.google.com/group/twitter-development-talk/browse_thread/thread/74ae054ec728e6dc
On Feb 18, 5:11 pm, Jo wrote:
> It seems as if no one at twitter as an answer
It seems as if no one at twitter as an answer or a solution on this.
That's bad...
Or are they still thinking about it?
Cheers.
Jo Seibert
On 15 Feb., 11:03, Dewald Pretorius wrote:
> Thanks Tim. So the point is, we still need to rely on the follower ids
> list API method if we want to maintain
Thanks Tim. So the point is, we still need to rely on the follower ids
list API method if we want to maintain an up to date picture of an
account's followers. For larger accounts this becomes impractical with
a limit of 350 calls per hour.
On Feb 15, 4:13 am, Tim Haines wrote:
> It sends you an e
It sends you an event when our subject user follows someone else, unfollows
someone else, or when they are followed by someone else. It does not send
an event when they are unfollowed by someone else.
Tim.
On Tue, Feb 15, 2011 at 3:08 AM, Dewald Pretorius wrote:
> If I remember correctly, Site
If I remember correctly, Site Streams sends you a transaction only
when the user follows another user (adding to Following). It does not
send you a transaction when someone else follows that user (adding to
Followers). I don't know if this work the same in User Streams.
Clarification by Twitter wil
I believe the new way to do this is to initially call the REST API to get
all of the ids for the first time you process this user. Then you setup a
User Stream on the user and process any requests that come in through there.
For your uses, if you only show users the differences in follower count
