This is ridiculous Erik.  There's no reason to purposely keep out functionality provided in by the Twitter API because you are still trying to figure out how you would use it.  I've made the endpoint generally available as it should be for users to decide how they would use it.

I was being facetious with the use of the word "sneak."  The addition of this code is perfectly reasonable, while any desire to prevent users of this gem from accessing this endpoint provided by twitter is in fact completely unreasonable.  It's so reasonable in fact, that I don't believe it warrants even a conversation let alone a separate pull request.