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:
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
wrote:
> It has not happened yet.
>
> The most recent parts of the discussion are in
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=gst&q=mark+mcbride#fcac7b30b85413e4
Thanks,
Taylor
On Tue, Apr 20, 2010 at 6:20 PM, mattarnold19
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
wrote:
> Hi Matt,
>
> I'm not able to see the issue at the moment -- can you provid
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, M
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, mattarnold1
Excellent job!
Many thanks,
Alan
On May 7, 9:38 pm, Doug Williams 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
I noticed the freeze on one of my scripts that monitors it yesterday.
Glad the issue has been resolved, everything working good here.
On Thu, May 7, 2009 at 11:04 AM, Sanjay wrote:
>
> I'm not entirely sure but this may be somewhat my "fault". Yesterday
> I noticed two different tweets in the p
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 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
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 wrote:
> Matt,
>
> As Doug mentioned, we're working on fixing the public timeline. I hope
> we c
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.
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 wrote:
>
> I've been seeing a ver similar issue since yesterday with the partner
> feed - a very small
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).
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
15 matches
Mail list logo
