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.
-Chad On Tue, Oct 20, 2009 at 4:51 PM, Chad Etzel <c...@twitter.com> wrote: > 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 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 list. >> >> -- ivey >> >> >> On Tue, Oct 20, 2009 at 2:57 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 they're building around Twitter's API? >>> >>> If Twitter is getting rid of whitespace, that means I can strip out a >>> bunch of code in certain places. >>> >>> I'd like someone to comment on this officially. >>> >>> TjL >> >> >