Along with all the bug fixes and fine tuning that appear in most releases, this release included some new functionality in particular focussed around interfacing with Twitter.
We already supported login via Twitter, this release built on that support to show how we can utilise the Twitter API to automate interacting with Twitter.
The bulk of this release utilises the Twitter API primarily to automate following (and unfollowing) Twitter users.
To generate the list of Twitter users to follow we query Twitter to get the existing followers of a specified Twitter account. eg. I want to follow every Twitter account that follows @springcentral.
Once we have that list we can incrementally follow those Twitter accounts, bearing in mind that we need to be aware of Twitter's rate limiting.
In addition to following accounts, we also implemented an unfollow strategy. Any Twitter account that we followed, that didn't follow back within 14 days should be automatically unfollowed.
Even if you don't need this functionality it still provides a good example of how you can utilise the Twitter API to communicate with Twitter and some of the challenges involved.
Additionally we also cache details of Twitter users to the database to avoid calling the Twitter API every time we need Twitter account details.
This not only provided good examples of how to utilise the Twitter API, but also introduced scheduling and how to invoke methods at a regular interval.
Previously all the application configuration and wiring was done in the ObistartApplication class. This is ok for small applications, but as your application grows you will want to break up your configuration into separate classes for easier management.
In this release we have moved social configuration into a separate class (SocialConfiguration).