Cubicgarden.com
I switched over to Tweetdeck a while ago… I use to use Gwibber on my laptop/desktop machines and Peep on my Android phone but recently switched…
HTC Peep was ok but honestly it use to wind me up when it wouldn’t update when the storage was quite low. No warning either. Gwibber was great but I found it slow when adding lots of columns. I tend to have a column for all the people I’m following (home) one for replies (@replies) and finally one for Private messages (d msgs). On top of that I have searches for events and the such things. Tweetdeck handles these pretty much in its stride, but Gwibber use to do odd things.
I think it might have something to do with being connected to Twitter x2, Identi.ca, Facebook and other services.
The one thing I do miss from Tweetdeck is the ability to connect to a identica and status.net server. Instead there’s accounts for Facebook (which actually works very well) and Google Buzz. Honestly I’d switch out Buzz for status.net anyday.
I don’t know how the news Twitter might buy Tweetdeck will effect everything but it looks like status.net and even the open microblogging standard isn’t coming any time soon. I may switch back one day, specially if Gwibber 3.0 is as good as it could be.
Evan Prodromou who I finally met at FOSDEM recently, has been running a poll to find out whats the best character limit for microblogging.
For our flagship site, Identi.ca, which runs on the status.net cloud service and uses the 0.9.0 beta, we’d like to open up the discussion of what an appropriate character limit should be. Setting a site-wide limit is a community decision we’d like to leave in the community’s hands. In a conversation on Identi.ca we’ve solicited some candidate character limits that we’d like people to decide on.
- 140 is compatible with Twitter; in many languages a notice with 140 characters fits into a single SMS message*
- 280 can fit into two Twitter or SMS messages
- 300 is a fan favorite
- 420 is Facebook’s status limit and 3 Twitter tweets or SMS messages
- 500 is a little bigger
- 1000 is bigger than that
- Unlimited
- Other
So personally I think 300 is enough. 300 will hold a very long URI with room for query string values. Also having it about the size of two text messages seems about right. If you stick to ANSI only characters you usually get about 306 characters to text with (160+160 with overhead) on most phones. Unicode drops it down to 280 characters which still seems fairly close to 300. I’m also thinking 300 characters keeps things micro readable still.
The idea of a more structured microblogging with URIs as metadata in interesting but I think metadata should be inline and in plain view. Its one of the neat things about Microblogging, which would be a shame to remove. Also got to say anything more complex than the current microblogging setup would maybe cause too many problems with backwards compatible. Literate results are good, if you want metadata use blogging instead.
