All the other webservices will store info stored by USER ID, there is no reason to do otherwise. While the login service is sorted out, I will accept the user ID in plain text format and use that for the DB table. As soon as the login service is sorted, it will return a userID when authenicating. Thus no changes will be made to the DB when we convert to using the login service.
What is the reason for not recording/using userIDs? I dont see the need to be so anymous. If people are worried about security/personal issues, dont use the webservice.
I think that people are generally sceptic to location services so anonymity will propably be the biggest issue with a service like this.
So I think that the sucess of a service like this would be based on trust to the system and the only way to do that is anonymity (at least thats my opinion).
Personally I'd like to have a service like this but I'd prefer if I could run it at my own personal server rather than uploading the data somewhere else.
Edit: But it should like stated earlier in this thread be separated between localisation data used for traffic and other public things and private data used for logging that the user can access and use to his likes.
The source will be open. All you need to do is edit to remove the saving of the userID and upload to your own server. Then you would need to edit the client to point to this new address.
Originally Posted by Borte