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 suspicious, given that there had
been some fairly prominent use of whitespace just a few hours before
this "bug" appeared:
I'm not alone in thinking the timing is suspicious, especially if this
wasn't some quickly undoable change. It works one way for years, then
"accidentally" gets changed but you can't figure out what happened or
how to undo it?