We've experienced this at random, whether the user has 1+ million followers or whether they have 20 followers. I generally don't mind if the post has the timestamp of 15~ minutes past the time we actually sent the request. As far as the timestamp being posted, that is also delayed as well.
I can guess we are running into a posting limit. I've actually had to cut back on our 20 minute cron jobs that checks whether a user is playing a game on steam/xbox etc.. We really ran into big latency issues when the cron was still posting the updates. We generally saw the updates coming many hours later, and sometimes days later. I suspect that it's were running into a posting limit like you mentioned. Is there a posting limit? When we post the updates, we don't receive any errors. This has plagued me because I'm always assuming the problem is on our end, but I can never find any good reason for it not to be working. On Sep 2, 6:48 am, John Kalucki <[email protected]> wrote: > While we occasionally have update latency events (I think there was > one yesterday afternoon for a bit of extra latency over a few tens of > minutes), nearly all updates are applied to nearly timelines within a > few seconds. The common case is even less latency. Some variance can > be expected when a user with millions of followers updates -- there > may be a period of many seconds before the last follower gets updated > -- but not typically hours. > > I suspect that something else is wrong. Is the timestamp on the status > correct, or is it delayed too? If it's delayed, perhaps you are > running into a posting limit and there's a corner-case error condition > that your HTTP client isn't logging and alerting? > > -John Kaluckihttp://twitter.com/jkalucki > Services, Twitter Inc. > > On Sep 1, 11:28 pm, Andy Pirate <[email protected]> wrote: > > > So here's the deal. We've had the Twitter API integrated into > > Pwned.com for many months now. One problem we keep running into is > > that it updates our members Twitter WAY later. For example, it says so > > and so is playing on-line, but we processed that request hours ago and > > then it finally shows up on their feed. > > > I have requested whitelisting before, but they claimed it was approved > > and I don't think that it is. We've had to severely limit our > > integration with Twitter because of this reason. > > > Any help would be greatly appreciated. > > > Thanks > > > Andy
