all repos — h3rald @ a6d8dfd7e5a9a137232a6873b287ab6cc3ae1250

The sources of https://h3rald.com

Minor typo.
h3rald h3rald@h3rald.com
Thu, 05 Nov 2009 17:25:43 +0100
commit

a6d8dfd7e5a9a137232a6873b287ab6cc3ae1250

parent

de3cdda66d3f3bf16103bf78be155a75044bbde4

1 files changed, 1 insertions(+), 1 deletions(-)

jump to
M content/articles/journotwit-review.textilecontent/articles/journotwit-review.textile

@@ -17,7 +17,7 @@ The official Twitter page quickly became inadequate to manage my tweets, so I began to search for an alternative through the myriad of Twitter clients available out there, both web and desktop based. After trying out a few desktop clients, I decided to restrict the search to web clients only: between work and home, I may use up to 4 different computers and 3 different operating system, and I really didn't fancy the idea of keeping the _same_ client up-to-date everywhere -- even if such client existed.

Over the past months I tried dozens of different web-based Twitter clients, and narrowed the list of _must-have_ features to the following: * The interface should be simple to use and not too cluttered. -* I should be able to categorize tweets in columns ( la TweetDeck). +* I should be able to categorize tweets in columns (à la TweetDeck). * I should be able to know, when visiting the site, how many _new_ tweets I have to go through. * I should be able to mark tweets as read. * It should display media files (at least pictures) inline with the tweets.