The public_timeline is updating correctly again. @Hwee-Boon: that email as a bit premature. We will announce via @twitterapi and this list when the push feed is available to the world at large.
Thanks, Doug ---------------------------------------------------------------- Doug Williams | Platform Support | Twitter, Inc. 539 Bryant St. Suite 402, San Francisco, CA 94107 http://twitter.com/dougw On Thu, May 7, 2009 at 10:16 AM, Hwee-Boon Yar <hweeb...@gmail.com> wrote: > > Hmm.. when did the Streaming API come about? I see Firehose mentioned > in there, OK that's known. What's Spritzer? (I read the description > and tested it). > > - > Hwee-Boon > > On May 8, 12:39 am, John Kalucki <jkalu...@gmail.com> wrote: > > Matt, > > > > As Doug mentioned, we're working on fixing the public timeline. I hope > > we can get that updating again shortly. > > > > As a workaround, you might consider an early migration to the > > Streaming API. The /spritzer resource should have about the same > > amount of data, but in an easier to consume format. So far the > > availability has been very good, and the latency very low. > > > > -John > > > > On May 7, 6:01 am, mattarnold1977 <matt.arnold.1...@gmail.com> wrote: > > > > > > > > > I just checked the log on my server and noticed that the public time > > > line has been putting out the same status information since around 5 > > > o'clock yesterday. Is this a known issue? > > > > > -Matt >
