Public Timeline Frozen

[mattarnold1977]

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

[Alan]

To give you an impression of the scale of this issue, of the last 10
requests for the feed, I have received 5 repeats each of 2 distinct
feeds:

The first begins with status 1718278475 , and is malformed, due to the
presence of an end-of-medium character in status 1718277608
The second begins with status 1718273418

Both statuses are from yesterday (6th May), although we are now 16
hours into the 7th of May.

The feeds were requested once per minute for 10 minutes, and repeats
are not consecutive, but rather interleaved, I also have many
instances of the same malformed (first) feed over the last 24 hours.
I don't have dumps of those feeds yesterday, but given that the xml
parser reports an invalid char at the same line/column, we can assume
that it's the same feed.

I have essentially received no new statuses since yesterday.

Hoping we can solve this issue soon. Please contact me if you need
more data. Many thanks,

Alan

[Alan]

I've been seeing a ver similar issue since yesterday with the partner
feed - a very small number of feeds are repeating over and over,
including one containing malformed XML (which makes it nicely obvious,
as it shows up in error logs with an invalid character at the same
line/column each time). The repeats are not necessarily consecutive,
are separated by minutes, hours even.

Please contact me if I can help by supplying more data. Many thanks,

Alan

On May 7, 3:01 pm, mattarnold1977 <matt.arnold.1...@gmail.com> wrote:

[Doug Williams]

We're having a look. I'll update this thread when it is taken care of.

Thanks,
Doug
--

Doug Williams
Twitter Platform Support
http://twitter.com/dougw

[John Kalucki]

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

[Hwee-Boon Yar]

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

[Doug Williams]

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

[Sanjay]

I'm not entirely sure but this may be somewhat my "fault". Yesterday
I noticed two different tweets in the public timeline that were
attached to protected accounts. I don't think they were an effect of
the accounts going from public->private since I caught them right
after they showed up and saw the accounts were protected. I emailed
Twitter at 4:36pm and then another one at 5:16pm (EST). That *may* be
the reason.

That said, I'm glad I'm not the only one noticing that the public
timeline was frozen. I thought I was crazy for a while yesterday and
then started looking at other options (none of which have worked out
that well).

Sanjay

[Josh Roesslein]

I noticed the freeze on one of my scripts that monitors it yesterday.
Glad the issue has been resolved, everything working good here.

[Alan]

Excellent job!

Many thanks,

Alan

On May 7, 9:38 pm, Doug Williams <d...@twitter.com> wrote:
> 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 94107http://twitter.com/dougw