-
Notifications
You must be signed in to change notification settings - Fork 26
Discovery for URI detection event in Telemetry #618
Comments
Is there a spec for this anywhere, or is this just a placeholder issue for now? There are probably some privacy concerns that would be good to hash out here (in particular, I'd like to ensure that we know as little as humanly possible about what URLs a user has navigated to). |
@irrationalagent @sandysage I assume the approach is similar to our other events/scalars, where sensitive details (here, the URL -- in whole or in part) are not interesting to capture. |
The idea discussed here, sorry for scant details, was just to capture a) if/when a match was found and b) the count of matches. e.g. I invoke the doorhanger when on reddit.com and have one matching reddit.com entry = event fired with "1" versus I invoke the doorhanger on facebook.com and have no entry = event fired with "0". This starts to give us a few potential signals: users are (or not) storing the usernames/passwords they use often, the doorhanger is matching, if users have multiple matches and how often (if we should design experiences accordingly), etc. I'll let @sandysage elaborate but wanted to make sure any immediate concerns with this were addressed and didn't hang out there. We're not talking about capturing PII or URIs or anything like that, just numbers. 🙃 |
+1 to Devin's response. We're just looking for number of matches after
detection, not what was matched. If there are concerns about this then
let's sync up about it.
…On Tue, Mar 6, 2018, 3:51 PM Devin Reams ***@***.***> wrote:
The idea discussed here, sorry for scant details, was just to capture a)
if/when a match was found and b) the count of matches.
e.g. I invoke the doorhanger when on reddit.com and have one matching
reddit.com entry = event fired with "1" versus I invoke the doorhanger on
facebook.com and have no entry = event fired with "0".
This starts to give us a few potential signals: users *are* (or not)
storing the usernames/passwords they use often, the doorhanger is matching,
if users have multiple matches and how often (if we should design
experiences accordingly), etc.
I'll let @sandysage <https://github.com/sandysage> elaborate but wanted
to make sure any immediate concerns with this were addressed and didn't
hang out there. We're not talking about capturing PII or URIs or anything
like that, just numbers. 🙃
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#618 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AFXV4f5w2eYTlD9EumEdlVeh42eQ0_AAks5tbxLqgaJpZM4SfBTv>
.
|
Component of #515
Acceptance criteria
The text was updated successfully, but these errors were encountered: