Handle the API rate limits properly

Is this something that would better be handled in the twitter library?
Isolate the API rate limit handling for reuse
Handle the rate limits when getting the user settings