View Single Post
Posts: 214 | Thanked: 140 times | Joined on Aug 2010
#310
Originally Posted by Self-Perfection View Post
First of all, thank you for the fix!

I've encountered two problems though:[*] Posting accuracy is broken again. Accuracy is posted but very rarely. Can it be caused by posting floating point value instead of integer as it were last time?
Possible - I had to re-code the entire posting-to-latitude coz it was frankly easier than trying to understand the strange google api for Oauth2... since I had hand-coded OAuth2 for all the other services, it was easier to just clone a lot of the code for FB and FS to the latitude service.

Tho, if you post an accuracy to latitude, latitude returns the value as a float?

Originally Posted by Self-Perfection View Post
[*] If zaploc-daemon is strated while the phone in offline mode and updating of auth token is required (due to expiration) then zaploc-daemon tries to get initial authorization via oauth2 and launches browser.
Yeah unfortunately the token expires after only one hour, which I find quite excessive (compare to the Gowalla token that expired after 2 weeks, or FB / FoureSquare that doesn't expire at all)

I'll see what I can do....

/Z