- 21 Posts
- 48 Comments
14·10 months agodeleted by creator
deleted by creator
17·10 months agodeleted by creator
51·10 months agodeleted by creator
1·10 months agodeleted by creator
deleted by creator
deleted by creator
4·1 year agoWould it be feasible to expose the metadata for posts in such a way that search queries could be customized to sort a front page any way a user wants to see it?
There is already such an API endpoint which is available for mods and admins.
@[email protected] in https://discuss.online/comment/6718715
Yeah, it would definitely be feasible to expose post metadata for customized search queries. Currently, the data is restricted to admins and mods, but having an API endpoint for users could enhance the sorting options without significant strain on the server. It could lead to more tailored and engaging user experiences on the platform.
https://discuss.online/comment/6718201
Perhaps even a sentiment analysis would be interesting to see: serious discussion, jokes and memes discussion, informative posters, political conversation left or right, etc.
This reminds me of Slashdot moderation and Media Bias Fact Check Integration
Slashdot moderation
this was something I loved about slashdot moderation. When voting, people had to specify the reason for the vote. +1 funny, +1 insightful, +1 informative, -1 troll, -1 misleading, etc.
That way you can, for example, set in your user preferences to ignore positive votes for comedy, and put extra value on informative votes.
Then, to keep people from spamming up/down votes and to encourage them to think about their choices, they only gave out a limited number of moderation points to readers. So you’d have to choose which comments to spend your 5 points on.
Then finally, they had ‘meta moderation’ where you’d be shown a comment, and asked “would a vote of insightful be appropriate for this comment” to catch people who down-voted out of disagreement or personal vandetta. Any users who regularly mis-voted would stop receiving the ability to vote.
I don’t think this is directly applicable to a federated system, but I do think it’s one of the best-thought-out voting systems ever created for a discussion board.
edit: a couple other points i liked about it:
Comments were capped at (iirc) +5 and -1. Further votes wouldn’t change the comment’s score.
User karma wasn’t shown. The user page would just say Karma: good. Or Excellent, or poor, or some other vague term.
I’d understand using new activity sorting for small communities but for large communities you can’t keep up with it.
I don’t understand platforms like Mastodon that mimic Twitter without incorporating the features that contribute to its popularity. If I were looking for a most recent sorting algorithm I would use a chat.
Well, that would only be implemented if it were offered by the API; otherwise, just use what is available right now, which are votes and the number of comments. I find it more invasive that other users can see the post history in my profile than admins being able to see the amount of time I spend reading each post. Revealing my feed feels akin to exposing my browsing history.
The number of sorting algorithms needs to be much more limited than that; otherwise, it puts too much load on the server calculating all those combinations. It’s important to strike a balance between customization and system performance to ensure smooth operation and optimal user experience.
I thought the ‘hot’ ranking was a mixture of votes and comment engagement?
Hot: Like active, but uses time when the post was published
I do feel like there needs to be some further tweaking, controversial should have a time falloff so it shows recent controversy instead of something 6 months old for example.
Yeah, I believe the “Most Comments” sort should have a time limit too. There is an issue opened about it: Controversial post sort should have time limit
7·1 year agoHuman bias is a pervasive element in many online communities, and finding a platform entirely free from it can be akin to searching for the holy grail. Maybe look into self-hosting an instance and punish moderators who don’t follow their own rules.
This is not possible because sorting is done in the database, so adding a new sort option requires a database migration with new indexes, columns and updated queries. Not something that can be done with a simple plugin.
@[email protected] in https://github.com/LemmyNet/lemmy/issues/3936#issuecomment-1738847763
An alternative approach could involve utilizing an API endpoint that provides metadata for recent posts, allowing users to implement custom sorting logic on their client side using JavaScript. This API endpoint is currently accessible only to moderators and administrators
There is already such an API endpoint which is available for mods and admins.
Regrettably, complaining tends to be a common pastime for many individuals. I acknowledge your frustrations with certain users who may appear entitled or unappreciative of the considerable effort you’ve dedicated to developing Lemmy. Shifting towards a mindset that perceives complaints as opportunities for enhancement can be transformative. Establishing a set of transparent rules or guidelines on how you prioritize issues and feature requests could help turn critiques into opportunities for improvement. This transparency can help manage expectations and foster a more collaborative relationship with the users in your community. While not all complaints may be actionable, actively listening to feedback and explaining your prioritization criteria could go a long way in building trust and goodwill. Open communication and a willingness to consider diverse perspectives can lead to a stronger, more user-centric product in the long run.
The philosophy of Complaint-Driven Development provides a simple, transparent way to prioritize issues based on user feedback:
- Get the platform in front of as many users as possible.
- Listen openly to all user complaints and feedback. Expect a lot of it.
- Identify the top 3 most frequently reported issues/pain points.
- Prioritize fixing those top 3 issues.
- Repeat the process, continuously improving based on prominent user complaints.
Following these straightforward rules allows you to address the most pressing concerns voiced by your broad user community, rather than prioritizing the vocal demands of a few individuals. It keeps development efforts focused on solving real, widespread issues in a transparent, user-driven manner.
Here’s a suggestion that could help you implement this approach: Consider periodically making a post like What are your complaints about Lemmy? Developers may want your feedback. This post encourages users to leave one top-level comment per complaint, allowing others to reply with ideas or existing GitHub issues that could address those complaints. This will help you identify common complaints and potential solutions from your community.
Once you have a collection of complaints and suggestions, review them carefully and choose the top 3 most frequently reported issues to focus on for the next development cycle. Clearly communicate to the community which issues you and the team will be prioritizing based on this user feedback, and explain why you’ve chosen those particular issues. This transparency will help users understand your thought process and feel heard.
As you work on addressing those prioritized issues, keep the community updated on your progress. When the issues are resolved, make a new release and announce it to the community, acknowledging their feedback that helped shape the improvements.
Then, repeat the process: Make a new post gathering complaints and suggestions, review them, prioritize the top 3 issues, communicate your priorities, work on addressing them, release the improvements, and start the cycle again.
By continuously involving the community in this feedback loop, you foster a sense of ownership and leverage the collective wisdom of your user base in a transparent, user-driven manner.
Having shared tags across communities allows for better content discovery and curation based on specific interests or preferences. Users could also easily filter out or avoid posts related to triggering content like their phobias, traumatic events, or other sensitive topics by specifying certain tags they wish to exclude.
Lemmy was better before the Reddit exodus last year, when people started insulting others by calling them tankies and fascists. Before that, it was much more peaceful.