Loquacious Apps

Bug fix release for a major bug with the TwitPic implementation and a couple of minor things:

• Fixed a bug where Loquacious would not upload any images from the Camera > Share > Loquacious and recent images from the pictures app causing you to receive a “TwitPic returned an error message.”
• Images uploaded to TwitPic from Loquacious now show “from Loquacious” instead of “from api” on the TwitPic website.
• The Edit User dialog box says “Edit User” instead of “New User.”
• Fixed a few minor issues with the regex that highlights links, @usernames, and #channels.

More nerdy details follow.

Issue #1: Long story short… I wrote and thoroughly tested and implementation of TwitPic that shouldn’t have worked before they moved to their new servers. Their old servers weren’t enforcing the Content-length requirement for multi-part form data. Their new servers do. In order to fix this, I was relying on Android’s media content provider to give me the length of the file because there’s no other good way to get that. There’s an issue that I was not aware of with Android returning a length of 0 for new images, which causes TwitPic to return an error since the file length was not 0. Since I wasn’t aware of that issue, I didn’t re-test all of the possible ways you can upload, thus letting this bug slip out. Totally my fault. Loquacious now forces Android to scan the image for file size whenever Android returns a length <= 0.

Issue #2: Funny story, actually. After waiting a couple of weeks and deciding it wasn’t worth it to hold out on releasing, I got the email with my source parameter less than a minute after I published 1.1 to the market.

Issue #3: Yeah, I’m a moron.

Issue #4: Because the regex that highlights links, @usernames, and #channels is by far the biggest load when displaying a list of Tweets, I’ve purposely kept them on the simple side. Since 95% of the links posted on Twitter are either URL shortened or from TwitPic, I can usually get away with this. Of course, after three months of not having a single issue with that, three separate posts had links that borked the morning after I published 1.1, so I’ve taken care of several other possible cases. I’m also enforcing at least 2 characters in a channel name now.