[twitter-dev] Re: Public Timeline Frozen
Taylor, I have a sample from my log. It's not very detailed, but at least you can see that it's happening at random times. I am waiting a full minute before hitting the timeline, so it's not that. Let me know your thoughts. 4/22/2010 7:22:21 PM~Duplicate Message ID: 12667336000 4/22/2010 7:28:16 PM~Duplicate Message ID: 12667634000 4/22/2010 7:29:18 PM~Duplicate Message ID: 12667683000 4/22/2010 7:37:20 PM~Duplicate Message ID: 12668102000 4/22/2010 7:41:17 PM~Duplicate Message ID: 12668312000 -Matt On Apr 21, 1:53 pm, mattarnold1977 matt.arnold.1...@gmail.com wrote: Taylor, That's odd then because I'm seeing duplicate status id messages in my log. I'll have to dig deeper to see which ID is being repeated to give you an example. -Matt On Apr 21, 10:45 am, Taylor Singletary taylorsinglet...@twitter.com wrote: It has not happened yet. The most recent parts of the discussion are in this thread:http://groups.google.com/group/twitter-development-talk/browse_thread... Thanks, Taylor On Tue, Apr 20, 2010 at 6:20 PM, mattarnold1977 matt.arnold.1...@gmail.comwrote: Taylor, I just remembered that you were planning to change the generation of status ids. Has that already occurred? If so, where is the documentation on that again? -Matt On Apr 20, 10:14 am, Taylor Singletary taylorsinglet...@twitter.com wrote: Hi Matt, I'm not able to see the issue at the moment -- can you provide some more details like examples of duplicate status ids? The public_timeline endpoint is cached for 60 seconds, so it will remain stagnant if you're requesting it more often than that. Taylor Singletary Developer Advocate, Twitterhttp://twitter.com/episod On Tue, Apr 20, 2010 at 4:44 AM, mattarnold1977 matt.arnold.1...@gmail.comwrote: It looks like the public timeline api is reporting the same statuses over-and-over again. This started sometime yesterday (4/19) and continues today. Is anyone else experiencing this issue? Thanks, Matt -- Subscription settings: http://groups.google.com/group/twitter-development-talk/subscribe?hl=en
Re: [twitter-dev] Re: Public Timeline Frozen
It has not happened yet. The most recent parts of the discussion are in this thread: http://groups.google.com/group/twitter-development-talk/browse_thread/thread/5152a34a8ae6ccb6/fcac7b30b85413e4?lnk=gstq=mark+mcbride#fcac7b30b85413e4 Thanks, Taylor On Tue, Apr 20, 2010 at 6:20 PM, mattarnold1977 matt.arnold.1...@gmail.comwrote: Taylor, I just remembered that you were planning to change the generation of status ids. Has that already occurred? If so, where is the documentation on that again? -Matt On Apr 20, 10:14 am, Taylor Singletary taylorsinglet...@twitter.com wrote: Hi Matt, I'm not able to see the issue at the moment -- can you provide some more details like examples of duplicate status ids? The public_timeline endpoint is cached for 60 seconds, so it will remain stagnant if you're requesting it more often than that. Taylor Singletary Developer Advocate, Twitterhttp://twitter.com/episod On Tue, Apr 20, 2010 at 4:44 AM, mattarnold1977 matt.arnold.1...@gmail.comwrote: It looks like the public timeline api is reporting the same statuses over-and-over again. This started sometime yesterday (4/19) and continues today. Is anyone else experiencing this issue? Thanks, Matt -- Subscription settings: http://groups.google.com/group/twitter-development-talk/subscribe?hl=en
[twitter-dev] Re: Public Timeline Frozen
Taylor, That's odd then because I'm seeing duplicate status id messages in my log. I'll have to dig deeper to see which ID is being repeated to give you an example. -Matt On Apr 21, 10:45 am, Taylor Singletary taylorsinglet...@twitter.com wrote: It has not happened yet. The most recent parts of the discussion are in this thread:http://groups.google.com/group/twitter-development-talk/browse_thread... Thanks, Taylor On Tue, Apr 20, 2010 at 6:20 PM, mattarnold1977 matt.arnold.1...@gmail.comwrote: Taylor, I just remembered that you were planning to change the generation of status ids. Has that already occurred? If so, where is the documentation on that again? -Matt On Apr 20, 10:14 am, Taylor Singletary taylorsinglet...@twitter.com wrote: Hi Matt, I'm not able to see the issue at the moment -- can you provide some more details like examples of duplicate status ids? The public_timeline endpoint is cached for 60 seconds, so it will remain stagnant if you're requesting it more often than that. Taylor Singletary Developer Advocate, Twitterhttp://twitter.com/episod On Tue, Apr 20, 2010 at 4:44 AM, mattarnold1977 matt.arnold.1...@gmail.comwrote: It looks like the public timeline api is reporting the same statuses over-and-over again. This started sometime yesterday (4/19) and continues today. Is anyone else experiencing this issue? Thanks, Matt -- Subscription settings: http://groups.google.com/group/twitter-development-talk/subscribe?hl=en
[twitter-dev] Re: Public Timeline Frozen
Taylor, I just remembered that you were planning to change the generation of status ids. Has that already occurred? If so, where is the documentation on that again? -Matt On Apr 20, 10:14 am, Taylor Singletary taylorsinglet...@twitter.com wrote: Hi Matt, I'm not able to see the issue at the moment -- can you provide some more details like examples of duplicate status ids? The public_timeline endpoint is cached for 60 seconds, so it will remain stagnant if you're requesting it more often than that. Taylor Singletary Developer Advocate, Twitterhttp://twitter.com/episod On Tue, Apr 20, 2010 at 4:44 AM, mattarnold1977 matt.arnold.1...@gmail.comwrote: It looks like the public timeline api is reporting the same statuses over-and-over again. This started sometime yesterday (4/19) and continues today. Is anyone else experiencing this issue? Thanks, Matt -- Subscription settings: http://groups.google.com/group/twitter-development-talk/subscribe?hl=en
[twitter-dev] Re: Public Timeline Frozen (Again)
This should be fixed. The database the public timeline service was pointing to went down. This problem has been fixed and a permanent/dynamic solution was put in place to ensure this doesn't happen again. Thanks, Doug -- Doug Williams Twitter Platform Support http://twitter.com/dougw On Sun, May 10, 2009 at 12:11 PM, Doug Williams d...@twitter.com wrote: This is the second report I am seeing. I'll open a ticket. Given that it is the weekend it may take a few hours to restart. I'll update this thread with any information. Thanks, Doug -- Doug Williams Twitter Platform Support http://twitter.com/dougw On Sun, May 10, 2009 at 6:31 AM, mattarnold1977 matt.arnold.1...@gmail.com wrote: Not sure if this is an outcome of the site maintenance, but it looks like the public timeline has been sending out the same statuses since about 9:20pm on 5/8/09. The timeline was frozen last week, but was fixed. Thus, I'm guessing this is a result of the maintenance that was just performed. Please let us know if this is a known issue.
[twitter-dev] Re: Public Timeline Frozen (Again)
This is the second report I am seeing. I'll open a ticket. Given that it is the weekend it may take a few hours to restart. I'll update this thread with any information. Thanks, Doug -- Doug Williams Twitter Platform Support http://twitter.com/dougw On Sun, May 10, 2009 at 6:31 AM, mattarnold1977 matt.arnold.1...@gmail.comwrote: Not sure if this is an outcome of the site maintenance, but it looks like the public timeline has been sending out the same statuses since about 9:20pm on 5/8/09. The timeline was frozen last week, but was fixed. Thus, I'm guessing this is a result of the maintenance that was just performed. Please let us know if this is a known issue.
[twitter-dev] Re: Public Timeline Frozen
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 On May 7, 3:01 pm, 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
[twitter-dev] Re: Public Timeline Frozen
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: 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
[twitter-dev] Re: Public Timeline Frozen
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 On Thu, May 7, 2009 at 7:19 AM, Alan alanev...@gmail.com wrote: 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: 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
[twitter-dev] Re: Public Timeline Frozen
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
[twitter-dev] Re: Public Timeline Frozen
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
[twitter-dev] Re: Public Timeline Frozen
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
[twitter-dev] Re: Public Timeline Frozen
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
[twitter-dev] Re: Public Timeline Frozen
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 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
