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.
Certain communities seem to be inaccessible from Lemmy.world and vice versa. For instance, if I try to access /c/boston in Lemmy.ml via lemmy.world/c/[email protected], I get a “404: couldnt_find_community” error. Similarly, trying to access /c/boston in Lemmy.world from either Kbin.social (via kbin.social/m/[email protected]) or Lemmy.ml (via lemmy.ml/c/[email protected]) both give 404 errors.
I’ve observed the same thing, newer lemmy.ml communities and pretty much everything from kbin returns 404 when accessed through this instance. It happens with other instances, to a varying degree, mostly with lemmy.ml. However [email protected] is accessible from beehaw but 404s from lemmy.world.
Strange! Does that possibly mean there’s an issue with federation on the lemmy.world side?
Hmm works for me, I can find it and open it. Maybe lemmy.ml was overloaded?
Yeah possibly! I think the second issue I mentioned is still occurring, though. Namely, lemmy.ml/c/[email protected] returns a 404 error (and also for Kbin.social).
Then I think lemmy.ml hasn’t discovered it yet, maybe there’s delay on their server?
Perhaps! This should be triggered by searching “[email protected]” from lemmy.ml, correct?
Yes, but as the server is overloaded, it might take some time.
Sounds good, I’ll check back another time, thanks for looking into it!
Yes