Thread: [SailfishOS] [Announce] Rockpool - Pebble daemon for Sailfish
View Single Post
ruff is offline ruff
2016-05-29 , 00:16
Posts: 207 | Thanked: 482 times | Joined on Mar 2016
#394
Originally Posted by ruff View Post
Account token - this is more tricky and more simple. This is unique user ID. It will be the same whatever number of times you generate new OAuthToken. Really - just pebble account id. Can be obtained from https://auth.getpebble.com/api/v1/me.json with proper OAuthToken.
Found a conflict in documentation. So here's excerpt from JSkit API docs:
A string that is guaranteed to be identical across devices if the user owns several Pebble or several mobile devices. From the developer's perspective, the account token of a user is identical across platforms and across all the developer's watchapps.
while here it states
The account token is a string that is guaranteed to be identical across devices that belong to the user, but is unique to your app and cannot be used to track users across applications.
which contradicts a bit with the above. Even though later is not official documentation it sill hints that accountToken is anonymized.
In the end I think the truth is in the middle and it should be safe to make accountToken a hash of the me.json->id + appinfo.json->companyName. That should match both statements more or less. Unique for user per all developer's apps and cannot be used to track users across *developers*.
But to make it really identical across devices we need to use same hash function. Or - again fetch this token from some other - yet unknown - API.
 

The Following 3 Users Say Thank You to ruff For This Useful Post: