Posted by & filed under General.

I know, you’ve got a new iPhone and you want to back fill your timeline with old messages… but you find that you’ve reached a limit or it looks like the App has broken trying to load extra pages.

In fact your question is better posed to Twitter themselves who set an abitary limit on the number of Tweets you can retrieve for certain timelines.

The limits as we understand them at the time of writing are as follows

  • Home timeline (thats your main timeline of people you follow): last 800 tweets
  • Mentions timeline: last 800 tweets
  • An individual user’s timeline, that is tweets a user has made or retweeted themselves: last 3,200 tweets
  • Search: last week’s worth of tweets

Don’t worry all your old tweets still exist inside Twitter’s database, they simply don’t let external clients access anything beyond that listed above.

Posted by & filed under iPad, iPhone, Mac.

When loading Tweetings after having used it already i.e. it’s not a new installation, then Tweetings tries to load all missing Tweets from the last tweet you saw.

Sometimes it’ll load all of them and sometimes you’ll see a gap. A gap means there are more Tweets than we can retrieve in a single call to the Twitter API. Tapping the gap goes off and loads some more, etc.

Now the Twitter API has a maximum number of tweets that you can call in a single api request. That number is 200.

Tweetings is only loading 100 though

In a recent update to both Tweetings for iPhone and Tweetings HD for iPad this number changed to 100 instead of 200, why is this.

Well Twitter are shortly going to wrap ALL url’s on Twitter with their own shortener called (see

Now if we didn’t make the changes we have already, then when this is switched on by default you won’t easily be able to tell where a link leads, if a Tweet has an image in it, if it has TwitLonger content associated with it, etc.

Twitter have dealt with this through a system called entities. In short this is a system we can enable in the background that allows us to decode these links for display purposes so we can still analyse these links for images, etc.

Why can’t you load 200 tweets though

We tried this in testing and 9 times out of 10 the first time you called your timelines Twitter would return an HTTP status code of 502. To you and me, this is the code for the Over Capacity / Fail Whale. Calling the timeline a second time would actually load it.

We asked Twitter about this and their response was

The count=200 limit was created when the timelines contained less information. As Twitter has grown and added more data to the timelines the amount of processing required has increased. What this means to developers is including all the retweets and entities takes too long when asking for 200 statuses at once and will result in a 502 error the first time the data is requested.

The current workaround is to request less than 200 per page and instead request more pages. Alternatively use one of the Streaming API methods to receive data and use the REST API for other interactions.

We are working to allow this amount of data to be returned in one request however it requires a longer term solution.

Updating the summary to better reflect the issue and marking as longterm

There you have it, straight from Twitter themselves. If you want us to be able to provide a stable client, but also be able to unwrap the url shortener we had to make a tough decision to lower the default amount of Tweets you can call on refreshing a timeline.

You can turn this off in the settings. It’s called ‘Expand URLs’ but we really don’t recommend you do so.

What about the Tweets per Page setting

This setting is exactly what is says. It’s for loading Tweets on SUBSQUENT pages and is totally ignored for refreshing timelines. However this should also only have a maximum value of 100 and not 200 too if you don’t want to see lots of over capacity errors!

But I still get Over Capacity errors at 100 tweets

It’s likely that an entity is corrupt in your timeline and it’ll pass in time, or that Twitter timed out requesting those entities and by the time you refresh it’s been generated and will work.

However that being said there is absolutely nothing we as API developers can do about it, the error firmly lies with Twitter themselves, complain to them about forcing on us

Can I turn this off?

Yes you can through the ‘Expand URLs’ setting in the app itself.  However if you do this no link will be decoded… which means when Twitter turns this on for EVERY link, as is their plan to do so, you’ll no longer know what is an image link, twitlonger, etc and they’ll open in a web browser instead.

Posted by & filed under iPad.

It’s been far too long to get this update out, and for that we apologise.

There were some stability issues with version 1.2.x which should now be resolved with the release of version 1.3.

The full change log can be found here but here is a quick summary of what’s new in 1.3:

  • User Interface and Experience has been overhauled, improved and refreshed.  Tweetings for iPad should look even more gorgeous now!
  • You can now selectively post to Facebook directly from the compose screen
  • Search screen overhauled, now saved searches are cached and you can browse suggested users
  • You can upload multiple attachments to a Tweet now, and with Posterous support added there is even more choice
  • Contacts, the first 100 retrieved from Twitter, are cached on the compose window to make it faster to select a user to sent a message to
  • We’ve re-written our entire XML and Location backend code to make it faster, and closed a number of memory leaks in the process
  • Of course, most importantly, a brand new icon. This is now the unified icon for Tweetings on both iPad and iPhone, version 3.1 for iPhone will also sport this lovely new icon :)

We’d advise taking a look at the change log if you really want to see everything we’ve changed but other wise just update 1.3 and enjoy!

Retina Display

Posted by & filed under iPhone.

As you may (or may not be aware) the iPhone 4 will have what Apple is calling, the Retina Display.

This is a high resolution display with more pixels than your eye can physically see. Tweetings for iPhone as it is now will still work and look pretty much the same as it is now.

Upgrade to Tweetings 3.1 (when it’s submitted and approved) and you’ll immediately see some amazing, sharp, images.

Here is just a little teaser at full size

Posted by & filed under iPhone.

Tweetings 3 for iPhone has been approved by Apple and is available from the iPhone AppStore.

This is a big release for Tweetings, with many internal core changes and many changes noticable to you, the user.

New Features

  • Add and manage multiple file attachments to a Tweet
  • Update your name, description, location and website from your profile
  • Tap your profile avatar when on your profile to select a new image from your photo library
  • Verified users will display the verified logo in lists of users
  • Protected users will display a padlock in lists of users
  • Saved searches are now cached on the search page
  • Now displays search with a mix of popular and recent tweets
  • Time can be changed in timeline between 12 hour, 24 hour or relative format
  • New popup menu when tap and hold a timeline status or tapping the user’s avatar in the timeline


  • Redesigned search screen
  • Redesigned the read tracker handling routine
  • Migrated TwitPic, MobyPicture & Twitgoo image uploads and TwitVid & MobyPicture video uploads and MobyPicture audio uploads to oAuth Echo. They will no longer require you to give Tweetings your password
  • GeoLocation manager re-written to improve GPS location
  • Twitter password setting removed from Settings page

Bug Fixes

  • Follow button disabled on user’s own profile
  • One character Tweets would crash when posting

Posted by & filed under iPhone.

We don’t normally reveal what is coming in future versions of Tweetings, but Tweetings 3 is a bit different, there is a lot of under the hood changes and quite a few new features we think you’ll love.

First up is oAuth Echo support. If you haven’t read our post about oAuth Echo, then please do so.

Next we have the features people have been asking for….

  • Multiple attachment support… yes it’s here and it’s done fantastically.  What do we mean by that, well if you are uploading 3 pictures and one fails, it will stop, let you fix it and reupload but only upload the ones that failed. You can preview attachments and individually remove them
  • Update your own profile, including your profile photo
  • Totally redesigned search page that we think you’ll love
  • Suggested users
  • Totally redesigned read tracker so you’ll have no more reopening Tweetings to discover messages you marked as read as unread again

Quite a few more features, changes and bug fixes too but we can’t spoil all the surprises can we?


Posted by & filed under iPad, iPhone.

On the 30th June 2010, Twitter is removing something called Basic Authentication.

Basic Authentication is a simple way of interacting with a user’s Twitter account, however there are problems with this, your Twitter username and password and submitted with each request and the application has to store this information.

If that service became compromised then your Twitter login information could be in the hands of someone else.

Don’t fret as Twitter have had a more secure service for sometime called oAuth. oAuth is a good thing.

  • you don’t have to change your account details in a client if you change your password;
  • your login is performed directly on Twitter’s website and not stored in the application at all

Tweetings has supported oAuth logins since day one… so what’s the reason for this post?

Push Notifications

Quite early on we migrated our push notifications to oAuth instead of Basic Authentication, so you should notice no difference in your push notifications after the deadline

Image, Video & Audio Uploading

You are most likely to notice the issue when trying to upload an image to services such as TwitPic, yFrog, etc

At the moment most of these services require your login information and use Basic Authentication.  Twitter has developed a system called oAuth Echo to allow these types of services to carry on working after the deadline.  Of course the Twitter Client also needs to update it’s code to cope with oAuth Echo too.

Any clients and/or media hosts that haven’t switched to oAuth Echo will in most likely hood cease to work correctly after the deadline

oAuth Echo & Tweetings

In version 3.0, coming soon, we have implemented oAuth Echo in Tweetings.

As of the time of writing, the following media providers are also oAuth Echo enabled and will automatically carry on working after 30th June 2010, so long as you are using Tweetings 3.0 or later


  • TwitPic
  • Twitgoo
  • MobyPicture
  • yFrog


  • TwitVid
  • MobyPicture
  • yFrog


  • MobyPicture

We will carry on integrating other services once they make the switch but after 30th June, if you find your favourite provider has ‘stopped’ working then please switch to one of the list above (which we will keep up-to-date) to carry on uploading.

We will remove ANY providers from Tweetings that haven’t made the switch after the deadline

Update: Twitgoo has been added to the list of supported oAuth echo providers
Update 2: MobyPicture support for image, video & audio
Update 3: yFrog supported added to Tweetings for iPad 1.3.  It was too late for Tweetings 3 but it will be added in an update


Posted by & filed under iPad.

Tweetings for iPad version 1.2 has been approved and is available from the App Store

New Features:

  • Default theme enhanced
  • Gap detection in cached timelines
  • Tweet Rough Location, this will allow you to Tweet from your location without giving exact geo-coordinates

Bug Fixes:

  • Possible crash changing between Inbox and Sent on DM timeline
  • Quoted message below the compose field when replying to a Tweet or DM would badly stretch when switching from portrait to landscape mode
  • Cosmetic changes to settings screen


Posted by & filed under iPhone.

Tweetings for iPhone version 2.5 is now available from the App Store.

New Features:

  • New theme – Shadows Evolved
  • Tap and hold a timeline status to view the popup menu (or as previously tap a user avatar)


  • Change trend definitions to

Bug Fixes:

  • Quoted message below the compose field when replying to a Tweet or DM would badly stretch when switching from portrait to landscape mode
  • Cosmetic changes to settings screen
  • Disable the ReTweet button in a direct message view
  • Crash on pulldown on sometimelines affecting some users
  • Selecting MobyPicture as a video provider from can cause settings page in app to crash
  • Tweetings Manual close button didn’t allow navigating back to previous sections
  • Compose contacts list now responds to landscape mode
  • Trapped a search geolocation crash on iPhone OS 4.0
  • Made table footer views iPhone OS 4.0 compatible
  • Compose screen OS 4.0 compatible
  • Made Facebook Connect integration OS 4.0 compatible
  • Handle invalid user tag in user XML from Twitter (Twitter issue tracker 1617)
  • User title bar not resizing correctly on a profile under OS 4.0