I think it will benefit all users of the library to document the method names for every call. While it's somewhat trivial to determine the method names it still required just an ounce of brain power. That ounce should be save for other tasks :).
It's been on my todo list to document them all, but I've been lazy :) On Nov 1, 3:21 pm, Michael Mokrysz <m...@46bit.com> wrote: > Thanks to both of you, having taken a better look at epitwitter's code > I'd have to agree that's it's best to switch. I still like to be able > to pretty much copy and paste urls from the documentation rather than > having think how to convert it into the (albeit ingenious) conversion > method EpiTwitter uses so I think I'll probably rewrite the __call > function a little but keep the rest of the code.
