You can add location information to your Tweets, such as your city or precise location, from the web and via third-party applications. You always have the option to delete your Tweet location history. Learn more
Yeah, no. The last ticket I saw on your tracker about AAC from another user, they were rudely and incorrectly accused of not reading the docs (while that person had in fact incorrectly read the ticket). The AAC encoder dev has also accused me of making up audiophile BS.
I've seen enough attempts to bring this up, from myself and from others. Ball's in your court. That encoder sucks, and anyone doing basic tests with a few nontrivial samples can see that. If you pretend everything's fine while being rude to those who notice, that's your problem.
Unfair to tar the whole project based on the actions of one dev
Three devs actually (the one who replied to the ticket without reading it, the one who closed it NEEDINFO after that again without reading, and the one I interacted with). I have no problem with the project as a whole, but *this* particular encoder seems to bring out trouble.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.
