Next to do is
Optimise what we’ve built before adding behaviour tracking:
-
Limit cached feed sessions per user so repeated refreshes don’t accumulate six hours of cached lists.
-
Improve category mixing to reduce CPU work on large queues.
-
Measure feed loading time and cache usage.
After that comes behaviour tracking: recording genuine impressions, topic opens and reading time. Prefetching must not count as reading.
Initially we’d collect those signals without changing the order. Once tracking is reliable, we can gradually introduce 15% behaviour weighting as users see 30–50 posts.