In this post I will list the known issues or possible improvements for Lemmy.world.
Please comment with any issue or area for improvement you see and I will add it here.
Remember: this instance was only started June 1st so a lot of troubleshooting and tweaking to be done.
Issues can be:
- Local (lemmy.world) (also performance issues)
- Lemmy software issues
- Other software related (apps/Fediverse platforms etc)
- Remote server related
- (User error? …)
Known issues
Websockets issues
There are some issues with the Websockets implementation used in Lemmy, which handles the streaming. Websockets will be removed in version 0.18 so let’s hope these issues will be all gone then!
- Top posts page gets a stream of new posts ? Websockets issue
- You’re suddenly in another post than you were before > Websockets issue
- Your profile will briefly display another name/avatar in the top right corner
Spinning wheel issues
Error handling is not one of Lemmy’s strongpoints. Sometimes something goes wrong, but instead of getting an error, the button will have a ‘spinning wheel’ that lasts until eternity. These are some of the known cases:
- You want to create an account but the username is already taken
- You want to create an account but the username is too long (>20 characters)
- You want to create an account but the password is too long
- You want to create a community but the name is already taken
- You want to create a community but the name is not in all lowercase letters
- You want to create a post over 2000 characters
- You want to post something in a language that isn’t allowed in the community
Other issues
- Federation not always working; Apparently not everything gets synced all the time. This needs troubleshooting.
- “404: FetchError: invalid json response body at http://lemmy:8536/api/v3/site” This sometimes happens when the Lemmy app container is very busy. Needs troubleshooting
Enhancement requests
- Can themes be added? > To be checked if this can be done without changing code.
For support with issues at Lemmy.world, go to the Lemmy.world Support community.
It surprised me that the communities list can’t be sorted by clicking on column headers; especially because the mouse cursor becomes a pointing-finger when hovering over them.
Can I just quickly mention that I for one really appreciate the work done by @ruul to keep this instance working as well as it does , thank you.
On the homepage lemmy.world, new posts keep appearing at the top even when not sorting by new. This causes annoying layout shift, especially when browsing all communities, not just local ones. (I use Firefox / Win 10)
I have the same issue. Makes the front page unusable with the flood of posts pushing everything down. Firefox / Win 11
See this: https://github.com/LemmyNet/lemmy/issues/3008
It will be fixed in the next release of lemmy, 0.18.
do you know when the next release is? the feed shifting around is getting annoying on desktop.
No idea, sorry.
This seems like a really big problem to me. I tried searching lemmy for it, but have not found anything conclusive.
I found a post or two claiming that the issue is that the API is implemented using websockets only, so it’s not as simple as just turning it off. I really hope that is not the case, since I currently can’t read anything on the frontpage that takes more than a few seconds!
In the comment listing, each comment first has an avatar, then the username, then the [—] button to collapse the comment thread. Observation: Because username length varies from comment to comment, the [—] button is in a different horizontal position. Consequence: As a user, it is tedious to collapse several comment threads because I have to search for that [—] button.
Request: put the [—] button as first item, to the left of the avatar and username.
I like this about the reddit UI where you can click anywhere on the vertical bar to collapse them. Collapse should be easier than the tiny button imo
Btw this also works on Jerboa, the Android app for Lemmy. You can basically tap anywhere in the message and it collapses.
The upvote/downvote (or whatever you call it here) sometimes freaks out a bit.
I’m trying to upvote this but it doesn’t seem to stick…
Same here. Upvotes never seem to work for me on either the app or web.
I get these random votes whenever I sort comments with anything else than the default sorting : it shows for it’s post’s votes.
There should be a way to set “my posting language is English” in my profile settings, so that it’s automatically set to English when I post, evern single time, unless I go out of my way to choose something different for a particular post.
New posts appear “live” at the top of the frontpage regardless of what sorting method is chosen. This disrupts the reading process and minimizes any expanded image view. Is there any way to disable this “live feed” behavior?
Also, the “sorting help” button points to a dead link.
Big +1 here. Mastodon provides a button to click to show new posts, maybe Lemmy could do the same
This is such a big issue for me I currently don’t really want to use Lemmy.
Just joined! Thanks!
One small thing i would add for sign up is giving a message about waiting for being approved for the community, i was confused that it sent me back to the homepage until reading the docs.
Yeah it is a bit hard to know if your account was approved or not as you get wheel of doom
oh nooooo…I may have tried to sign up over 20 times not knowing if it went through or not. sorry @[email protected] if I clogged your sign up list with my requests 😬
No problem
I scanned through the comments here and I don’t think it’s been mentioned yet, but I would love, love, love to have an option added to settings to open links in a new tab (or possibly windows if some people would prefer that). The current behavior is to open in the current tab, which I am so unaccustomed to I keep closing the tab when I’m done with it rather than hitting the back arrow.
It’s quite jarring to not open in a new tab these days, especially for external links.
Good idea. Suggestions can be submitted in their Github https://github.com/LemmyNet
Personally I think when clicking ‘Post’ it takes too long for it to be posted. I will see what I can do about this.
Also, there’s no local saving of the data in the post submition, so if there’s a server or connection error, you lose whatever you typed.
That’s something for the devs, maybe raise that at https://github.com/LemmyNet
Yeah. I’m making a list of issues/features I’d like to see so I can submit them as GitHub issues.
I’ve had multiple times where posting has just timed out
The hot sort appears to be frozen for the last 24 hrs. The top posts on all or local haven’t changed in nearly a day. There appears to be a bug causing a deadlock in the database (see issue 3076 for more info). The only solution seems to be to restart the instance when that thread crashes.
Yes as a workaround I restart the lemmy container every hour.
Thanks for the tip. That keeps my sort acting much better.
I’ve noticed that despite setting my default view to “All” in the user settings, my default view on the home page appears to be local.
It’s not the worst thing ever, since hitting All is not a problem, just interesting it doesn’t seem to work, unless I’m missing something!
Edit: It appears to have fixed itself, so maybe there was some time for the setting to kick in, although the local tab shows highlighted.
I’ve noticed a bug with that and created an issue for the devs, they will fix it.
deleted by creator
If I do Posts -> All -> Top Week (or any other Top) it will show the top posts at first, but after waiting a minute or so the page will update with new posts at the top. This is usually how I browse and it makes it unusable.
Another thing is when I tried to login after signing up, the loading wheel just spun forever without any error messages. Turns out I needed to verify my email.
The button “sorting help” links to a page that 404s:
https://join-lemmy.org/docs/en/users/01-getting-started.html/docs/en/users/03-votes-and-ranking.html
should probably be:
https://join-lemmy.org/docs/en/users/03-votes-and-ranking.html
Thanks, submitted bug report https://github.com/LemmyNet/lemmy-ui/issues/1348