Please post one top-level comment per complaint about Lemmy. You can reply with ideas or links to existing GitHub issues that could address the complaints. This will help identify both common complaints and potential solutions.

I believe there are a large number of feature requests on Lemmy’s GitHub page, making it difficult for developers to prioritize what’s truly important to users. I propose creating a periodic post on Lemmy asking users to list their complaints and suggestions. This way, developers can better understand the community’s biggest pain points and focus their efforts accordingly. The goal is to provide constructive feedback so developers can prioritize the most pressing issues.

Please keep discussion productive and focused on specific problems you’ve encountered. Avoid vague complaints or feature wishes without justification for why they are important.

Here is a summary of all the complaints from the previous post from six months ago. It’s interesting to see how many issues have been solved and whether or not developers value user feedback.

spoiler

• Instance-agnostic links (links that don’t pull you into a different instance when clicked) • Ability to group communities into a combined feed, similar to multireddits • Front page algorithm shows too many posts from the same community in a row, including reposts • Need to separate NSFW and NSFL posts • Basic mod tools • Proper cross-posting support • Ability to view upvoted posts • Post tagging/flairs and search by flair • Better permalink handling for long comment chains • Combine duplicate posts from different instances into one • Allow filtering/blocking by regex patterns • Avatar deletions not federating across instances • Option to default to “Top” comment sort in settings • Migration of profile (posts, comments, upvotes, favs, etc.) between instances • Mixed feed combining subscribed/local/all based on custom ratios • Categories of blocklists (language, NSFW, etc) • Group crossposts to same post as one item • Feedback for users waiting for admin approval
• Propose mixed feed merging subscribed/local/all feeds • Ability to subscribe to small/niche communities easier • Reduce duplicate crossposts showing up • Scroll to top when clicking “Next” page • User flair support • Better language detection/defaults for communities • Ability to subscribe to category “bundles” of similar meta-communities • RSS feed support • Option to turn off reply notifications • Easier way to subscribe across instances • Default to “Subscribed” view in community list • Fix inbox permalinks not navigating properly • API documentation in OpenAPI format • Notification badges should update without refresh • Single community mode for instances • Reduce drive-by downvoting in small communities • More powerful front page sorting algorithm

  • PumpkinDrama@reddthat.comOPEnglish
    0·
    8 months ago

    Comprehensive Tagging System

    Problem

    Users often have difficulty finding specific posts or content they’ve previously seen on social media platforms. The current tagging/hashtag systems on platforms like Twitter are limited and don’t provide adequate organization and searchability. Additionally, many users want more granular content filtering options beyond just binary NSFW/NSFL flags.

    Proposed Solution

    Implement a comprehensive, flexible tagging system similar to platforms like Safebooru, with the following functionality:

    1. Allow users to add multiple tags to posts to categorize content.
    2. Enable advanced search capabilities to find posts by including/excluding tag combinations (e.g. tag1 AND tag2 but NOT tag3).
    3. User-controlled blacklists in settings to filter out unwanted content based on tags.
    4. Provide communities/instances ability to configure tagging permissions (unrestricted, privileged user, or moderator-only tagging).
    5. Make tags editable by post authors for a set period after posting.
    6. Allow privileged users/moderators to add new tags and edit/delete existing tags.
    7. Moderation features like edit history, user trust levels or voting to accept or reject new tags.

    Benefits

    • Improved content discovery and rediscovery
    • Enhanced content organization
    • Granular feed customization by including/excluding tags
    • Personalized filtering of sensitive/undesirable content
    • Community participation in curation process
    • Incentives and gamification (e.g. leaderboards for top taggers)
    • Tags are non disruptive metadata, hashtags are just spam

    Additional Ideas

    • User-specific personal tag sets visible only to that user
    • Allow following specific tags for notifications
    • Mandatory tags (e.g. SFW/NSFW) configured per community/instance
    • Tag synonym support to consolidate similar tags
    • Autocomplete suggestions when adding tags
    • Track percentage of user’s liked posts per tag in user stats
    • Use tag percentages for user affinity matching

    Implementation:

    • New tags database table(s) to store tags, names, descriptions, languages
    • API endpoints for CRUD operations on tags
    • UI components for adding/editing tags on posts
    • Search functionality to query posts by tag combinations
    • User settings for tag blacklists/filtering
    • Trust system and edit history for moderation
    • Optional gamification with leaderboards

    The proposed tagging system aims to vastly improve content organization, discovery, and personalized filtering capabilities compared to basic hashtags or binary flags. It provides flexibility for communities to tailor permissions while empowering users to curate their experience.