---
title: 'TwitterThreads: Portland’s love affair with Twitter continues'
date: '2008-02-13T00:05:16-08:00'
type: post
word_count: 205
char_count: 1350
tokens: 267
categories:
  - API
  - CouldBe
  - Oregon
  - Portland
  - Twitter
  - TwitterThreads
tags:
  - CouldBe
  - Oregon
  - Portland
  - Twitter
---

# TwitterThreads: Portland’s love affair with Twitter continues

One of the biggest drawbacks of trying to follow [Twitter](http://twitter.com "Twitter") conversations is that Twitter tends to come at you in one stream. And if you’re following enough people, it’s a fire hose. That said, one of the biggest benefits of using Twitter is that, with the availability of the API, someone is going to figure out how to fix pretty much any Twitter “drawback” you can highlight.

Case in point: [TwitterThreads](http://www.twitterthreads.com/ "Twitter Threads") from Portland-based [CouldBe Studios](http://www.couldbestudios.com/ "CouldBe Studios"), [a one-night project](http://whatcouldbe.com/blog/?p=70 "Blog post on TwitterThreads development") that delivers Twitter conversations in—shockingly enough—threaded format. (Man, they should call this thing… oh wait, they already have.)

Developed by [Matt Beck](http://twitter.com/mattbeck "Matt Beck"), TwitterThreads provides a more conversational view of your tweets, allowing you to see multiple tweets from the same person grouped together or to more easily follow conversations as the @s start percolating.

To see it in action, visit [TwitterThreads](http://twitterthreads.com "Twitter Threads") where you can view the public timeline. Or, login and see how your conversation threads come together.