Lemmy.world improvements and issues
Lemmy.world improvements and issues
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.
You're viewing a single thread.
Any idea why I can't open https://lemmy.world/c/[email protected]? Mander.xyz should be federated. I just get
404: couldnt_find_communityCould you try it again now? I did a search for the community on here and afterward was able to open it via your link, but I want to confirm it's not just me.
Edit:
If it works for you now, I think it was related to the community not being searched/seen by the instance just yet despite us being linked to mander.xyz.It works for me now, thank you. I guess there's just a delay in pushing/pulling things from different instances?
In a way, yeah. From your experience I'm getting a better sense that if a community on another instance hasn't been searched on your instance, it won't have fetched it yet.
What I did was I went to the top navbar and searched [email protected] to get lemmy.world to fetch it. Took a few seconds but it did! I think if it had been on an instance lemmy.world's not linked to yet though, you'd want to copy the URL of the instance including community, e.g. https://lemmy.world/c/lemmyworld
Nice, good info to know. I've been using this browser extension to speed up subscribing to communities across different instances, so I end up just loading the URL directly rather than searching for it on lemmy.world. I'll make sure to try searching next time if I run into the same problem.