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.

Sign up for GitHub

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

Jump to bottom

Refactor and merge ActivityTracker and UserActivityTracker #359

Open
Half-Shot opened this issue Sep 27, 2021 · 0 comments
Open

Refactor and merge ActivityTracker and UserActivityTracker #359

Half-Shot opened this issue Sep 27, 2021 · 0 comments
Labels
T-Task Refactoring, enabling or disabling functionality, other engineering tasks.

Comments

@Half-Shot
Copy link
Contributor

These two classes support similar, but not identical use cases:

  • The ActivityTracker class is used to determine the most likely active state of a Matrix user, based upon messages we've seen from the user and presence/EDU activity.
  • The UserActivityTracker tracks both Matrix and Remote users to determine their activity, but only uses message events to determine this. It also has a concept of a MAU period (how many active users are there in a given month). The other module just reports data.
@Half-Shot Half-Shot added T-Task Refactoring, enabling or disabling functionality, other engineering tasks. and removed enhancement labels May 13, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
T-Task Refactoring, enabling or disabling functionality, other engineering tasks.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@Half-Shot