@jpabartholomew @tom_forsyth My address book has 300 people in it. It could send it compressed to the client on load in milliseconds.
-
This Tweet is unavailable.
-
This Tweet is unavailable.
-
This Tweet is unavailable.
-
This Tweet is unavailable.
-
This Tweet is unavailable.
-
-
Replying to @cmuratori
@jpabartholomew@tom_forsyth There is _absolutely no reason_ why it should be anything other than instantaneous to complete.1 reply 0 retweets 0 likes -
Replying to @cmuratori
@jpabartholomew@tom_forsyth If someone had one hundred thousand people in their address book, then maybe I could see some argument.1 reply 0 retweets 0 likes -
This Tweet is unavailable.
-
Replying to @jtwxtr
@jpabartholomew@tom_forsyth I would also argue that even if it's not instant, they "picked" the absolute worst possible behavior.1 reply 0 retweets 0 likes
@jpabartholomew @tom_forsyth It should be a given that a system should never complete to a name _that could not have been matched_.
2:49 AM - 26 Nov 2013
0 replies
0 retweets
0 likes
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.