Thanks for pointing this out...I wasn't aware of this issue until you mentioned it. If you don't mind, could you report it as a bug at https://jira.springsource.org/browse/SOCIALFB? I'll definitely take a look at it.
How do you track the status of these things? Well, the best thing to do is to report the issue in JIRA (as mentioned above) and then when I (or anyone else) does any work on it, you'll be notified. Since it's a bug, it will definitely be worked on soon.
Know, however, that unless there's a huge demand for it, I'm not likely to cut a Spring Social 1.0.3 release for this bug fix. It's a bug, no doubt, but the fact that the token will actually be good for 60 days, it is not a high priority bug. (That is, if you assume the 10 days to be correct and renew every 10 days, it will still work.) Instead, I will move forward with it to be fixed in 1.1.0.BUILD-SNAPSHOT first and then 1.1.0.M1 when I cut that release (planned for the next couple of weeks).
Also note that as part of 1.1.0.M1, I plan to include a new feature to *automatically* handle invalid tokens regardless of why they are invalid (expired, revoked, etc). I'm about 80% complete with that work and hope to tie up loose ends in time for the 1.1.0.M1 release.
Spring Social Project Lead