What features would you like added to Lemmy itself?
Often, its asked what the fediverse or lemmy needs more of in terms of content, but are there any specific features or functionality you really feel are lacking?
This is the big one I want too. I'd love to curate topic based feeds from multiple communities so that other people could subscribe to a single coffee feed instead of 5-8 communities that they had to find themselves. I think this would be particularly useful for new people joining Lemmy, it would save a lot of time if they could just sub to a couple of multi's and start getting content they're interested in rather than needing to build their sub list entirely from scratch.
Yeah. Or just personalized feeds that you could share. I'm sure some instances have a great list of communities that their subscribers follow, that isn't available on/Local. And going to /All isn't always a good time. If there was like a /All, but maybe with some extra filters, that users could just subscribe to, that would be awesome
I have this in Tesseract as "Community Groups" (works exactly like you described; browse the group as a custom feed), but I've neglected it for some time now. It works, but it's kind of slow and the sorting/mixing could use some improvement.
The sorting/mixing used to be better, but Lemmy 0.19.0 removed most of the ranking specs from the API response, so I can only sort on the basics like score, number of comments, and date. :(
I actually think some URI like fediverse:... might be better. You know, something like the mailto:coolguy@coolmail.com URI that works across all supported email websites or even apps.
Photon does that, and so does Tesseract, but it only works if you're logged in since it relies on resolve object API call (which requires authentication)
Ninja edits. A grace period where you can edit your comment without it showing it was edited. This is usually for typos and formatting mistakes that you notice right after posting your comment. A minute will do.
rather than allowing edits for invisible edits for X minutes, couldn't your client just delay actually sending it for X minutes allowing to cancel or edit freely until that point?
Gmail allows a similar feature and it seems safer in a distributed system than relying on everyone else to respect what happens after you send a raw message and an edit right after
Implementing this like Gmail would mean doing it server-side. Handling it in the client would be more error-prone, since your device would have to have a good connection in the future, and if it doesn't, handle retries and make sure never to double-post.
Back-up/failover instances for communities and users.
Every user and every admin of a community should be able to assign a failover instance in case the main instance goes down temporarily or permanently. All relevant data (posts, upvotes, settings, password hashes, mod log) would be permanently syched so you could just switch over in case of a downtime and most importantly, no content would be lost.
If you implement a feature to set the failover instance as your new main instance, that would also implicitly allow you to migrate users and communities elsewhere.
Lol I've had the experience of others not from my country telling me what the real politics of my country are because they know better than the people living there, apparently. No thanks.
No, I mean clicking on them and reading them doesn't mark them as read. You have to manually click the "Mark all as read" button or individually click the "mark as read" arrow button on each of the comments.
Add technical depth by allowing communities to select a default "sort by most recent comment" like a forum. This is the key difference between ADHD content that focuses on time versus forums that focus on depth. Then find a way to integrate these deep threads into the Allfeed. Bridge the gap between forums with depth and PITA user names versus link aggregators with ADHD but recent info and broad scope.
To some extent yes, but it is not a default option at the community level. The scope is only as a user setting overall.
I'm abstracting to analyze a question of why link aggregators do not naturally displace very technical niche forums. I don't believe that expecting the user to alter their overall sorting method is effective here. Nor do I believe that the pinned thread is an effective prioritization method to promote a more technical niche. In my opinion, the method of prioritization and promotion needs to be organic and democratically sourced as a fundamental mechanism that drives community behavior.
The part that I cannot intuitively work out is how to integrate the old niche threads with the aggregated feed in a way that is nonauthoritative or forced or feels like a narrative agenda. How to both enable content discovery while enabling depth is an interesting challenge that could IMO surpass any current or previous link aggregation platform's functionality and use in such a way as to antiquate all previous platforms.
Consolidation of communities with a sort of overlay.
Mods can choose to mirror the whole community. This way you can have a sort of unified community happening between instances instead of happening on each island.
Also mods can move a discussion if needed.
Just recently I have seen a three separate discussions across three different c/technology communities.
The "3 dots" menu is sometimes referred to as a "kebab menu" if the dots are vertical and a "meatballs menu" if the dots are horizontal. I think it's weird, but I have heard it used in instructional videos before.
Alongside others mentioned (tags/flairs, multi-communities, keyword filtering, etc.) another feature I'd like to see added/improved is notification settings.
Something like...
In account settings:
Enable/disable all notifications.
Enable/disable post reply notifications.
Enable/disable comment reply notifications.
For others' posts/comments and per posts/comments:
Enable/disable post reply notifications.
Enable/disable comment reply notifications.
With those settings you could more easily tune out all notifications or only opt into those you'd like to see, and opt out of those you're done with (say your post/comment got popular and you've had your fill from the replies).
Unrelated to notification settings, it would also be nice to be able to block communities from the front page via the ... More menu in the default web UI.
I've said before, but part of my biggest gripe with Lemmy is the process of curating a decent feed. A lot of new users will see the mess of posts in All, including political extremists, an ever growing list of fetish porn communities, and bottom of the barrel shitposts, and they won't be interested in spending a couple hours blocking and subscribing to things before the feed is usable.
One way to address this is to give instance admins better tools to curate a default subscriptions and block list for their users. Allow admins to create what they think is the most accessible feed, but also allow users to customize it as they see fit.
Tagging. del.icio.us style tagging. LJ style tagging. as free-form as tumblr or as structured as AO3's tagging system. any tagging system. as long as there is tagging system.
Some sort of super community that are searchable (i.e. not something Clientside) and span multiple servers. The fragmentation of having the same few communities everywhere is my biggest issue here.
In general I want more and better discoverability of communities anywhere.
Yeah, it's be great if a community could decide to link its feed with another community, essentially to make them one super-community that share the same content and members. Factorio, for example, has I think three communities. I'm sure there are many worse than that.
Ability to see and export the posts and comments I upvoted and downvoted
Polls with configurable restrictions (ex: only allow subscribed members of the community to vote from the date the poll was published, single-choice or multiple choices, restricted to local instance)
Tags for posts and users inside a community
Have a table for rules, and have those rules show up when creating a report
A lemmy:// (or fediverse://) protocol, to make linking content, users, communities, etc more universal across instances, apps, etc
Some way of grouping Communities other than by name (not very useful). E.G. search on 'Climate' and you don't get the name of one of the busiest communities.
In other words, group them a step up the taxonomy. Create 10 or 15 groups (sci/tech, history, music, culture, media, nature, issues, locations....), see what mods have to say about that list. (Could do worse than the Wikipedia taxonomy.)
option to get notifications when a post or a comment subtree gets a new comment. Especially (but not only) useful for your own posts, and for when you have commented on a topic whereyou are interested in not only the direct responses, but in the overall discussion.
to handle deleted content better: when a post or a comment is deleted, keep them openable, to still have the context readable
Ability to search Saved Posts, and RSS for them too like Reddit has.
I save a lot of handy things on Lemmy but it’s really difficult to find them again later. It also seems to sort by original post creation date instead of when I saved them so this makes it even more difficult to find later.
The ability to hide posts that are the exact same but posted in Different places. It is very annoying to browse through 3,4,5 posts with the same text, same image and same poster just in different communities.