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

improve hangout telemetry #1291

Closed
tansaku opened this issue Sep 21, 2016 · 1 comment
Closed

improve hangout telemetry #1291

tansaku opened this issue Sep 21, 2016 · 1 comment
Assignees

Comments

@tansaku
Copy link
Contributor

tansaku commented Sep 21, 2016

currently we only know who appeared in a hangout, but not when they arrived and left

@tansaku
Copy link
Contributor Author

tansaku commented Sep 21, 2016

this would probably involve refactoring the data model so that rather than event instance "participants" being a text string, to the case where we had

class EventInstance
  has_many: users
end

so when the hangout sent back a participant string we would parse it into a users and link with join table.

We know at the moment at least 2/3 of users don't have G+ accounts and so won't link to existing user accounts. (we could try to calculate what percentage of participants in hangouts don't have corresponding AV accounts using G+)

QUESTION

should we have a new entity called participant to distinguish from user?


thinking about snapshots of the hangout

class EventInstance
  has_many :snapshots
end

snapshots initially could be just the json data and timestamp ...

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

No branches or pull requests

3 participants