1ec5 left a comment (openstreetmap/openstreetmap-website#6606)
> There has been discussion on GDPR-adjacent topics about how the API is not
> able to provide access to certain things like confirmation of Terms of Use. I
> wonder if we should start designing things like this in a way that allows for
> API clients to access these in the future?
We’re tracking this confirmation in #6610. It’s premature to assume that
everyone has confirmed the ToU, but I haven’t seen any indication that we need
to expose this information via the API. If so, it would probably be similar to
the “consider public domain” flag, which a client can discover about the
currently authenticated user but not about other users.
> Currently I have it as a big button under the heatmap:
Sensible, though kind of amusing. Maybe you could stick it next to the heading,
so it’s less obtrusive. It feels like we’re eventually going to have an
overarching discussion about restyling the editing options anyways.
--
Reply to this email directly or view it on GitHub:
https://github.com/openstreetmap/openstreetmap-website/pull/6606#issuecomment-3662411692
You are receiving this because you are subscribed to this thread.
Message ID:
<openstreetmap/openstreetmap-website/pull/6606/[email protected]>
_______________________________________________
rails-dev mailing list
[email protected]
https://lists.openstreetmap.org/listinfo/rails-dev
