-
Notifications
You must be signed in to change notification settings - Fork 11
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Opt-out should be possible and undetectable #50
Conversation
For framing any discussion we have. Closes #49.
We've gotten some pushback about this. Do we have a position on whether it's sufficient to reveal a "this API is not available" kind of signal as long as there are lots of other reasons for an API's unavailability, aside from the user opting out? This seems analogous to e.g. probes for device capabilities. "No you can't have gyroscope sensor access, either because the user said No or because there just is no gyroscope." |
@michaelkleber Seeing that you're noting some change on whether we all agree on this I've marked it as needs work and as a candidate for an agenda item in a meeting. If that makes sense to you can you open an issue in meetings? |
Let's see if we can resolve it in discussion in #49 — maybe agenda space won't be needed. |
and the conditions where it might be OK
For avoidance of doubt: as I said in #49 (comment), Martin's change has resolved my previously-raised concern. |
For framing any discussion we have regarding #49.
Closes #49.