While @nutomic@lemmy.ml and I do have a lot of issues that are going to take us a lot of time this upcoming year, its still useful for us to hear what your most desired features for Lemmy are, and prioritize them.
If they’re smaller, we could get to them fairly quickly, or others wanting to contribute could see whats most wanted.
Outside of just posting them here, make sure github issues exist for them (this is what we work from), and do a thumbs up react for all the ones you’d like. Despite being a popular project, we have very few people voting on these issues . We can then use the link above (issues sorted by most thumbs up ), to keep track.
Thanks all.
The ability to tag posts (what are called “flairs” on reddit)
maybe more privacy features, like offering an invidious link when someone posts youtube, nitter for twitter, stuff like that
We could add helpers in the ui, like the one we have on the create post page for using an archive link. But overall I’d like a link aggregator to remain mostly agnostic about the links being posted ( we also do remove some tracking / utm params tho ).
The other thing is there are many of these 3rd party viewers, and they go down quite often and leave dead links. We’d use it if someone made a rust or js library for it tho.
For the case of Invidious, a redirector exists at https://redirect.invidious.io/ which could be used as intermediate point in this case.
Oh wow, I would love this. I agree, it would be mighty convenient.
It’s not that big of a deal, but I’d love to see a redesign on the main page’s community related sidebars. Both of them feel really clunky the way they are now, having them come one after the other instead of in a vertical list, and with no way to order the ones you are subscribed into alphabetical order instead of popularity order.
The way Reddit does the trending communities in its redesign look pretty good, and the way old Reddit orders the subreddits you joined in the top bar is also nice, something at least inspired on that would be really good.
Also a redesign on the top bar (when the page is taking less than half of the screen) should be at least in the priority list, it’s the one aspect of the site that looks REALLY bad.
I’ll make a issue later but front page sort options should be cached in local storage so that if I click comments on a thread and comeback I don’t have to reset my filters.
I just would want the option to view pages as lightweight, static html with low or no JavaScript, even if it means pages are not interactable.
I also think it would be nice if there were additional themes, and that the things fundamentally rethought how much white space was put all over the place. There’s so much potential with the things, but I genuinely just don’t think they are reaching their potential right now.
Lemmy UI works with javascript disabled, but you can only read things, everything else doesn’t work.
I see what you mean with theming. Making it easier to change themes easily makes the experience better for those of use who want it just right in a different way. But as to defaults, I don’t dislike Lemmy’s design at all. Though I get the desire for flexibility.
I’d really love to see an option that’s closer to old reddit or Tildes.net or something, I always feel a little alienated by the design as it is now.
user defined lists of communities for viewing as a feed
Include a Replies Collection via Page json, so that Mastodon & other #ActivityPub software can know about all the replies each Lemmy post has
Could you open up a github issue for this one.
Human readable URLs! The URL is a very important part of a site’s user interface, and lemmy’s URLs currently just have a post number - there is no title, or even the name of the sub-community. Compare this to reddit: when I paste a friend a reddit URL in chat they get two hints about what it is about: the subreddit name, and the post’s title, both embedded in the URL itself. This lets them decide if they want to click it now, or later, or never, or to recognize if they’ve already seen it. Lemmy links should be like that.
I kind of wish that when I respond to a comment in my inbox, that it doesn’t just disappear after I submit it. I usually want to click the context button after I respond. It’s just a little pet peeve and not really much of an issue, but I digress.
deleted by creator
Improvements on federation with Mastodon, etc. Right now posts on Mastodon have as author the user post, nor the community (but you are following lemmy communities, not users, because it is not possible follow users). So, when any Mastodon user want to follow these “new source” and follow the user of the tooth, nothing happens. And he is unable to follow the community! A furst workarround should be add a bottom line on the tooth like "follow this community at community_name@lemmy_instance.tdl "
-
Multi-communities akin to multireddits, and also, cross-instance multi-communities.
-
If you log into your account on a post, I’d prefer to be taken back to the post, instead of the front page, as it is now.
-
MoAr federation (for example, the ability to follow mastodon or pixelfed accounts from Lemmy, it could work well with custom multi-communities).
-
Allow the post author to decide the default sorting. I think this would be really nice because it would allow the author to design the appropriate dialgue.
For example, top sorting is good for finding the best answers. New is better to get a understanding of the general reception of the post.
It could also make sense to create new sorting methods if this was implemented. Perhaps a twitter like sorting where you can only see the first post in a thread. Then you can click into that thread.
Perhaps limit how users can interact for the post? Removing voting on comments or disable threads.
Client Oauth2/OIDC login and account creation (“federated auth”) would be nice for people self-hosting Lemmy and trying to integrate with other services.
Server side OIDC (like Mastodon has) or app auth tokens would be nice in for using 3rd party clients.
Adding onto this, IndieAuth looks good.
Sorting/scoring of posts and comments based on votes from users that I trust or users with similar voting pattern to mine.