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!
It would be nice if communities that are similar enough could “share” a comment thread, so you don’t end up with comments scattered over many different communities for the same link. The mods could toggle something in the settings and say “This other community is good and we’ll be OK sharing posts with them”. You also wouldn’t have to explicitly crosspost.
Consolidated View:
- Create a “Consolidated Thread” view that aggregates comments from all related posts into a single, cohesive conversation.
- Provide an option to switch between individual instance views and the consolidated view.
Neat, thanks!
It might be helpful to be able to set default per community for something like this. For example, !dailygames@lemmy.zip, it would be a jumbled mess to have it be all in one thread
Thank you!!
User-Driven Linking:
- Allow users to suggest links between related posts, with a voting system to confirm relevance.
- Create a “Related Discussions” section for each post, populated by user suggestions.
I want something like that too, although it’s worth noting that the implementation corner-case details could be horrendous.
There’s got to be a better way to do cross posts. When people/bots crosspost, my “All” feed gets cluttered with multiple copies of the same post. Maybe something like a drop-down showing all the instances and communities it’s posted to.
Edited to fix autocorrect…
I don’t know if this was requested before but I really want there to be a way to see all comments throughout crossposted threads. It sucks that there are so many crossposts that have like 1-2 comments each. I want to see all discussion about a post at the same time.
Some apps will collapse those into a single post, but not all of them, and not all the time. It would be nice if that were better.
Dynamic Linking System:
- A system that automatically links related posts across different communities and instances.
- Allow users to see all related discussions in one place, regardless of where they were originally posted.
Option for default comment sorting. you can change the default sort only for posts, but not for comments, comments always sorted by Hot, and you have to manually change it each time you open comments.
In Voyager you can set this up, but it would be useful in the webui as well.
Every day for the last 15 months I have been hitting Top on every. single. post. Every day I hope that tomorrow will be the day this completely obvious missing feature has been added.
On a related note, threads ought to be able to have the default sorting changed at least by a mod, if not by the user who posted them. For example, the recent hurricane megathreads ought to have been defaulting to sorting by new.
My biggest issue is that when I post, I’m torn between sharing in the community of the largest instance or in the instance I prefer the most. Posting in the largest instance offers more visibility for my post, but it feels like I’m not supporting the instance I truly like. The communities are too fragmented.
I think “cross posting” but like as a symlink would be great for this - i.e. if you click on the post in either community, you see the same comments
Something like multireddits or Kbin collections would solve this, but it would still take a lot of effort to turn all similar communities into a single group. I really hope there is an automatic way to solve this.
I personally like distributing my posts between instances that I feel are trustworthy as it provides backup instances (thereby increasing the bus factor) which should cover the unfortunate situation of an instance shutting down.
Since we’re all federated I’m no longer forced to put all my eggs into 1 basket like reddit🤗
Feel free to crosspost! The entire point of the web is that it has connections.
It would be nice if there was a way to handle instance/user migrations. If an instance gets their domain name taken away, there’s no way AFAIK for the admin to say “Here’s our new location, with a verifiable signature”. Likewise there’s no way for a user AFAIK to move their account with a verifiable signature that the new one is still them. Ideally this could all happen automatically with signatures getting synced automatically and all that.
I’m sure it would be a lot of work and no idea if ActivityPub would get in the way, but it would give people a lot more assurance that they didn’t pick a server that will screw them over by going down.
no idea if ActivityPub would get in the way
It totally would. In ActivityPub, all objects (like users and posts) have an identifier that includes the domain name. For instance, your ID is
https://midwest.social/u/m_f. That’s what identifies your user. There is no way to change an ID - the point of an ID is after all that it stays the same and still refers to the same entity. This is a pretty serious limitation of ActivityPub right now unfortunately.I wonder who was the idiot who made a persistent ID for identity reliant on a third party factor that can be trivially taken away.
Any plans for solving it that are known?
Not as far as I am aware - I don’t think you can really fix it within the protocol, i.e. without a breaking change. Then you may as well make a new protocol.
I think there’s a FEP that could (or fixes) this. To my understanding ID can be any URI, so there are better ways. I guess it’s hard because it would brake a lot of stuff or how mastodon is build.
Any FEP trying to fix this will be incompatible with existing instances, so I don’t really see how it’s gonna work.
Yeah, it sucks. But I think that at a certain point it will need to happen if we want to make ActivityPub better with better portability.
A mute community in addition to block community. There are communities i may not want to see in my feed, but I might want to look at them. Currently my only option is to block and then offi want to check them out i have to unblock.
One thing you can do there is to take advantage of federation and jump to an instance where you are not logged in, which will then display all of the comments. On the web UI, the multicolored Fediverse icon works fantastic for this purpose, as it will jump straight to the comment that you want to see (although the hidden ones would be below that, or perhaps you would rather go to the post itself).
e.g. for me, I am reading your comment at https://discuss.online/post/12642239/11643668, but the multicolored button would take me to https://sopuli.xyz/comment/12447782, which I do not have an account on hence nothing under that would be blocked for me there.
Yes, that will allow me to read the community, it will not allow me to interact/post/reply.
Oh absolutely that is correct - once you’ve “blocked” something, you cannot then interact with it later, as it is a rather hard cutoff. I suppose you want to see something like a “remove from my feed” - basically a “hide this community from me until I want it” - rather than an actual, full-on “block”. Which is notable then that e.g. a user block of an instance is even softer than that, allowing you to see and reply and receive replies from people (though you don’t get notifications for those, unless they specifically tag your username). So community blocks are harder than people would like, and instance ones are softer, so they really aren’t hitting the sweet spot in-between.:-)
Yes, I suppose I want that too - a “community hide” option, rather than full community block:-).
Yeah, hide community is better verbiage than mute.
Hopefully they’ll work on stuff like this - but I don’t know their prioritization.
I will suggest filtering, by term and by source URL. I think it would help customize individual feeds, making it easier and perhaps more comfortable navigating the news.
Example A: term filtering: This should be fairly obvious. Say I’m a Linux user who could care less about KDE. But people keep gushing over it in the Linux subs I subscribe to, and the damn developers keep pushing new releases that also get posted. Argh! Filter out posts (maybe even comments) that mention KDE, Bob’s your uncle. And I can still enjoy all those delicious GNOME posts. Definitely not a real world inspired scenario.
Example B: URL filtering: Simply(!) filtering out link posts by source URL. Not a fan of Fox News and/or WaPo? Filter out one site or the other by root URL, like
*.foxnews.comor*.washingtonpost.com. Me, I’d gladly filter out all and any YouTube links unseen by default. That’s a constant noise generator I could genuinely live without. But I digress.I hope the examples illustrate my point because I could clearly never explain a feature request succinctly nor to the point.
Reminds me of Custom Feeds
- Inspired by Firefish’s Antennas feature
- Similar to Reddit’s multireddit functionality
- Follow specific users, communities, and instances
- Include/exclude tags or keywords
- Choose post types (posts, comments, or both)
- Set custom feeds as default
Yeah, more or less right. On Mastodon I’m a heavy filter user, so loads of terms and hashtags just GTFO. I don’t see anything near that capability baked into Lemmy.
And I have to say, the more I think about it, the more important link source filtering is. Given how many posts are links to external sites I think it would be a great feature to sift out the chaff before you even have the chance to roll your eyes at it!
I don’t see it mentioned, so maybe it’s not a popular thing, but the ability to tag a post. Often time this can be annoying, but it can help in filtering posts in certain types of communities.
Show saved items in order they were saved, not original post date. If I come across and save something from 6 months ago, when I go back into saved items, it’s sorted way back i stead of being the first item in the sort list.
This was supposed to be fixed in a server update, but doesn’t seem to be.
I really wish Lemmy had tags like RES
Keyboard navigation. I know about https://github.com/vmavromatis/Lemmy-keyboard-navigation but it’s annoying that I have to use an addin/userscript for such a basic feature.
You can use the Photon frontend instead.
Photon doesn’t exactly have keyboard navigation, i’ve been working on it though
I would love to be given a few minutes worth of grace to edit some minor spelling and/or grammar mistakes once I’ve hit the “post” button.
that or the ability to see what was before the edit, but I assume that has already been discussed
I would like to have the ability to follow a Lemmy user, in the sense of seeing their posts in unblocked communities.
There were several issues on GitHub regarding proposals on how to solve the low visibility of small instances. However, after the Scaled Sort was implemented, all those issues were closed, yet the problem persists. I continue to use Reddit the same as before because I primarily used it for niche communities, which are lacking here. The few times I’ve posted to a niche community here, I’ve either received no answers or been subject to drive-by downvotes, likely from users not even subscribed to the community. As a result, I now only post on Lemmy when the post is directed to a large community, and I use Reddit for the rest.
I think multi-communities (which have already been improved for funding) will push Lemmy forward big time. https://github.com/LemmyNet/lemmy/issues/818
This is definitely my biggest request
