Open chrisshaw opened 2 years ago
Hi @chrisshaw - Can you confirm that this request is just about the browser extension and not for the embedded client (ie. when publishers embed Hypothesis on their website) or the client in the LMS app?
@robertknight Open to suggestions; the intent is reporting on the client. With that said:
A general comment I have regarding any kind of data collection that might require user approval, is that we could only use it in scenarios where we have a way to persist these preferences. This means either the extension or logged-in users (for whom we can store account-level preferences). The embedded client does not have reliable access to persistent storage when the user is not logged in. This is due to the way that browsers (especially privacy-focused ones) treat iframes, as part of anti-tracking measures.
As an example of such a setting that we already have, there is an account-level setting that tracks whether the user has seen and dismissed a tutorial panel in the client.
This would help us
Flow
As the product manager
Constraints
Notes
In conversations
Reference