Currently sitting pretty at version 1.3.6, Yatca has included photo uploading along with SMS and email forwarding and many, many other bug fixes which are quite extensive. Be sure to check out the full list of revisions after the jump or if you're already interested in just grabbing the download you can hit bit.ly/yatca and get the updated version. Remember folks, this is just for devices running a version 4.6 OS.
Yacta v1.36 Changelog
- Photo support has been completely reworked. Yatca no longer attempts to integrate directly with the device camera. Instead it presents a gallery of all photos on your device from which you can choose one to be uploaded. There’s also a button to launch the built-in Camera application and any photos taken will be detected and added to the gallery when you close the Camera application and return to Yatca. N.B. When you open the photo gallery for the very first time it will be very slow. This is because it has to create thumbnails for all the photos. Painful I know but sadly unavoidable because RIM doesn’t share the inner workings of their ‘thumbs.dat’ file so Yatca has had to reinvent the wheel. Please remember too that when it comes to the reliability of uploads, Yatca is completely at the mercy of (a) your carrier and (b) TwitPic.
- When reading a tweet you’ll notice that the ‘Retweet’ button has become the ‘Forward’ button. When you invoke it, you’re asked if you want to forward by retweet, SMS or email. Choosing SMS or email invokes the relevant application.
- Also when reading a tweet you’ll notice that there’s now an indication of when the tweet was sent. I follow the modern convention of displaying a relative description (e.g. 15 minutes ago) for tweets in the recent past and a date for tweets older than one week.
- Previously, Yatca did not correctly identify a reply from somebody you follow unless it was a reply to a specific tweet from you. So if a friend simply tweeted “@username blah blah blah” that was not filed as a reply but rather as an update, causing replies to be missed on occasion. This has now been fixed.
- If a user has been offline for an extended period of time Yatca will now stop playing catch-up once it has downloaded the maxium number of tweets it can store, which is 1,000. Previously it would keep going way back to clear the backlog, which was pointless because the user would never actually get to see tweets beyond the 1,000 most recent.
- The ‘Mark All Items Read’ command on the menu is now the ‘Mark All Yatca Items Read’ command. This is just to avoid confusion about what the consequence of running the command might be!
- There is a new option to hide the display of the @user in the reply dialog. Please note that if you choose to do this Yatca will still prepend @user to the text of your tweet before sending.
- An awful lot of the effort that went into this version was spent in what we programmers like to call “refactoring”. This is just a fancy way of saying that I replaced all the bad code written in a hurry with something that I could stand over. Although much of this work is invisible to the end user, it has resulted in a few significant performance improvements here and there. But perhaps more importantly, the refactoring should make it easier for me to add future enhancements to Yatca.
Don't listen to AT&T: Your phone isn't going to stop making calls
AT&T customers have been receiving warnings from the carrier saying that their phones will soon stop making calls. That's technically true, but the network change isn't coming until 2022. Here's what you need to know about the transition to VoLTE (HD Voice) on AT&T.