List: open issues, all issues Report: new issue
421
KPM3 collects also GSM cells in background
Feedback
Resolved
November 24th, 2013 @ 11:20 am
Usul
CiaranG
Hi, I already posted in the forums [1] that KPM3 has a dedicated background task that collects GSM cells for OpenCellIDs project, that is currently also maintained by the company.
As this feature can't be disabled and isn't nessesary to fullfil the goal of adding OSM content, it had been discussed very controversal within the OSM community:
http://wiki.openstreetmap.org/wiki/Talk:Keypad-Mapper_3#Permissions
I'm not sure if this is a 'no go' for F-droid but IMHO the users should at least been aware of this unexpected second contribution. At OSM wiki, we made a big hint about this feature. This might be important, as your GSM contribution can also unveil your OSM ID http://www.openstreetmap.org/user/I%20guess%20not/diary/20196
1 https://f-droid.org/forums/topic/keypad-mapper-3/#post-9741
As this feature can't be disabled and isn't nessesary to fullfil the goal of adding OSM content, it had been discussed very controversal within the OSM community:
http://wiki.openstreetmap.org/wiki/Talk:Keypad-Mapper_3#Permissions
I'm not sure if this is a 'no go' for F-droid but IMHO the users should at least been aware of this unexpected second contribution. At OSM wiki, we made a big hint about this feature. This might be important, as your GSM contribution can also unveil your OSM ID http://www.openstreetmap.org/user/I%20guess%20not/diary/20196
1 https://f-droid.org/forums/topic/keypad-mapper-3/#post-9741
3 comments
Login to comment
Assignee CiaranG
The functionality doesn't seem like a bad thing in itself - in fact, it seems like a very useful thing. But the fact that it doesn't tell you it's doing this (unless you read to the very end of a huge help file), and there's no expectation it would be, and you can't turn it off, let alone get asked to opt-in, mean it should probably have the Tracking antifeature applied, with an explanation in the description.
Somebody started an fork that removed this feature http://forum.openstreetmap.org/viewtopic.php?pid=380465#p380465
Status Assigned > Resolved
Fixed by adding Tracking antifeature, and an explanation in the descripition (with a link to here in the issue tracker)