30
Lemmy.world improvements and issues - Lemmy.world
lemmy.worldIn 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. 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 ## 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
[https://lemmy.world/c/support].
I added some known issues with websockets / spinning wheel to the known issues post
Also still seeing lots of backend timeouts and slow responses, plus I somehow got logged out again (I logged back in after a few tries).
I begin to hate Lemmy’s web front end, because it uses so much asynchronous network stuff. The success path works somewhat ok when things are fast, but when things are slow (even if you don’t hit an error), you can never tell whether the screen state has caught up to the server state. We need an old fashioned synchronous front end, so if the browser says that a page has finished loading, you can know that what you see on the screen is the final state of the page.