Issue Tracker

Have you ever wished for a social media platform that combines the best features of Lemmy and image boards with customizable feed algorithms? I know I have. Here's what my perfect social media platform would look like:

1. A mix of Lemmy and image board: My ideal platform would allow users to post both text-based content and images, using tags instead of communities. With a view like Lemmy^1, and another grid-view like an image board^2.

2. User curation: Unlike Lemmy, where images are difficult to find again due to the lack of tags , my ideal platform would have well-curated images with tags for easy searching^2.

3. Advanced search could also be implemented, as suggested in the Lemmy issue #3788.

4. User trust levels and community moderation: A hierarchical trust level system, similar to Discourse’s trust levels[^3], could distribute the responsibility among users and reduce the burden on admins. Trust levels would be assigned for each community based on user activity and voting affinity with the admin, allowing admins to shape their instance according to their preferences without micromanaging every aspect of the community. This idea is also discussed in the Lemmy issue #3548.

5. Customizable feed algorithms: One of the best things about Lemmy is that users can choose their own algorithm for their home feed^1. My ideal platform would take this a step further by allowing users to customize their feed algorithms like in Bluesky[^4].

6. Machine learning algorithms: To make the feed even more personalized, my ideal platform would use machine learning algorithms to suggest posts to users based on their activity on the platform[^5]. For example, if a user frequently upvotes posts about cats, the platform would suggest more cat-related posts to that user.

7. One-size-fits-all image format: Image boards are known for their simple, one-size-fits-all image format^2. My ideal platform would adopt this format to make it easy for users to share images without worrying about formatting issues.

[^3]: Understanding Discourse Trust Levels [^4]: Bluesky custom feeds and algorithms [^5]: How to implement personalized feed ranking

cross-posted from: https://lemmy.world/post/1723295

I've noticed that there are a few communities that tend to dominate when viewing all. Some days it gets to where looking at all isn't very different than just looking at [email protected] or [email protected].

Before someone says "you can just block communities you don't want to see," it's not that I never want to see them, it's that I want to be able to have a view that shows me what is new and popular in a wide variety of communities. I appreciate seeing a few good memes in my feed. The problem is when that's all I see. Changing the sort from active to hot or top x days doesn't have much effect on which communities dominate, so that isn't the solution either.

"You can just subscribe to communities you like". True, but that has the effect of narrowing what I see. I'd like a view that showed me new things I never thought to subscribe to.

Lemmy devs - if you are reading this - it would be nice to have a feed that limited the number of posts showing up from any particular community. It could be a simple cutoff of 2 or 3 posts, or maybe some sort of weighting function to cause additional posts from the same community to appear lower in the sort order for that feed.

I'd love to hear what devs and other users think about this.

Edit: To everyone saying "just sort be new" - yes, that has its uses, but it only solves part of the problem. I'd like a feed that shows me what is new and popular, but from more than just one or two communities.

cross-posted from: https://merv.news/post/26663

most people i know use google by searching whatever question they have and including the word “reddit” at the end to find reddit threads since it currently has the most useful information.

As Lemmy gets more and more filled with useful threads and reviews it would be great if we can collectively improve Lemmy’s SEO so just including the word lemmy in a search will show lemmy threads related to the search.

The obscure tlds used in lemmy servers don’t help and lemmy.com currently redirects to lemm.ee. Is there a way we can improve the SEO of all instances or have lemmy.com be a aggregator of threads from many Lemmy servers?

I miss this function from reddit. I used it often to find if a post has already been submitted. Also, it was useful to see what else was posted from this domain. I hope some day this will come to Lemmy.

Examples:

1. https://www.reddit.com/domain/hillelwayne.com/
2. https://www.reddit.com/domain/hillelwayne.com/top/?sort=top&t=all

Requirements

• [X] Is this a feature request? For questions or discussions use https://lemmy.ml/c/lemmy_support
• [X] Did you check to see if this issue already exists?
• [X] Is this only a feature request? Do not put multiple feature requests in one issue.
• [X] Is this a backend issue? Use the lemmy-ui repo for UI / frontend issues.

Is your proposal related to a problem?

I have just heared about the XSS volunerability and wanted to update my instance ASAP, but was left realizing that since 0.17.3, there has not been any new arm64 builds submitted to Docker Hub at all.

So just in case, I checked the docs to see if I might just be using the wrong containers, but no - all the ones I use.

Describe the solution you'd like.

I would like to see arm64 builds return. Even if they are only found on :latest, that'd still be enough for me - I use Watchtower to autp-update my containers anyway.

Describe alternatives you've considered.

Provide arm-tagged images like older versions (i.e. 0.17.3-arm64-linux).

Additional context

No response

Requirements

• [X] Is this a feature request? For questions or discussions use https://lemmy.ml/c/lemmy_support
• [X] Did you check to see if this issue already exists?
• [X] Is this only a feature request? Do not put multiple feature requests in one issue.
• [X] Is this a backend issue? Use the lemmy-ui repo for UI / frontend issues.

Is your proposal related to a problem?

Lemmy currently lacks a feature that allows users to easily find, browse, and organize images using tags, similar to booru-style imageboards. One of the main reasons why I would like a booru-style image view in Lemmy is that I have often wanted to revisit some images but couldn't find them.

Describe the solution you'd like.

Introduce a booru-style image view in Lemmy, where users can find images by tags and edit tags to improve the organization of content. This feature would allow users to search for images based on tags. Users should also be able to edit and add tags to images, contributing to the organization and categorization of content on the platform.

Describe alternatives you've considered.

Additional context

Booru-style imageboards, such as Safebooru, are popular for their unique curation process and the ability for users to contribute to the organization and categorization of content. Implementing a similar feature in Lemmy would enhance the user experience and make it easier to discover and organize images on the platform.

Originally posted by 8ullyMaguire in #3626

Requirements

• [X] Is this a feature request? For questions or discussions use https://lemmy.ml/c/lemmy_support
• [X] Did you check to see if this issue already exists?
• [X] Is this only a feature request? Do not put multiple feature requests in one issue.
• [X] Is this a UI / front end issue? Use the lemmy-ui repo.

Is your proposal related to a problem?

Currently, there isn't a way for users to see their voting affinity with communities, instances, and other users on Lemmy. This information could help users better understand their interests and engagement on the platform.

Describe the solution you'd like.

I propose a new "Stats" page that displays a user's voting affinity with communities, instances, and other users. The page could also include additional relevant information such as:

• Top voted posts and comments by the user
• Most active communities and instances for the user
• Recommendations for similar users or communities to follow based on voting patterns

This feature would provide users with a deeper understanding of their engagement on Lemmy and offer suggestions for connecting with like-minded individuals.

Describe alternatives you've considered.

Additional context

Related to https://github.com/LemmyNet/lemmy-ui/issues/1389, https://github.com/LemmyNet/lemmy/issues/2370

Originally posted by ghost in #3241

Requirements

• [X] Is this a feature request? For questions or discussions use https://lemmy.ml/c/lemmy_support
• [X] Did you check to see if this issue already exists?
• [X] Is this only a feature request? Do not put multiple feature requests in one issue.
• [X] Is this a backend issue? Use the lemmy-ui repo for UI / frontend issues.

This feature would allow users to select their preferred scoring method from a range of options, ensuring that the platform accommodates diverse preferences and aligns more closely with individual needs.

Here are some key elements that could be included in this flexible scoring system:

1. Affinity to Admin: Enable users to opt for a scoring system that increases the weight of votes based on their affinity to the admin. By doing so, the platform would prioritize the preferences of the admin, creating a more tailored and focused community for that particular instance.

2. Score Posts based on Community Size: Provide an option for scoring posts based on the size of the community at the time of voting. This approach would consider the collective opinion of a larger community, resulting in a more democratic and representative scoring system.

3. Balancing Scores based on Instance Size: Implement a scoring mechanism that prevents the dominance of big instances, promoting a more diverse representation of instances in the feed. This approach would ensure that posts from smaller instances have a fair chance of being seen and appreciated by users across the platform.

4. Personalized Filter based on User Affinity: Introduce a personalized filter, similar to Reddit's "Best" feature, which takes into account the user's affinity with posts based on their voting history. By analyzing the user's preferences through upvotes and downvotes, Lemmy can provide a customized feed that aligns with their interests, enhancing the user experience.

5. User-Weighted Communities: Allow users to assign a weight to each community they are subscribed to, determining the proportion of posts from each community that appears in their feed. Users could assign weights ranging from 0-100 points or represented as 0 to 5 stars. For users who do not assign a weight, the system can automatically assign a weight based on their interactions with posts in each community. This feature would ensure that communities closely aligned with a user's interests have a greater presence in their feed.

6. User Engagement: Take into account user engagement metrics, such as comments, shares, and interactions, when calculating the score of a post. This approach would provide a more comprehensive measure of a post's relevance and impact within the community, beyond simply the number of votes.

7. Quality Assessment: Introduce a mechanism to evaluate the quality of posts, either through manual moderation or automated algorithms. By promoting high-quality content, the scoring system can prioritize posts that contribute meaningfully to the community, fostering valuable discussions and interactions.

Finding the perfect balance for scoring on Lemmy is a complex task, and no single approach may suit every instance or community. However, by providing users with the ability to choose their preferred scoring system, Lemmy can become a more inclusive and adaptable platform that reflects the values and needs of its diverse user base.

Related issues:

• Voting Affinity and Engagement Analysis. #3241
• The rank of a post in the aggregated feed should be inversely proportional to the size of the community. #1026
• Score posts based on community size at the time of voting. #2794
• Keep a score of the upvotes and downvotes given to user. #2370

Originally posted by 8ullyMaguire in #3477

Requirements

• [X] Is this a feature request? For questions or discussions use https://lemmy.ml/c/lemmy_support
• [X] Did you check to see if this issue already exists?
• [X] Is this only a feature request? Do not put multiple feature requests in one issue.
• [X] Is this a backend issue? Use the lemmy-ui repo for UI / frontend issues.

Is your proposal related to a problem?

Currently, the number of posts displayed in the 'subscribed' feed on Lemmy is determined by the votes a post receives, which is proportional to the size of the community. This can lead to posts from larger communities overshadowing those from smaller, but more favored, communities.

Describe the solution you'd like.

Introduce a feature that allows users to assign a weight to each community they subscribe to. The number of posts displayed from each community in the 'subscribed' feed should be proportional to the assigned weight, rather than the number of votes a post receives. This would enable users to see more content from their favorite communities, even if they are smaller in size.

Describe alternatives you've considered.

An alternative solution could be to implement a ranked-choice voting system, where users rank their preferred communities, and the feed displays posts based on these rankings. However, this may not be as flexible as the weighted approach, as it does not allow for fine-tuning the proportion of posts displayed from each community.

Originally posted by 8ullyMaguire in #3518

Requirements

• [X] Is this a feature request? For questions or discussions use https://lemmy.ml/c/lemmy_support
• [X] Did you check to see if this issue already exists?
• [X] Is this only a feature request? Do not put multiple feature requests in one issue.
• [X] Is this a backend issue? Use the lemmy-ui repo for UI / frontend issues.

Is your proposal related to a problem?

Admins are experiencing burnout due to the increasing number of users. The same goes for moderators, leading to a rise in unmoderated communities. The current solution of creating posts to request community moderation adds more workload for admins, and potential moderators may be discouraged by the full-time commitment required for the role.

Describe the solution you'd like.

Implementing a hierarchical trust level system, similar to Discourse's trust levels[^1^], could distribute the responsibility among users and reduce the burden on admins. Trust levels would be assigned for each community based on user activity and voting affinity with the admin[^2^]. This way, admins would only need to adjust the trust levels of top-tier users to shape their instance according to their preferences, without having to micromanage every aspect of the community. Admins should be able to choose which privileges users can achieve, and if they want to micromanage everything in their instance, then users get no privileges at all.

Describe alternatives you've considered.

None.

Citations: [^1^]: Discourse Blog - Understanding Discourse Trust Levels [^2^]: GitHub - Lemmy Issue: Voting Affinity and Engagement Analysis

Originally posted by 8ullyMaguire in #3548

Requirements

• [X] This is a feature request and not a bug report. Otherwise, please create a new bug report instead.
• [X] Please check to see if this request (or a similar one) already exists.
• [X] It's a single feature. Please don't request multiple features in one issue.

Is your proposal related to a problem? *

Currently, on Lemmy, there is no way to merge comments from similar posts into a single view. This can lead to fragmented discussions and make it difficult for users to follow conversations happening across multiple posts on the same topic.

Describe the solution you'd like. *

I propose adding a feature that allows users to select a few similar posts and merge all comments into the same view[^1]. There could be a user setting to show all comments for similar posts when you open any of them. The posts would have a selected checkmark that users could deselect to not show comments from those posts. This would make it easier for users to follow and participate in discussions happening across multiple similar posts.

Other ideas

• Vote Weight Calculation: Determine a formula or algorithm that calculates the weight of each comment vote based on the number of votes the parent post has received. For example, you could assign a higher weight to comment votes from posts with more votes and vice versa.
• Balancing Comment Scores: Apply the calculated weight to the comment votes to adjust their scores accordingly. This would ensure that comments from highly voted posts have a stronger influence on the overall comment ranking.
• Display of Weighted Scores: Display the adjusted or weighted scores alongside the comment votes to provide transparency and clarity to users about the impact of post votes on comment rankings.
• Visual Indicators: Use visual cues or icons to indicate which post a comment originated from within the merged view. This would allow users to understand the context of each comment and easily identify the post it belongs to.

Related

• How viable would a feature that combines comments from crossposted threads be? [^1]: Linking related posts #874

Originally posted by 8ullyMaguire in #1908

Requirements

• [X] This is a feature request and not a bug report. Otherwise, please create a new bug report instead.
• [X] Please check to see if this request (or a similar one) already exists.
• [X] It's a single feature. Please don't request multiple features in one issue.

Is your proposal related to a problem?

Yes, when writing a large post, users face the inconvenience of having to scroll to the top of the page to access the format buttons. This disrupts the writing flow and makes it difficult to format the text effectively.

Describe the solution you'd like.

I propose implementing a feature that enables scrolling only the text window when the mouse is over it, instead of scrolling the whole page. This would keep the format buttons in place and within reach, allowing users to conveniently access them while staying within the text window, improving the user experience and making it easier to format large posts.

Describe alternatives you've considered.

An alternative solution could be to add a sticky toolbar at the top of the page that contains the format buttons. This way, users would have easy access to the formatting options regardless of their scroll position.

Originally posted by 8ullyMaguire in #1921

Requirements

• [X] This is a feature request and not a bug report. Otherwise, please create a new bug report instead.
• [X] Please check to see if this request (or a similar one) already exists.
• [X] It's a single feature. Please don't request multiple features in one issue.

Describe the feature you'd like

I would like to request the addition of a single-click copy to clipboard button in all relevant places. This button would be located in the right top corner of code blocks, quotes, and post/comment sources, and would be represented by a clipboard icon. When clicked, the button would automatically copy the text to the user's clipboard, making it easy to paste the text elsewhere.

Originally posted by 8ullyMaguire in #1925

Requirements

• [X] This is a feature request and not a bug report. Otherwise, please create a new bug report instead.
• [X] Please check to see if this request (or a similar one) already exists.
• [X] It's a single feature. Please don't request multiple features in one issue.

Describe the feature you'd like

I would like to request a new feature that allows users to log in to multiple accounts. Currently, I have created multiple accounts on different instances due to heavy-load, defederations, and other reasons. However, it's difficult to manage them and find my previous posts. With this feature, I would be able to see all my posts for all the accounts when looking at my posts. Having the ability to see all notifications in one place would be a significant advantage Additionally, when modifying the content, it would be modified with the appropriate account. It would also be great if there was an easy way to select the main account to use when creating new content. This would make it much easier for me to manage my accounts and find my posts.

If the Sync Users feature was implemented, adding some sort of virtual posts and comments to be able to see my content from other accounts without modifying it, then I wouldn't need this feature. However, if this feature was implemented, I wouldn't need the Sync Users feature [^1]

Alternatively being able to migrate accounts including changing the poster of all posts/comments would solve this issue [^2].

[^1]: Sync Users [^2]: Implement a way for a user to export their account data

Originally posted by 8ullyMaguire in #1926

Requirements

• [X] This is a feature request and not a bug report. Otherwise, please create a new bug report instead.
• [X] Please check to see if this request (or a similar one) already exists.
• [X] It's a single feature. Please don't request multiple features in one issue.

Describe the feature you'd like

It would be great to have the ability to view the feed of another instance directly from the instance I'm using. This feature would enhance the user experience by allowing us to explore and engage with content from different instances without having to visit each single community or switch between instances manually.

Originally posted by 8ullyMaguire in #1928

Requirements

• [X] Is this a feature request? For questions or discussions use https://lemmy.ml/c/lemmy_support
• [X] Did you check to see if this issue already exists?
• [X] Is this only a feature request? Do not put multiple feature requests in one issue.
• [X] Is this a backend issue? Use the lemmy-ui repo for UI / frontend issues.

Is your proposal related to a problem? *

Currently, the Lemmy API makes it difficult to fetch and push all read and saved posts for account migration purposes, as there is no instance-agnostic way to link any post when using Lemmy. This limitation hinders the development of account migration tools like LASIM[^1].

Describe the solution you'd like. *

I propose adding a feature to the Lemmy API that allows fetching and pushing all read and saved posts for a user. This would enable account migration tools like LASIM to efficiently transfer user data between instances, improving the user experience and facilitating seamless account migration.

Describe alternatives you've considered. *

An alternative solution could be to improve the search API to allow filtering by creator and community more efficiently. However, this may still require searching through numerous pages to find the desired post, which is not an optimal solution.

Additional context

This feature request is related to the existing issue Allow fetching list of liked and disliked posts #3401. Implementing this feature would greatly enhance the functionality of account migration tools and improve the overall user experience on Lemmy.

Citations: [^1]: https://github.com/CMahaff/lasim

Originally posted by 8ullyMaguire in #3582

Many of the currently open pull requests are for adding new lemmy-ui user settings, for example keyboard navigation or infinite scroll. These settings are surely useful, but the process for adding them is unnecessarily complicated. Not only does a new setting have to be implemented in lemmy-ui, it also requires changes to this repo for adding a database migration, as well as adding the setting to various database and api structs.

This results in very repetetive work to implement and review such changes. It would be good if the process could be simplified in one way or another. A related problem is that we only store settings for lemmy-ui, but it would also be useful to store settings for alternative frontends and client apps.

One possible solution would be not to store individual settings, but an arbitrary json blob where Lemmy doesnt need to care about the content at all. This would also allow a user to store multiple settings blobs for different frontends/clients. Lemmy would have to do nothing more than provide endpoints for writing/reading the settings, and enforce a size limit.

Are there other solutions worth considering?

Originally posted by Nutomic in #3584

Requirements

• [X] Is this a feature request? For questions or discussions use https://lemmy.ml/c/lemmy_support
• [X] Did you check to see if this issue already exists?
• [X] Is this only a feature request? Do not put multiple feature requests in one issue.
• [X] Is this a backend issue? Use the lemmy-ui repo for UI / frontend issues.

Is your proposal related to a problem?

Currently, Lemmy uses an upvote/downvote system for ranking content, which often leads to users treating it as a like/dislike mechanism rather than evaluating the relevance of the content. This can result in content being ranked based on popularity rather than quality or relevance.

Describe the solution you'd like.

I propose an expandable menu for each post or comment that includes star ratings for various criteria, such as:

• Irrelevant-Relevant
• Dislike-Like
• Low Quality-High Quality
• Unhelpful-Helpful
• Ordinary-Creative
• Serious-Humorous
• Rude-Polite
• Violent-Harmless

The results of these ratings would not be displayed until after the votes are cast, and users could fill in any number of them. This would allow content to be ranked based on a more comprehensive evaluation, rather than just its popularity.

Identification of malicious or biased users: By flagging users who consistently vote far from the consensus, the feature may help identify users who are intentionally manipulating the ranking system or exhibiting biased behavior.

It would make for a more interesting Stats Page for Voting Affinity and Engagement Analysis.

This idea is inspired by the Likes/Dislikes issue on GitHub and OpenAssistant.

Additional context

Implementing this feature could significantly improve the content ranking system on Lemmy, making it more comprehensive and accurate. However, it could also complicate the ranking system, and I don't know whether the payoff would be worth the added complexity.

Originally posted by 8ullyMaguire in #3590

Requirements

• [X] Is this a feature request? For questions or discussions use https://lemmy.ml/c/lemmy_support
• [X] Did you check to see if this issue already exists?
• [X] Is this only a feature request? Do not put multiple feature requests in one issue.
• [X] Is this a backend issue? Use the lemmy-ui repo for UI / frontend issues.

Is your proposal related to a problem?

Currently, when a user blocks a community on LemmyNet, the blocked community still appears in search results. This can be problematic for users who want to completely avoid any content from blocked communities.

Describe the solution you'd like.

The solution I would like to propose is to implement a feature that allows users to hide blocked communities from search results by default. This means that when a user blocks a community, it will no longer appear in search results unless explicitly unblocked. This would provide a more personalized and tailored experience for users who want to avoid content from blocked communities altogether.

Describe alternatives you've considered.

An alternative solution would be to keep the current behavior where blocked communities still appear in search results, but provide a user setting that allows users to toggle whether they want to see content from blocked communities in search results or not. This would give users the flexibility to choose their preferred behavior.

Additional context.

By implementing this feature, Lemmy can enhance user control and customization, allowing users to curate their own experience on the platform. It would provide a more seamless and personalized browsing experience for users who have blocked communities and want to ensure they are not exposed to any content from those communities in search results.

Originally posted by 8ullyMaguire in #3595

Requirements

• [X] Is this a feature request? For questions or discussions use https://lemmy.ml/c/lemmy_support
• [X] Did you check to see if this issue already exists?
• [X] Is this only a feature request? Do not put multiple feature requests in one issue.
• [X] Is this a backend issue? Use the lemmy-ui repo for UI / frontend issues.

Problem

The current ranking system in Lemmy lacks a feature that functions exactly like a traditional forum. Although there are options for sorting posts by "Active" and "New Comments" the ranking system does not consider activity related to the initial post or editing of posts or comments. This limitation hinders the prioritization of recent activity and engagement on the platform.

Proposed Solution

I propose adding a new ranking option in Lemmy that functions like a traditional forum. This ranking would take into account any activity related posts/comments, including editing, and prioritize them to the top. By considering all types of activity, this ranking system would provide a forum experience.

Alternatives

An alternative approach could be to exclude editing from the ranking system, focusing only on new comments and the initial post. This would still prioritize recent activity and engagement, but without considering edits. Additionally, the possibility of implementing a "ghost bump" feature could be considered [^1]. This would allow users to bump posts without leaving a useless message behind saying "deleted by creator".

Additionally

It would be beneficial to add a view to the frontend that shows both posts and comments at the same time. In combination with this feature, this would allow users to see all recent activity for small communities at a quick glance.

[^1]: Instance configuration for bumping posts

• Lemmy Docs: Votes and ranking

Originally posted by 8ullyMaguire in #3604

Describe the feature you'd like

Please add a button and/or keyboard shortcut that is the equivalent of clicking on an image thumbnail in a single post from the community view but applied to all image posts displayed on a page. This would be equivalent to Shift+X in Reddit Enhancement Suite.

Originally posted by archer007 in #1930