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.
Issue:
So, I've created !childfree as a local community, seemingly normal. Only, it doesn't seem to be accessible to anyone locally.
Meaning, https://lemmy.world/c/childfree gives me a 404. Instead, I have to open it as https://lemmy.world/c/childfree@lemmy.world - initially I thought maybe I had made an error creating the community and added the instance, but trying to replicate it shows that @ is not a permitted character, so the problem must have come from elsewhere.
From other instances now I can access it just fine: https://latte.isnot.coffee/c/childfree@lemmy.world or https://feddit.de/c/childfree@lemmy.world (where the @instance is the default behaviour). Locally however, that should not have happened.
Even if I enter the community locally, and click on the !childfree just below the name of the community, it gives me a local 404 (see below).
Any idea what's going on here, and how to resolve the problem? Since we are redirecting users from our sub here, it's creating quite some headaches... And apparently users trying to subscribe from other instances also don't see any posts for up to 48h (tried that myself).
Edit: Apparently I cannot access the community via feddit.de. The other one works fine though - I do have accounts on either instance.
Same with https://lemmy.world/c/titanfall
https://lemmy.world/c/titanfall@lemmy.world works
https://lemmy.world/c/titanfall does not and gives a 404
And similarly when going via feddit.de, i.e. https://feddit.de/c/titanfall@lemmy.world I can see the community but only 1 out of the 2 posts.
I think OP comment and my issue are related. What can we do to help investigate this? I was planning on moving over a community from reddit and this is unfortunately blocking it. If I can help in any way to figure this out and resolve it, I'd be more than happy to do so <3