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.
I also had the same issue on my first login (the email was verified, btw). The login button just went spinning and nothing happens. Trying the login on Jerboa gave me invalid credentials (it wasn't a mistype, because I used a password manager).
The workaround I did was to do a password reset and use a simpler one (was 50+ chars with special chars on, then changed to 32 chars and no special chars).
Not sure if what fixed was the reset itself, or the new password.
After this, the login went smooth on both the website and the app.
EDIT: And when posting this, the post submit button also kept spinning (the more than 200+ chars issue). But trying in a new tab, the message was actually sent.
And some minute later, on the old tab the message was sent, but the OP post changed from the "improvements and issues" to "The inability to post multiple pictures is holding Lemmy back.", but the comments below mine where for the "improvements and issues", while the comment above where to the other thread.
I think there is an issue with long passwords, I'll have to search their Github.
Submitting issue is known, it will take 30 seconds at least but the post is available immediately. That is being looked into.
The issue with posts changing and other strange behaviour I think is an issue with the websockets they use. In 0.18 they will replace websockets entirely so I hope that will solve many issues..
Change websockets to what, http? Its definitely a strange choice to be using websockets
Not really. They just screwed up the implementation and couldn't bother fixing it.
I've been trying to sign up for an account for a few days now and always get stuck on the spinning button. My password isn't overly complex as far as I can tell. I've tried multiple browsers and devices and can't create an account. I even left it running over night and it was still spinning in the morning.
Have you tried to go to login page, fill in with your email only and click on forget password? If this work, maybe there's also some issue not related with the password complexity
EDIT: (I mean, if you at least got the email verification)
Hey, it worked! I guess I missed the verification mail going to my junk folder. Thanks!