Summary
Currently, the implemented view count functionality increments on every page refresh, even within the same browser tab/session.
Related Discussion: #204 (comment)
Current Behavior
- Refreshing the same page repeatedly increments the view count each time.
- The same user/browser/session can generate multiple counts within a very short timeframe.
Suggested Improvement
Consider introducing a lightweight deduplication mechanism to reduce repeated counts from the same user or device within a defined interval.
Possible approaches could include:
- Session-based tracking
- Cookie-based deduplication
- Temporary local storage/session storage checks
- Rate-limiting repeated increments from the same browser
Why This Could Help
- Produces more meaningful engagement metrics
- Reduces accidental/artificial inflation from refreshes
- Aligns more closely with how “unique views” are commonly interpreted by users
Notes
This does not appear to be covered in the current PRD and may be completely acceptable for the initial implementation. Logging this as a potential future enhancement for discussion and consideration.
Designs
No response
Describe alternatives you've considered
No response
Code of Conduct
Summary
Currently, the implemented view count functionality increments on every page refresh, even within the same browser tab/session.
Related Discussion: #204 (comment)
Current Behavior
Suggested Improvement
Consider introducing a lightweight deduplication mechanism to reduce repeated counts from the same user or device within a defined interval.
Possible approaches could include:
Why This Could Help
Notes
This does not appear to be covered in the current PRD and may be completely acceptable for the initial implementation. Logging this as a potential future enhancement for discussion and consideration.
Designs
No response
Describe alternatives you've considered
No response
Code of Conduct