[twitter-dev] Re: Followers count
If I'm not mistaken, that still requires you to page through 5000 at a time until you reach the end to figure out the number of followers. I don't need the user ids of each follower, just the count. Being able to get this with users/show is perfect because it only requires one API call. Except it doesn't update between status updates. Will this be fixed? - Jason On Sep 4, 8:51 pm, freefall wrote: > Until today you could use:http://twitter.com/followers/ids.xml > > and get the total - this was way more accurate than getting it from > user/show. They appear to ahve just lowerd this total to 5000 so that > will no longer work (unless that's a bug). > > > On Sep 2, 5:44 pm, Jason Tan wrote: > > > > Hello, > > > > I have spent a good portion of today reading through closed, merged, > > > and open issues onhttp://code.google.com/p/twitter-api/issues/list > > > > I am trying to figure out the best way to get an accurate followers > > > count. Initially, I was using /users/show which returns the full user > > > object, including the followers_count item. However, I have noticed > > > that this number only updates when the user posts a tweet. If the > > > user has no new tweets, the follower count is not updated. Data I was > > > pulling in was many days old. I understand the need to cache data, > > > but being unable to pull up an approximate count of followers from the > > > past several days is a problem. > > > > I have seen this issue posted many times, but it is always merged into > > > issue 474, which appears to only deal with the following flag, and not > > > the followers_count. There was one issue (which I can't find anymore) > > > where there was acknowledgment that the users/show data was cached > > > until a new post was made but no mention of any fix or solution. > > > > My next approach was to use the statuses/user_timeline. I wasn't sure > > > if the user object for each status would have the "current" value or > > > the value at the time of the status update. When I grabbed the xml > > > formatted response, I got (starting from the most recent status and > > > going back): > > > 1686, 1653, 1685, 1685, 1685, 1685, 1685... > > > > Through the rest of the statuses, it stayed the same. Interestingly, > > > 1686 is the current value listed on the website. 1653 was the value I > > > got from /users/show. And I'm quite certain that the followers count > > > did not stay constant at 1685. > > > > Moreover, when I grabbed the json version of statuses/user_timeline, I > > > got entirely different results: > > > 1653, 1653, 1683, 1675, 1652, 1661, 1644... > > > > This seems to reflect the current number of followers at the time of > > > the status update, unlike the XML feed. > > > > Anyways, to get back to my original question. How do I get an > > > accurate followers count for a user? Also, why are there still XML/ > > > JSON discrepancies (I came across a few reported issues that said they > > > had been resolved). > > > > Any help or suggestions would be very much appreciated! > > > > Thanks, > > > Jason > > > > P.S. The account I was using for the above examples was DailyPHP
[twitter-dev] Re: Followers count
It's a good idea to have lots of checks in place. Twitter reliably returns unreliable data... ESPECIALLY BEFORE HOLIDAY WEEKENDS. In fact, for a couple of calls yesterday we got non-error responses saying that the user had ZERO followers. Then it was 5000 followers. Now it is their follower count +- 5%. I could deal with this if Twitter.com used the same bogus data, but Twitter itself doesn't use its own API calls, so the DM count, the follower/friend count... these are all internally computed and do not match any existing API call. On Sep 5, 11:35 am, Jesse Stay wrote: > Fortunately it only affected a couple users, but I'd like to make it up to > them. BTW, this didn't affect the mass unfollow feature you saw Scoble and > others using (that would have worked fine). This affected the "unfollow > those who unfollow me" feature. We have safety valves in place as well, but > there are still a few users that get through that. > Jesse > > On Sat, Sep 5, 2009 at 12:30 PM, Dewald Pretorius wrote: > > > Jesse, > > > Last night when this thing hit I actually immediately thought about > > you and wondered how it impacted you. > > > I'm now thanking my lucky stars that I don't do mass unfollow. I do > > have the "unfollow those who unfollow me" feature, but I have limited > > it to a maximum of 10 unfollows every 8 hours, even if the API said > > that more people have unfollowed the user. That safety valve has > > seriously saved my butt this time. > > > Dewald > > > On Sep 5, 3:06 pm, Jesse Stay wrote: > > > Again, I can't stress this enough - when bugs like this are introduced, > > it > > > is imperative that follow limits are also removed temporarily (or on a > > > case-by-case basis) so we can make this up to our users. I've already > > had > > > to issue refunds to a couple due to this. If you need me to send you the > > > usernames John let me know. > > > Jesse > >
[twitter-dev] Re: Followers count
I would have built in something like doing an array diff before doing any unfollow, and if the diff is 10%+ of the old followers list, then just bail and do nothing. Even the mass unfollow would not have worked, if the API returned only 5,000 friends instead of the full list, correct? Dewald On Sep 5, 3:35 pm, Jesse Stay wrote: > Fortunately it only affected a couple users, but I'd like to make it up to > them. BTW, this didn't affect the mass unfollow feature you saw Scoble and > others using (that would have worked fine). This affected the "unfollow > those who unfollow me" feature. We have safety valves in place as well, but > there are still a few users that get through that. > Jesse
[twitter-dev] Re: Followers count
Fortunately it only affected a couple users, but I'd like to make it up to them. BTW, this didn't affect the mass unfollow feature you saw Scoble and others using (that would have worked fine). This affected the "unfollow those who unfollow me" feature. We have safety valves in place as well, but there are still a few users that get through that. Jesse On Sat, Sep 5, 2009 at 12:30 PM, Dewald Pretorius wrote: > > Jesse, > > Last night when this thing hit I actually immediately thought about > you and wondered how it impacted you. > > I'm now thanking my lucky stars that I don't do mass unfollow. I do > have the "unfollow those who unfollow me" feature, but I have limited > it to a maximum of 10 unfollows every 8 hours, even if the API said > that more people have unfollowed the user. That safety valve has > seriously saved my butt this time. > > Dewald > > On Sep 5, 3:06 pm, Jesse Stay wrote: > > Again, I can't stress this enough - when bugs like this are introduced, > it > > is imperative that follow limits are also removed temporarily (or on a > > case-by-case basis) so we can make this up to our users. I've already > had > > to issue refunds to a couple due to this. If you need me to send you the > > usernames John let me know. > > Jesse >
[twitter-dev] Re: Followers count
Jesse, Last night when this thing hit I actually immediately thought about you and wondered how it impacted you. I'm now thanking my lucky stars that I don't do mass unfollow. I do have the "unfollow those who unfollow me" feature, but I have limited it to a maximum of 10 unfollows every 8 hours, even if the API said that more people have unfollowed the user. That safety valve has seriously saved my butt this time. Dewald On Sep 5, 3:06 pm, Jesse Stay wrote: > Again, I can't stress this enough - when bugs like this are introduced, it > is imperative that follow limits are also removed temporarily (or on a > case-by-case basis) so we can make this up to our users. I've already had > to issue refunds to a couple due to this. If you need me to send you the > usernames John let me know. > Jesse
[twitter-dev] Re: Followers count
Again, I can't stress this enough - when bugs like this are introduced, it is imperative that follow limits are also removed temporarily (or on a case-by-case basis) so we can make this up to our users. I've already had to issue refunds to a couple due to this. If you need me to send you the usernames John let me know. Jesse On Sat, Sep 5, 2009 at 12:01 PM, PJB wrote: > > > The friend/follower counts are TOTALLY off. Why can't new features be > introduced without breaking critical existing features? When will > this be fixed. Many of us rely on these counts for accurate f/f > counts! > > On Sep 4, 8:49 pm, John Kalucki wrote: > > The 5k limit is a bug. Working to fix. > > > > On Sep 4, 6:51 pm, freefall wrote: > > > > > Until today you could use:http://twitter.com/followers/ids.xml > > > > > and get the total - this was way more accurate than getting it from > > > user/show. They appear to ahve just lowerd this total to 5000 so that > > > will no longer work (unless that's a bug). > > > > > On Sep 3, 7:24 am, Waldron Faulkner wrote: > > > > > > Same oddness w. friends count as well? I'd guess so. > > > > > > My problem is that if I try to get followers using paging, I get > > > > different numbers (and different followers) than if I pull the entire > > > > list w/o paging. Also, followers disappear and reappear from one hour > > > > to the next. > > > > > > On Sep 2, 5:44 pm, Jason Tan wrote: > > > > > > > Hello, > > > > > > > I have spent a good portion of today reading through closed, > merged, > > > > > and open issues onhttp://code.google.com/p/twitter-api/issues/list > > > > > > > I am trying to figure out the best way to get an accurate followers > > > > > count. Initially, I was using /users/show which returns the full > user > > > > > object, including the followers_count item. However, I have > noticed > > > > > that this number only updates when the user posts a tweet. If the > > > > > user has no new tweets, the follower count is not updated. Data I > was > > > > > pulling in was many days old. I understand the need to cache data, > > > > > but being unable to pull up an approximate count of followers from > the > > > > > past several days is a problem. > > > > > > > I have seen this issue posted many times, but it is always merged > into > > > > > issue 474, which appears to only deal with the following flag, and > not > > > > > the followers_count. There was one issue (which I can't find > anymore) > > > > > where there was acknowledgment that the users/show data was cached > > > > > until a new post was made but no mention of any fix or solution. > > > > > > > My next approach was to use the statuses/user_timeline. I wasn't > sure > > > > > if the user object for each status would have the "current" value > or > > > > > the value at the time of the status update. When I grabbed the xml > > > > > formatted response, I got (starting from the most recent status and > > > > > going back): > > > > > 1686, 1653, 1685, 1685, 1685, 1685, 1685... > > > > > > > Through the rest of the statuses, it stayed the same. > Interestingly, > > > > > 1686 is the current value listed on the website. 1653 was the > value I > > > > > got from /users/show. And I'm quite certain that the followers > count > > > > > did not stay constant at 1685. > > > > > > > Moreover, when I grabbed the json version of > statuses/user_timeline, I > > > > > got entirely different results: > > > > > 1653, 1653, 1683, 1675, 1652, 1661, 1644... > > > > > > > This seems to reflect the current number of followers at the time > of > > > > > the status update, unlike the XML feed. > > > > > > > Anyways, to get back to my original question. How do I get an > > > > > accurate followers count for a user? Also, why are there still > XML/ > > > > > JSON discrepancies (I came across a few reported issues that said > they > > > > > had been resolved). > > > > > > > Any help or suggestions would be very much appreciated! > > > > > > > Thanks, > > > > > Jason > > > > > > > P.S. The account I was using for the above examples was DailyPHP- > Hide quoted text - > > > > > > - Show quoted text - > > > > >
[twitter-dev] Re: Followers count
The friend/follower counts are TOTALLY off. Why can't new features be introduced without breaking critical existing features? When will this be fixed. Many of us rely on these counts for accurate f/f counts! On Sep 4, 8:49 pm, John Kalucki wrote: > The 5k limit is a bug. Working to fix. > > On Sep 4, 6:51 pm, freefall wrote: > > > Until today you could use:http://twitter.com/followers/ids.xml > > > and get the total - this was way more accurate than getting it from > > user/show. They appear to ahve just lowerd this total to 5000 so that > > will no longer work (unless that's a bug). > > > On Sep 3, 7:24 am, Waldron Faulkner wrote: > > > > Same oddness w. friends count as well? I'd guess so. > > > > My problem is that if I try to get followers using paging, I get > > > different numbers (and different followers) than if I pull the entire > > > list w/o paging. Also, followers disappear and reappear from one hour > > > to the next. > > > > On Sep 2, 5:44 pm, Jason Tan wrote: > > > > > Hello, > > > > > I have spent a good portion of today reading through closed, merged, > > > > and open issues onhttp://code.google.com/p/twitter-api/issues/list > > > > > I am trying to figure out the best way to get an accurate followers > > > > count. Initially, I was using /users/show which returns the full user > > > > object, including the followers_count item. However, I have noticed > > > > that this number only updates when the user posts a tweet. If the > > > > user has no new tweets, the follower count is not updated. Data I was > > > > pulling in was many days old. I understand the need to cache data, > > > > but being unable to pull up an approximate count of followers from the > > > > past several days is a problem. > > > > > I have seen this issue posted many times, but it is always merged into > > > > issue 474, which appears to only deal with the following flag, and not > > > > the followers_count. There was one issue (which I can't find anymore) > > > > where there was acknowledgment that the users/show data was cached > > > > until a new post was made but no mention of any fix or solution. > > > > > My next approach was to use the statuses/user_timeline. I wasn't sure > > > > if the user object for each status would have the "current" value or > > > > the value at the time of the status update. When I grabbed the xml > > > > formatted response, I got (starting from the most recent status and > > > > going back): > > > > 1686, 1653, 1685, 1685, 1685, 1685, 1685... > > > > > Through the rest of the statuses, it stayed the same. Interestingly, > > > > 1686 is the current value listed on the website. 1653 was the value I > > > > got from /users/show. And I'm quite certain that the followers count > > > > did not stay constant at 1685. > > > > > Moreover, when I grabbed the json version of statuses/user_timeline, I > > > > got entirely different results: > > > > 1653, 1653, 1683, 1675, 1652, 1661, 1644... > > > > > This seems to reflect the current number of followers at the time of > > > > the status update, unlike the XML feed. > > > > > Anyways, to get back to my original question. How do I get an > > > > accurate followers count for a user? Also, why are there still XML/ > > > > JSON discrepancies (I came across a few reported issues that said they > > > > had been resolved). > > > > > Any help or suggestions would be very much appreciated! > > > > > Thanks, > > > > Jason > > > > > P.S. The account I was using for the above examples was DailyPHP- Hide > > > > quoted text - > > > > - Show quoted text - > >
[twitter-dev] Re: Followers count
The 5k limit is a bug. Working to fix. On Sep 4, 6:51 pm, freefall wrote: > Until today you could use:http://twitter.com/followers/ids.xml > > and get the total - this was way more accurate than getting it from > user/show. They appear to ahve just lowerd this total to 5000 so that > will no longer work (unless that's a bug). > > On Sep 3, 7:24 am, Waldron Faulkner wrote: > > > Same oddness w. friends count as well? I'd guess so. > > > My problem is that if I try to get followers using paging, I get > > different numbers (and different followers) than if I pull the entire > > list w/o paging. Also, followers disappear and reappear from one hour > > to the next. > > > On Sep 2, 5:44 pm, Jason Tan wrote: > > > > Hello, > > > > I have spent a good portion of today reading through closed, merged, > > > and open issues onhttp://code.google.com/p/twitter-api/issues/list > > > > I am trying to figure out the best way to get an accurate followers > > > count. Initially, I was using /users/show which returns the full user > > > object, including the followers_count item. However, I have noticed > > > that this number only updates when the user posts a tweet. If the > > > user has no new tweets, the follower count is not updated. Data I was > > > pulling in was many days old. I understand the need to cache data, > > > but being unable to pull up an approximate count of followers from the > > > past several days is a problem. > > > > I have seen this issue posted many times, but it is always merged into > > > issue 474, which appears to only deal with the following flag, and not > > > the followers_count. There was one issue (which I can't find anymore) > > > where there was acknowledgment that the users/show data was cached > > > until a new post was made but no mention of any fix or solution. > > > > My next approach was to use the statuses/user_timeline. I wasn't sure > > > if the user object for each status would have the "current" value or > > > the value at the time of the status update. When I grabbed the xml > > > formatted response, I got (starting from the most recent status and > > > going back): > > > 1686, 1653, 1685, 1685, 1685, 1685, 1685... > > > > Through the rest of the statuses, it stayed the same. Interestingly, > > > 1686 is the current value listed on the website. 1653 was the value I > > > got from /users/show. And I'm quite certain that the followers count > > > did not stay constant at 1685. > > > > Moreover, when I grabbed the json version of statuses/user_timeline, I > > > got entirely different results: > > > 1653, 1653, 1683, 1675, 1652, 1661, 1644... > > > > This seems to reflect the current number of followers at the time of > > > the status update, unlike the XML feed. > > > > Anyways, to get back to my original question. How do I get an > > > accurate followers count for a user? Also, why are there still XML/ > > > JSON discrepancies (I came across a few reported issues that said they > > > had been resolved). > > > > Any help or suggestions would be very much appreciated! > > > > Thanks, > > > Jason > > > > P.S. The account I was using for the above examples was DailyPHP- Hide > > > quoted text - > > > - Show quoted text -
[twitter-dev] Re: Followers count
Until today you could use: http://twitter.com/followers/ids.xml and get the total - this was way more accurate than getting it from user/show. They appear to ahve just lowerd this total to 5000 so that will no longer work (unless that's a bug). On Sep 3, 7:24 am, Waldron Faulkner wrote: > Same oddness w. friends count as well? I'd guess so. > > My problem is that if I try to get followers using paging, I get > different numbers (and different followers) than if I pull the entire > list w/o paging. Also, followers disappear and reappear from one hour > to the next. > > On Sep 2, 5:44 pm, Jason Tan wrote: > > > > > Hello, > > > I have spent a good portion of today reading through closed, merged, > > and open issues onhttp://code.google.com/p/twitter-api/issues/list > > > I am trying to figure out the best way to get an accurate followers > > count. Initially, I was using /users/show which returns the full user > > object, including the followers_count item. However, I have noticed > > that this number only updates when the user posts a tweet. If the > > user has no new tweets, the follower count is not updated. Data I was > > pulling in was many days old. I understand the need to cache data, > > but being unable to pull up an approximate count of followers from the > > past several days is a problem. > > > I have seen this issue posted many times, but it is always merged into > > issue 474, which appears to only deal with the following flag, and not > > the followers_count. There was one issue (which I can't find anymore) > > where there was acknowledgment that the users/show data was cached > > until a new post was made but no mention of any fix or solution. > > > My next approach was to use the statuses/user_timeline. I wasn't sure > > if the user object for each status would have the "current" value or > > the value at the time of the status update. When I grabbed the xml > > formatted response, I got (starting from the most recent status and > > going back): > > 1686, 1653, 1685, 1685, 1685, 1685, 1685... > > > Through the rest of the statuses, it stayed the same. Interestingly, > > 1686 is the current value listed on the website. 1653 was the value I > > got from /users/show. And I'm quite certain that the followers count > > did not stay constant at 1685. > > > Moreover, when I grabbed the json version of statuses/user_timeline, I > > got entirely different results: > > 1653, 1653, 1683, 1675, 1652, 1661, 1644... > > > This seems to reflect the current number of followers at the time of > > the status update, unlike the XML feed. > > > Anyways, to get back to my original question. How do I get an > > accurate followers count for a user? Also, why are there still XML/ > > JSON discrepancies (I came across a few reported issues that said they > > had been resolved). > > > Any help or suggestions would be very much appreciated! > > > Thanks, > > Jason > > > P.S. The account I was using for the above examples was DailyPHP- Hide > > quoted text - > > - Show quoted text -
[twitter-dev] Re: Followers count
Same oddness w. friends count as well? I'd guess so. My problem is that if I try to get followers using paging, I get different numbers (and different followers) than if I pull the entire list w/o paging. Also, followers disappear and reappear from one hour to the next. On Sep 2, 5:44 pm, Jason Tan wrote: > Hello, > > I have spent a good portion of today reading through closed, merged, > and open issues onhttp://code.google.com/p/twitter-api/issues/list > > I am trying to figure out the best way to get an accurate followers > count. Initially, I was using /users/show which returns the full user > object, including the followers_count item. However, I have noticed > that this number only updates when the user posts a tweet. If the > user has no new tweets, the follower count is not updated. Data I was > pulling in was many days old. I understand the need to cache data, > but being unable to pull up an approximate count of followers from the > past several days is a problem. > > I have seen this issue posted many times, but it is always merged into > issue 474, which appears to only deal with the following flag, and not > the followers_count. There was one issue (which I can't find anymore) > where there was acknowledgment that the users/show data was cached > until a new post was made but no mention of any fix or solution. > > My next approach was to use the statuses/user_timeline. I wasn't sure > if the user object for each status would have the "current" value or > the value at the time of the status update. When I grabbed the xml > formatted response, I got (starting from the most recent status and > going back): > 1686, 1653, 1685, 1685, 1685, 1685, 1685... > > Through the rest of the statuses, it stayed the same. Interestingly, > 1686 is the current value listed on the website. 1653 was the value I > got from /users/show. And I'm quite certain that the followers count > did not stay constant at 1685. > > Moreover, when I grabbed the json version of statuses/user_timeline, I > got entirely different results: > 1653, 1653, 1683, 1675, 1652, 1661, 1644... > > This seems to reflect the current number of followers at the time of > the status update, unlike the XML feed. > > Anyways, to get back to my original question. How do I get an > accurate followers count for a user? Also, why are there still XML/ > JSON discrepancies (I came across a few reported issues that said they > had been resolved). > > Any help or suggestions would be very much appreciated! > > Thanks, > Jason > > P.S. The account I was using for the above examples was DailyPHP
[twitter-dev] Re: Followers count
I hope you find out. I long ago gave up. If I really needed the feature, I would scrape that one out of the html, which I know is frowned upon, however, as your data shows, this is pretty all over the map. On Sep 2, 2009, at 2:44 PM, Jason Tan wrote: Anyways, to get back to my original question. How do I get an accurate followers count for a user? Also, why are there still XML/ JSON discrepancies (I came across a few reported issues that said they had been resolved). -- Scott * If you contact me off list replace talklists@ with scott@ *
[twitter-dev] Re: Followers Count doesn't add up with the actual followers
I can confirm this now. I just pulled the remaining followers that were not in the paged follower-list, but exist in the social-graph. So far all of them are suspended account. I guess with the paged list, the API only brings back the ones that are active. Chris On Fri, Jul 3, 2009 at 7:37 PM, Tim wrote: > > > Where > > are the other 200 go ? > To answer your questions, chances are that these 200 accounts have > been disabled (probably for being spam accounts), but I noticed there > are still counted in the number of followers. > > Tim >
[twitter-dev] Re: Followers Count doesn't add up with the actual followers
Others have also noticed that some accounts show up multiple times in the list of followers when retrieved via the API. Not sure why that happens, but it does. - h On Fri, Jul 3, 2009 at 11:37, Tim wrote: > > > Where > > are the other 200 go ? > To answer your questions, chances are that these 200 accounts have > been disabled (probably for being spam accounts), but I noticed there > are still counted in the number of followers. > > Tim >
[twitter-dev] Re: Followers Count doesn't add up with the actual followers
> Where > are the other 200 go ? To answer your questions, chances are that these 200 accounts have been disabled (probably for being spam accounts), but I noticed there are still counted in the number of followers. Tim
[twitter-dev] Re: Followers Count doesn't add up with the actual followers
Thanks Matt for pointing to the right place. Hope that this issue can be resolved quickly, because the alternative of hitting the individual user for all followers would be a disaster. Chris On Jul 2, 3:27 pm, Matt Sanford wrote: > Hi Chris, > > Welcome to the group! Take a look at the current list of issues > [1] … there are a few there related to this problem. Mark one of those > with a star (click on the star next to the issue number) and you'll > get updates when we make changes. > > Thanks; > – Matt Sanford / @mzsanford > Twitter Dev > > [1] -http://code.google.com/p/twitter-api/issues/list > > On Jul 2, 2009, at 4:20 AM, Chris Prakoso wrote: > > > > > Hi all, > > I am new with Twitter API Dev, so apologise if my question seems > > silly. > > > I have a user that has followers_count = 6000+ > > But when I try to collect the user data of those followers by paging > > through the statuses/followers API, at the end of the pages (where no > > more items are returned back), I get only about 5800-ish users. Where > > are the other 200 go ? > > > Am I missing something here ? > > > Thanks for your help, > > Chris
[twitter-dev] Re: Followers Count doesn't add up with the actual followers
Hi Chris, Welcome to the group! Take a look at the current list of issues [1] … there are a few there related to this problem. Mark one of those with a star (click on the star next to the issue number) and you'll get updates when we make changes. Thanks; – Matt Sanford / @mzsanford Twitter Dev [1] - http://code.google.com/p/twitter-api/issues/list On Jul 2, 2009, at 4:20 AM, Chris Prakoso wrote: Hi all, I am new with Twitter API Dev, so apologise if my question seems silly. I have a user that has followers_count = 6000+ But when I try to collect the user data of those followers by paging through the statuses/followers API, at the end of the pages (where no more items are returned back), I get only about 5800-ish users. Where are the other 200 go ? Am I missing something here ? Thanks for your help, Chris
[twitter-dev] Re: Followers count via api not consistent with real data
So does this also create the scenario where followers (not count) called via the api are different than the followers on the site? I have a client who has spam followers appearing on our site when we call followers method via the api and the same followers are not under her account on the site. On Mon, May 18, 2009 at 11:04 AM, Doug Williams wrote: > This is a known issue: > http://code.google.com/p/twitter-api/issues/detail?id=580 > Thanks, > Doug > -- > > Doug Williams > Twitter Platform Support > http://twitter.com/dougw > > > > > On Sun, May 17, 2009 at 12:58 AM, alon wrote: > >> >> I filed abug on this but im wondering if someone else is getting that >> also. >> Seems to happen to new users only: >> >> http://twitter.com/users/show.xml?screen_name=mirit_v >> >> http://twitter.com/mirit_v >> >> One is 40+ one is 30+ . big difference between count. for some users >> like /arik_a its 7 comparing to 47. >> > > -- Peter M. Denton www.twibs.com i...@twibs.com Twibs makes Top 20 apps on Twitter - http://tinyurl.com/bopu6c
[twitter-dev] Re: Followers count via api not consistent with real data
This is a known issue: http://code.google.com/p/twitter-api/issues/detail?id=580 Thanks, Doug -- Doug Williams Twitter Platform Support http://twitter.com/dougw On Sun, May 17, 2009 at 12:58 AM, alon wrote: > > I filed abug on this but im wondering if someone else is getting that > also. > Seems to happen to new users only: > > http://twitter.com/users/show.xml?screen_name=mirit_v > > http://twitter.com/mirit_v > > One is 40+ one is 30+ . big difference between count. for some users > like /arik_a its 7 comparing to 47. >
