That's the way it's supposed to work at any rate. Starting last week, all messages were identified as "from Web." There was nothing you could do to fix this minor nuisance. ("Minor" to most people anyway; third-party client developers may have a different outlook.) The solution required a fix from Twitter itself. Happily, this bug has now been fixed.

Have you ever attempted to refresh your Twitter listings and received a "bad request error"? This message has nothing to do with the politeness or moral value of your tweets. Rather, Twitter limits how often you can request to connect to its servers. The reason for the limit is to prevent their servers from being overloaded with too many requests.

Currently, the limit is 70 connections every hour. If you exceed that amount, you'll get the error and have to wait a bit before you can refresh again. Don't think that shifting to a different Twitter client, or shifting from your Mac to your iPhone, will work around this limit. The connection numbers for your account are tallied at the Twitter server, no matter where your tweets or refreshes may originate.

Seventy connections per hour may seem more than you need--but not necessarily. If you are using a Twitter client, it is likely set to refresh itself automatically after a given interval. For example, default setting is to refresh every 3 minutes. This may seem to translate into 20 server requests per hour. Unfortunately, as pointed out on this , each refresh counts as three server requests (one each for recent messages, replies and direct messages)! This means that the default settings alone account for 60 out of your 70-per-hour connection limit. If you often manually refresh or start posting several tweets in a row, you can easily surpass the limit.