Skip to content
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

Telemetry #18

Closed
arjunmadan opened this issue Feb 10, 2016 · 3 comments
Closed

Telemetry #18

arjunmadan opened this issue Feb 10, 2016 · 3 comments

Comments

@arjunmadan
Copy link
Collaborator

  • Log where stuff is copied from
  • Timestamps
  • Anything else??
@arjunmadan
Copy link
Collaborator Author

  • External application that monitors when there's a copy/paste/cut event.
  • Log active window, copied/pasted content, time.

@arjunmadan arjunmadan modified the milestones: Feb24, Mar1 Deliverable Feb 17, 2016
@arjunmadan
Copy link
Collaborator Author

  • Now possible to log all copy/cut events system wide. Stores the string copied, time, and active window (window where the string was copied from).
  • To do: log pastes.
    • One solution: integrate paste logging with the extensions since it's the only way (I can think of) that would allow us to only detect pastes in Atom.
    • Another solution: Check if active window is Atom while pasting, and log only if this is true. (Will look at this first).

@arjunmadan
Copy link
Collaborator Author

An interesting problem I just encountered:

Integrating the logging with the Atom extension code would result in only the stuff being copied from within Atom being logged, but having it separate would result in us losing information about what is being pasted since the clipboard is local to Atom.

One solution I have is to use a separate logger for logging copy and cut events (basically when the contents of the clipboard change), and having a separate logger that runs from within the extension. This would basically just be a block of code that writes to a file with the same information as the copy logger.

We could then merge the data, and sort based on the timestamp in order to get an accurate representation of how the extension is being used.

I'll have the block of code ready by the 24th, and we can spend the last few days integrating it to make sure it works fine.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant