Some have mentioned that "At Me" App doesn't show all @ replies, or
somehow misses @ replies.
I should explain how "At Me" pulls results.
Go to
http://search.twitter.com/. Type in @[username] where [username]
is your Twitter username. What you see is exactly what "At Me" pulls.
It pulls all *public* results for that search.
So, if you're not seeing some @ replies through "At Me," that person's
account may be set to private on Twitter.
The only way for "At Me" to get those private @ replies is to
authenticate as the user. In other words, I would need Twitter
usernames/passwords for people wishing to see their *true* @ replies
(what you see under your "Replies" tab on the Twitter web interface).
Since most people won't want to provide their usernames/passwords, I
can only pull what is public information.
In truth, your "Replies" tab doesn't even show all @ replies. If
someone includes @[username] in the *middle* of their tweet (anywhere
except as the first word), your "Replies" tab will not pull that
tweet. Strange, but true.
However, "At Me" *will* pull those tweets where the @[username] is not
at the beginning of the tweet. Again, any results you see on
search.twitter.com is exactly what "At Me" sees.
I think there is also some delay with
search.twitter.com, which is odd
because Twitter purchased Summize, so the results should be reflected
in real-time. It appears it's still using the API to pull results,
which is stupid because an official Twitter app should not have to use
the Twitter API!
So, if you don't see the @ reply right away (but you know it exists
because, for example, maybe you follow the person and you already saw
the update), wait a few minutes and try again. Summize (er,
search.twitter) should catch up.