It seems with the (new ?) publish platform that we do not need to use the Twitter gem, we can take the status, timeline, list or search url and pass straight to this api.
Pros:
No external dependencies, just a json api - remove the Twitter gem
Extra features I have wanted - timeline, tweet button
No auth required - remove code for API keys
No rate limit - remove caching code?
Existing format of public api works - drop the api type, the params still applicable and correct
Better to understand (?) - we use the Twitter gem that supports posting, updating, etc and things we will never need, this gem is now a jekyll extension of the publish platform, we can publish twitter stuff in jekyll pages. Simple.
Cons:
Twitter gem hides the Twitter API nicely, now we would be directly coupled to their API, any major changes their end mean we break. What happens if they decided to shut it down?
It seems with the (new ?) publish platform that we do not need to use the Twitter gem, we can take the status, timeline, list or search url and pass straight to this api.
Pros:
Cons: