You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I was planning on discussing this eventually anyway, but it's also timely now: in #3466 (comment), @westnordost wrote,
Now, one can argue that the precise/coarse location of the user can be determined by
his current contribution history (especially if he has auto-sync on)
When we used overpass, auto-upload was very important, because some quests (house number) would not appear until after a pre-requisite quest (building type) had been uploaded. However, with offline data storage, this is no longer a requirement. Actually, it's the other way: some functionality is only available when auto-upload is off (undo of certain actions, like leaving notes).
And it's probably the biggest privacy concern in the app.
Proposed Solution
Change the default setting to upload on wifi only.
Risks
Some people may not realize they need to upload now. Maybe there could be a prompt, similar to when you are not logged in yet, if you reach a certain number of changes waiting to be uploaded or if you have changes which are older than a certain age. It would tell (or require?) the user to upload, and let them know about the auto-upload setting (with a warning about battery usage).
The text was updated successfully, but these errors were encountered:
Use case
I was planning on discussing this eventually anyway, but it's also timely now: in #3466 (comment), @westnordost wrote,
Proposed Solution
Change the default setting to upload on wifi only.
Risks
Some people may not realize they need to upload now. Maybe there could be a prompt, similar to when you are not logged in yet, if you reach a certain number of changes waiting to be uploaded or if you have changes which are older than a certain age. It would tell (or require?) the user to upload, and let them know about the auto-upload setting (with a warning about battery usage).
The text was updated successfully, but these errors were encountered: