I’d like to invite you all to share your thoughts and ideas about Lemmy. This feedback thread is a great place to do that, as it allows for easier discussions than Github thanks to the tree-like comment structure. This is also where the community is at.
Here’s how you can participate:
- Post one top-level comment per complaint or suggestion about Lemmy.
- Reply to comments with your own ideas or links to Github issues related to the complaints.
- Be specific and constructive. Avoid vague wishes and focus on specific issues that can be fixed.
- This thread is a chance for us to not only identify the biggest pain points but also work together to find the best solutions.
By creating this periodic post, we can:
- Track progress on issues raised in previous threads.
- See how many issues have been resolved over time.
- Gauge whether the developers are responsive to user feedback.
Your input may be valuable in helping prioritize development efforts and ensuring that Lemmy continues to meet the needs of its community. Let’s work together to make Lemmy even better!
The “Top of All Time” lists on Lemmy are currently dominated by posts from the exodus period, potentially overshadowing excellent content from both before and after this event.
Unfortunately, none of the suggested solutions can be implemented as the required data hasn’t been tracked over time by the software.
Visibility-Based Ranking: Factor in how often a post is shown to users by tracking the number of times a post appears in users’ feeds and calculating an “engagement rate” by dividing votes by views. Rank “Top of All Time” posts using this engagement rate. This option cannot be implemented as the software does not keep track of post views or the number of times a post appears in users’ feeds.
Community-Specific Normalized Scoring: Adjust post scores based on each community’s monthly active user count at the time of posting. Unfortunately, this option cannot be implemented as the software does not keep track of the monthly active user count for each community over time.
Normalized Scoring: Adjust post scores based on the instance’s monthly active user count at the time of posting. However, this option cannot be implemented as the software does not keep track of the monthly active user count over time.