Skip to content
This repository has been archived by the owner on Feb 7, 2019. It is now read-only.

Discovery for URI detection event in Telemetry #618

Open
1 task
sandysage opened this issue Mar 6, 2018 · 4 comments
Open
1 task

Discovery for URI detection event in Telemetry #618

sandysage opened this issue Mar 6, 2018 · 4 comments
Assignees

Comments

@sandysage
Copy link
Contributor

sandysage commented Mar 6, 2018

Component of #515

Acceptance criteria

  • A list of proposed events and how those would be implemented
@sandysage sandysage added the backlog We have looked at and understand the issue. Prioritized with alignment to product initiatives. label Mar 6, 2018
@jimporter
Copy link
Contributor

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).

@linuxwolf
Copy link
Contributor

@irrationalagent @sandysage
As @jimporter says, we need to understand what we hope to learn so we can implement it.

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.

@devinreams
Copy link
Contributor

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. 🙃

@irrationalagent
Copy link
Contributor

irrationalagent commented Mar 7, 2018 via email

@sandysage sandysage added to do and removed backlog We have looked at and understand the issue. Prioritized with alignment to product initiatives. labels Mar 8, 2018
@sandysage sandysage changed the title Capture URI detection event in Telemetry Discovery for URI detection event in Telemetry Mar 8, 2018
@sandysage sandysage added this to the 0.1.9 milestone Mar 9, 2018
@devinreams devinreams removed this from the 0.1.9 milestone Mar 21, 2018
@devinreams devinreams removed the to do label Mar 30, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants