The October 2013 Platform Changes and their impact to Spring Social:
- Game Achievement API update
- Spring Social Facebook currently does not support the Game Achievement API and will not be impacted by this change.
- /USER_ID/likes default update
- This will not break the current API binding. However, in the current implementation, you will only be able to fetch the first 25 likes for a user. That's because none of the LikeOperations method accept a PagingParameters object to designate the offset and limit for the request. (See
- /POST_ID/likes update
- I've tested this extensively, both with October Breaking changes enabled and disabled, and see very little difference. Nevertheless, LikeOperations.getLikes() is missing proper paging support (it returns a PagedList, but there's no method where you can use the nextPage or previousPage properties to page through the likes). getLikes() should be overloaded to accept a PagingParameters to page through the results. This is the same work covered by
- Removing 'network' based privacy
- Spring Social Facebook currently does not support NETWORK privacy, so the removal of it at Facebook will have no impact on Spring Social Facebook.
- Removing the ability to post to friends' timelines via API
- The mechanism for posting to a friend's timeline is the same as posting to a Page timeline. Therefore, this functionality can't be removed without removing the ability to post to a Page's timeline. JavaDoc, however, should be updated to not mention that the owner of the timeline can be a user.
- FQL and Graph API limit=0 change
- To my knowledge, no API binding methods take advantage of the bug described where limit=0 will return all results. Therefore, no changes should be required in Spring Social Facebook. If, however, an application using Spring Social is taking advantage of this, they will need to change accordingly.