Matt, It appears that the timeline does not contain all the content. It is still missing the most recent tweet.
As an example, this tweet 23043372398673920 is shown in new twitter, but not in the website view. Thanks for the info though, Adam On Jan 6, 2:48 pm, Matt Harris <thematthar...@twitter.com> wrote: > Hey Adam, > > Thanks for raising this. The website isn't part of the API so we're not in a > position to fix or address the issue. That being said I have checked with > our user support team and know that they are tracking this very issue with > the engineering teams. > > From what i've been told the timeline should contain all the content, it's > just the timestamps are wrong. Does that match with your observation? > Best, > @themattharris > Developer Advocate, Twitterhttp://twitter.com/themattharris > > > > > > > > On Thu, Jan 6, 2011 at 11:08 AM, Adam Covati <cov...@gmail.com> wrote: > > We have a problem where some one was worried that their posts weren't > > making it from our application to twitter. After looking deeper I've > > found that a twitter page for a user is very different if you are > > logged in or not. > > > Please note: Below I refer to the page you see when not logged in as > > the 'public page', this is an 'old twitter' page, as opposed to the > > 'new twitter' view I see when logged in. > > > It appears the public page for one of our client's twitter accounts is > > cached right now and is currently 7 ours behind - this is not just on > > one computer, we've seen several computers loading the 'old' page. By > > 7 hours behind, I mean that a tweet time shows as '1 hour ago' on the > > page, but then shows as '8 hours ago' if you log in and view the page > > or if you click through on the time and view the actual status' page. > > Also a tweet that was posted about 3 hours ago doesn't show up at all > > the public page. > > > Might this be due to page caching or load balancing that is done on > > twitter's end for 'old twitter' but not done for 'new twitter'? > > > I can provide details or screenshots taken within seconds of each > > other if that helps, but if anyone else has seen this at all, or knows > > of this being normal that'd be helpful. > > > Thanks > > > -- > > Twitter developer documentation and resources:http://dev.twitter.com/doc > > API updates via Twitter:http://twitter.com/twitterapi > > Issues/Enhancements Tracker: > >http://code.google.com/p/twitter-api/issues/list > > Change your membership to this group: > >http://groups.google.com/group/twitter-development-talk -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
