Rub21 left a comment (openstreetmap/openstreetmap-website#7089)
> The end goal needs to be to get rid of the page number argument and replace
> it by a cursor so that subsequent fetches can use an index to start from the
> right point rather than having to start form the beginning each time
Yes, this is one of the biggest performance issues today. If we keep only
`trackable` and `identifiable`, we get better performance because we no longer
depend on two queries joined by `UNION ALL`, and we could use the trace ID as
the cursor.
> Why do we have different options at all?
According to the 2026 stats, some GPS uploaders today pick `trackable` (3.4%)
or `private` (23%) because they do not want their username linked to the trace
, they want the anonymous option.
I think this is a strong reason to still keep two visibility levels, but it
seems we could have a better description for `trackable`: e.g
```yaml
traces:
visibility:
trackable: "Trackable (trace not listed at /traces, points shared in API
as anonymous, ordered, with timestamps)"
identifiable: "Identifiable (trace listed at /traces, points shared in API
as identifiable, ordered, with timestamps)"
```
I think keeping both options, `trackable` and `identifiable`, is the right
path. That way we keep the users that need anonymity and we also improve the
performance of the site.
--
Reply to this email directly or view it on GitHub:
https://github.com/openstreetmap/openstreetmap-website/issues/7089#issuecomment-4478366736
You are receiving this because you are subscribed to this thread.
Message ID:
<openstreetmap/openstreetmap-website/issues/7089/[email protected]>_______________________________________________
rails-dev mailing list
[email protected]
https://lists.openstreetmap.org/listinfo/rails-dev
