blogger api endpoints unstable, need resilient retry mechanism

I often get SSLExceptions with "read timed out" when accessing Blogger API using the Google API Java Client.

I wrote a workaround for that. However:

for proper retry mechanisms, the API needs to support some sort of a unique transaction code to detect duplicates, ie. when creating new Blogger posts to avoid creating duplicates. For that reason the retry mechanism should be embedded into the Google Client itself.

I also found people in the Android Google Play Store complaining about unreliable API connections when using the official Google Blogger android app.