@oliphant @rootfake So it seems pretty clear Twitter's Android team is smaller than the iPhone team. Under old management, new features would debut on the iPhone and take 2-3 months to make it over to Android. This was actually great because (1) Twitter features always suck and (2) any kinks were ironed out by the time Android got them.
But this feature landed on Android within days of landing on iPhone, close enough they could've been submitted to the app stores simultaneously.
@oliphant @rootfake The atypical release cadence, combined with the fact a MAJOR and easily caught (it is possible the bug is caused by my Android version or third party keyboard, but come on! Android QA means configuration testing!) new bug, seems to me to imply that an established release process was circumvented, probably at the demand of a 51-year-old child with localized absolute power
