1ec5 created an issue (openstreetmap/openstreetmap-website#7089)
The user can choose from four [visibility
levels](https://wiki.openstreetmap.org/wiki/Visibility_of_GPS_traces) when
uploading a GPS trace: `private`, `public`, `trackable`, and `identifiable`.
I’ve been talking with @Rub21 and @joto about the possibility of streamlining
these visibility levels based on our current needs and user expectations. It
sounds like we might be able to eliminate the `private` option as redundant and
`trackable` as underused.
This would make [the upload form](https://www.openstreetmap.org/traces/new)
more straightforward without the need for more toggles as in #2308. Meanwhile,
we would avoid leaving the mistaken impression that “private” trace _data_ is
private, since
[deanonymization](https://openstreetmap.us/events/state-of-the-map-us/2019/openstreetmap-for-location-data-privacy/)
is a potential risk in some circumstances. @Rub21 is also investigating
whether paring back the visibility levels can give us more options for
improving the performance of GPS trace listings.
--
Reply to this email directly or view it on GitHub:
https://github.com/openstreetmap/openstreetmap-website/issues/7089
You are receiving this because you are subscribed to this thread.
Message ID: <openstreetmap/openstreetmap-website/issues/[email protected]>
_______________________________________________
rails-dev mailing list
[email protected]
https://lists.openstreetmap.org/listinfo/rails-dev
