On Tue, Oct 20, 2009 at 5:13 PM, Chad Etzel c...@twitter.com wrote:
Just to follow up. We have determined that this is a bug and the
engineering team is working to figure out how this snuck in. I'm
afraid I don't have an ETA on a fix, but we are working on it.
FYI how this snuck in is fairly
Bump.
On 20/10/2009, at 3:54 PM, TjL luo...@gmail.com wrote:
http://twitter.com/status/show/5008681027.xml| was entered with
newlines between the words. It does not show the newlines.
http://twitter.com/status/show/4999223282.xml shows that this was
working just a few hours ago.
Both were
As an aside; please don't bump threads on this list.
-- ivey
On Tue, Oct 20, 2009 at 12:58 PM, Tim Haines tmhai...@gmail.com wrote:
Bump.
On 20/10/2009, at 3:54 PM, TjL luo...@gmail.com wrote:
On Tue, Oct 20, 2009 at 2:11 PM, Michael Ivey michael.i...@gmail.com wrote:
As an aside; please don't bump threads on this list.
As an aside, how about someone answers the question rather than just
getting pissy at people who are trying to figure out how a change is
going to effect products
I've observed the same behavoir at least 10 hours ago and still seeing
it now.
--
Hwee-Boon
On Oct 21, 3:57 am, TjL luo...@gmail.com wrote:
On Tue, Oct 20, 2009 at 2:11 PM, Michael Ivey michael.i...@gmail.com wrote:
As an aside; please don't bump threads on this list.
As an aside, how
I don't know the answer, and I wasn't getting pissy.
I was (rather politely, in fact) pointing out that the folks from Twitter
have repeatedly asked us not to bump threads here.
Just because you're frustrated with a situation doesn't mean you should take
that frustration out on the others on the
We are investigating this internally.
Please don't bump.
-Chad
On Tue, Oct 20, 2009 at 4:44 PM, Michael Ivey michael.i...@gmail.com wrote:
I don't know the answer, and I wasn't getting pissy.
I was (rather politely, in fact) pointing out that the folks from Twitter
have repeatedly asked us
On Tue, Oct 20, 2009 at 5:13 PM, Chad Etzel c...@twitter.com wrote:
Just to follow up. We have determined that this is a bug and the
engineering team is working to figure out how this snuck in. I'm
afraid I don't have an ETA on a fix, but we are working on it.
Good to know it isn't a
