Timeline for Should I contact the manufacturer if their product allows access to other users' location information?
Current License: CC BY-SA 3.0
6 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jan 12, 2017 at 19:29 | comment | added | Delioth | Judging from OP, it seems like it doesn't need the LAT/LONG to function- just the UID seems to give the location on a map (i.e. LAT/LONG is pulled in the backend and then populated in, likely to feed data into the frontend so the frontend can figure out showing the map correctly). | |
| Jan 11, 2017 at 20:31 | review | Suggested edits | |||
| Jan 11, 2017 at 20:46 | |||||
| Jan 10, 2017 at 0:47 | comment | added | Evan R. | @XiongChiamiov right...which is why I, as well as others, suggested a password/PIN. I never said it was the best way to do what they're doing, just like two tin cans + string probably isn't the best way to communicate over long distance. It works for what they wanted, but isn't the most secure/optimal way to do it. | |
| Jan 9, 2017 at 23:52 | comment | added | Xiong Chiamiov | Other answers cover the flaws in this: just because you want to share your location now doesn't imply you want to share it forever, and just because you want to share your location with one person doesn't mean you want to share it with everyone. Saying that this isn't a security flaw because it's designed to share location data is kinda like saying an issue where you could view any other user's Dropbox files isn't a flaw in Dropbox, since it's a service designed for sharing files. | |
| Jan 9, 2017 at 23:36 | review | First posts | |||
| Jan 9, 2017 at 23:52 | |||||
| Jan 9, 2017 at 23:36 | history | answered | Evan R. | CC BY-SA 3.0 |