I would like to see recommendations for communities based on my communities. It’s not trivial to solve, but discoverability isn’t great right now.
Problem here is also that your instance may not know about all communities from the instances you’re connected to. This could probably also be improved.
I guess the ‘simple’ way of doing this would be adding tags to communities like ‘art’ ‘hobbies’ ‘sport’ ‘football’ etc. This might then let the app suggest others based on the tags you are subscribed to.
It would probably still require some AI/analytics to work out the links based on user activity in different communities/tags but I think it would make it easier to group interests and promote smaller communities.
It could also improve Lemmy visibility in Masterdon if the tags are used as hashtags or something. (Would require more work)
Recommendation algorithms are a big reason for the enshitification of other social media. You don’t need to be connected to everything everywhere all at once. Enjoy your handful of small communities.
Split NSFW into NSFW and NSFL.
It would probably be better to have a more general tag system and then NSFW and NSFL could just be examples of tags.
Although NSFW really serves the extra purpose of “18+” which is important to have for legal reasons.
Maybe a setting for each tag for whether it qualifies as NSFW? That way you could have multiple tags that would be filtered as NSFW for different classes of content, which could enable individual users to only filter one of the tags if they only want to avoid something specific.
I’ve made a post a few days ago. I’d argue we should make a proper distinction. Adult content and NSFW isn’t the same thing. Currently everything from sex education to gore and death is the same category. I think it’s really not. NSFW tags help so you can scroll through things in an open-plan office or while commuting. Porn is porn and gore is gore. I think we shouldn’t oversimplify this but keep the nuances and have different categories. Also I’d like to not mix stuff like sex education which might be fine, and minors ask those questions all the time on Reddit with other things like fetish.
An option to view all comments from crossposts when browsing a post. It’s annoying how you can see a post that’s been crossposted 5 times and wonder where the comments are.
Reading some of these is making me really appreciate @ernest.
We have this one, it’s handy. There’s a list of crossposts and how many comments each has, you can click to where the acive discussions are.
Cross instance post/comment deletion.
Sometimes I just don’t want my comments to live forever and deleting shouldn’t be impossible.
-
Reports categories based on both the community, the instance of the community + the user to reduce report noise between mod actions and admin actions.
-
Post tags, to label content within a community.
-
Better language support, clearly indicating which ones are allowed when submitting something in the language dropdown, as well as basic language detection support.
-
When the instance is using pictrs, add a section in the user’s settings to see all the uploaded pictures in that account, with the ability to delete any of them.
-
Better accessibility / a11y support for uploaded images with alt-text.
-
Support for svg-based emojis
-
For mods, the ability to make a pinned post made by one of the mods editable by other mods, which would be useful for FAQs, etc.
-
The ability to subscribe/follow a specific user, not just communities.
-
Passkeys support as a 2FA method.
-
Some basic builtin automod action, such as blocking known keywords from spammers from being posted, not just showing as removed as when using the slur filter in the admin settings.
EDIT: Something I just thought of
- A URI protocol handler to refer to communities, users, post and comments in an instance-independant way (ie:
lemmy://u/mp3@lemmy.ca,lemmy://c/asklemmy@lemmy.ml,lemmy://c/asklemmy@lemmy.ml/p/1234567) or another syntax that makes more sense. That way you could let the OS redirect the query to the software of your choice, and define your home instance there.
Now there are some issues to figure out before defining the URI handler, like how to refer to a post or comment that will redirect to the appropriate one on your home instance since post and comment currently have a unique ID on each instance, which makes them hard to directly address without doing some kind of conversion.
