deleted by creator
The mental cartwheels required to fathom why that was even made physically possible are almost beyond me.
More for jerboa, but RIF had an option to confirm you want to go back/refresh feed. My palm accidentally hits the back button often, and I have to start scrolling back from the top.
There needs to be a way to link to a post in an instance agnostic way.
For example, this post is in !asklemmy@lemmy.ml and the id is 1255605, but that id number won’t work on any other instance.
If someone shares a link with me like https://lemmy.ml/post/1255605 that will take me to lemmy.ml, where I’m not logged in. If I have an account on lemmy.world then the only way for me to comment on this post is to navigate to lemmy.world/c/asklemmy@lemmy.ml manually and then literally look at the feed to find this post. It’s a pain in the butt for new / current threads but will be a huge pain for older threads.
easy subscribe links - like, click on it and then subscribe, not the current method (which totally functions but its cumbersome and unwieldly).
When people link other instances in posts or comments, it should automatically be translated to view it on your own instance instead of having to take it and search for it.
I like this one. Posted instance mentions were doing my head in as a newbie.
Default to showing subscribed communities, rather than local ones. De-emphasise the server in certain areas (eg community list) - I think the community is more important than the server it’s on and having it there so prominently causes confusion about it’s importance.
I can see why it has the server focus but I’d argue most people want to join a general server with a wide reach rather than something isolated.
Though this is me trying to use Lemmy as “distributed Reddit” so maybe I just don’t get it.
The ability to merge/join communities across instances. Right now, there’s lots of duplicated communities - which isn’t a big problem, but I feel that it’ll hinder adoption as it fragments the audience for a given topic.
Edit: also worth saying that it seems like that the if the instance hosting a community goes away, so does the community.
Yes, it is worth saying. In fact I was scrolling for this. There should be a way to adopt refugee communities with all its posts from other instances so as to not lose all the information when the server goes down for good. It needs consensus, but only from admins of original community and the new host, this last to prevent server abuse. Also, if communities can get merged, the list of instances hosting the community would serve both as redundant backup and as distributed (instead of fragmented) service.
When i scroll on the website, the website header does not follow. Meaning if I want to go somewhere or refresh the feed, i have to scroll way up to do so. Its a bit frustrating.
In the meantime you can use Stylus, there are styles already supporting this, basically it’s just setting the navbar position to fixed.
Karma
/s
I’m actually curious the reason why Lemmy does not have a karma equivalent.
I don’t miss it since I rarely checked my reddit karma but it does have pros and cons.
Karma might work on a per instance basis, but if implemented on a federation wide scale you’d have to trust every instance. It would be far too easy to artificially increase your karma with your own rogue instance just by editing the database.
I think it’s mainly to discourage reposting for the sake of reposting. On top of that, lemmy doesn’t go out of it’s way to improve user retention, which I believe karma and the incessant notifications about your comments being upvoted, were about.
Edit: added some stuff
User and post flares!
Opengraph tags for posts with embedded content need some work. That would fully fix interop between lemmy threads and Mastodon, as just one benefit.
Turn off porn on the “all” thread without having to block other NSFW content. It’s getting pretty bad blocking three or four porn communities every time I try to browse, but not being able to block the instances they’re all coming from.
I always thought that NSFW was too vague a term. One person’s NSFW is different to another’s.
What would work better is specific content tags. That would work well for trigger warnings too.
It would cover porn: nudity, softcore, hardcore
But also content themes: Alcoholism, drug taking, violence, suicide, war, guns
It could even be used for spoilers.
Users could then select the specific themes they didn’t want to see. For better UX you could have a slider that had pre selected levels. “strict”, “relaxed”, “everything”.
Posts often present content warnings behind spoiler tags at the start. The idea being that some users don’t want the story spoiled by hearing what themes it contains. That’s why I believe this system would work. Rather than having the content warnings visible it all happens in the background through structured data. Your app already knows if it’s content you don’t want to see so it either hides it, or perhaps blurs it with a warning that you likely don’t want to read it.
I’d like to be able to set the default view to sort by new in subscribed communities, currently it defaults back to active/local.
Highlight new comments (if there’s already a way to do this please let me know as I’m brand new here)
an ability to re-order search results, eg in the communities list page having it so that we can click on a column and have the results sort according to that column, or alphabetically or most recent.
and some way of filtering the results would be good as well
