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

Correct View Count Incrementation Logic #117

Open
3 tasks
andylizf opened this issue Mar 24, 2024 · 0 comments
Open
3 tasks

Correct View Count Incrementation Logic #117

andylizf opened this issue Mar 24, 2024 · 0 comments
Assignees

Comments

@andylizf
Copy link
Contributor

andylizf commented Mar 24, 2024

Description

View count metrics are inaccurately inflated due to their incrementation on every data fetch operation, including internal service calls.
For instance, fetching a single answer not only increments the view count for that answer but also for the question it belongs to, and if that question's best answer is fetched in the process, its view count is incremented as well. This creates a chain reaction where accessing one piece of content inadvertently increases the view counts across related content, significantly distorting true user engagement levels.
This mechanism is susceptible to exploitation and fails to provide a faithful representation of user interest.

Actions

  • Revise view count logic to increment only on direct user views.
  • Introduce rate limiting and detection for suspicious view count activities.
  • Differentiate between direct views and internal fetches in view count logic.
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

2 participants