A while ago, I blogged about Quotably’s lack of conversation context. Quotably was designed to solve the problem of sparse Twitter conversations. It did its best to generate a threaded view of the twitter conversation. As I stated before, it failed in many cases and added frustration to a seemingly unfixable problem. Today I found a new feature on Quotably that I want to share:

Now you are able to (manually) fix threads that Quotably gets wrong. The context returns! Even though it’s a manual process which may not jive for some users, at least you have the option of fixing the conversation. I like this. While it’s not the most elegant solution, it does provide a realistic approach to fixing a design issue with Twitter. Quotably gets a nod of respect from yours truly for this improvement. Here’s a video I made which depicts the process (and also a perfect example of a broken thread):

See room for improvement? So do I. The CAPTCHA process needs tweaking. The system leads you to believe you are inputting a correct CAPTCHA when you are apparently not. It is kind of frustrating, but workable. We’ll see if it gets addressed in a later iteration.

Related posts:

• Quotably Needs Conversation Context
• Tweetree’s Value Is Embedded Media
• Twitter User Streams: Real-Time Is Back?
• BingTweets Mashes Up Twitter Trends And Search Results
• Socialmedian Improves User Experience With Filters