transitioning to the v2 API #105
Description
Last week Twitter announced the version 2 of their public API, which looks like a promotion of some of their "Labs" endpoints, plus some reimaginings of their API structure in general, into a new API surface. It seems like the launch of the API itself was delayed due to the security incident that also occurred last week, but it's worth tracking it as it means new work for egg-mode.
The first change i notice when looking at the Labs APIs is that they allow you to specify which fields you want to retrieve in the API call, which is great for extensibility but makes returning a statically-defined data structure (like we have been doing in egg-mode) difficult. On the other hand, this could also allow us to trim down our biggest structures, by (for example) returning only a screen name/ID for the author of a tweet instead of serializing the entire TwitterUser out.
I've yet to do a complete read-through of the current Labs APIs (not to mention whatever it will look like when they properly release the v2 API) but it does seem like there will be some rework that needs to happen to support them properly.