Feature: Implement dual indexing for "Best" and "Newest" feeds

[Dream-World-Coder]

Description:

• Task: Create necessary database indexes to support two distinct feed sorting methods.
• Details: Add indexes to efficiently query and sort posts by chronological order ("Newest") and engagement/popularity ("Best View"). Update the feed query logic to switch between these indexes based on user selection.

[wangwangbobo]

Good call on planning the indexes upfront!

For the dual feed:

• Newest: Index on (or use since it's timestamp-based)
• Best: Need to define the scoring formula first (views? likes? comments? recency-weighted?)

Once we know the "Best" algorithm, we can create a compound index or even a precomputed field with an index on that.

What's the planned scoring formula for "Best"? 🤔

[Dream-World-Coder]

look at the server/jobs/updateEngagementScore.js for the current formula. it needs lots of update as of now, like using hours instead of days from the creation. adjusting the decay factor, and possibly use buckets to reduce floating point calculations. so if you are going to contribute on this feature, please keep an eye on all these. its a core feature, so checks will be quite strict.

[wangwangbobo]

Thanks for the pointer! 🙏

I'll check out server/jobs/updateEngagementScore.js and review the current formula. The improvements you mentioned make sense:

• Switching to hours instead of days for fresher scoring
• Tuning the decay factor
• Using buckets to avoid floating point issues

Happy to help optimize this core feature. Will take a look and propose some improvements if I find opportunities. 👍