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!

  • PumpkinDrama@reddthat.comOP
    link
    fedilink
    English
    arrow-up
    0
    ·
    19 days ago

    A more robust approach could involve combining multiple user engagement metrics like votes, reading time and number of comments, along with a system that sorts posts depending on how they compare to their community averages. This system would be less susceptible to manipulation by new accounts or brigading, as it would require genuine engagement across multiple factors to influence a post’s ranking.

    Incorporating User Engagement Metrics in Lemmy’s Sorting Algorithms