We’re still working to find a solution for the posting slowness in large communities.
We have seen that a post does get submitted right away, but yet the page keeps ‘spinning’
So right after you clicked ‘Post’ or ‘Reply’ you can refresh the page and the post should be there.
(But maybe to be sure you could copy the contents of your post first, so you can paste again if anything would go wrong…)
Keep in mind that the upcoming Lemmy update will probably fix this I think. (Replacing websockets)
Maybe this is a dumb question, but why would replacing websockets speed things up? I read the Wikipedia page on it, but I guess I don’t understand it fully.
In general websockets scale badly because the server has to keep open a connection and a fair amount of state. You also can’t really cache websocket messages like you can normal HTTP responses. Not sure which reasons apply to Lemmy though.
Just hopping into the chain to say that I appreciate you and all of your hard work! This place—Lemmy in general, but specifically this instance—has been so welcoming and uplifting. Thank you!
maybe related, but I’ve noticed that upvoting/downvoting has similar lag delays
At least the “reply” button goes away so I don’t end up double- triple- or even duodecuple-posting! Thanks for all the hard work that must be going on behind the scenes right now!
I kept getting a timeout message from Jerboa which led me to think I hadn’t been posted. So I ended up submitting the same joke to the Dad Jokes sub three times. Which actually is how dad might tell that joke.
I get this occasionally with Jeroba too, I had assumed it was because I’m on Mint and the connection is shoddy but maybe it’s an issue with the client.
I came here looking for information on this exact thing and judging by a couple of posts I found through Google on other Lemmy instances, it seems to be a Lemmy.world specific problem with Jerboa. So probably connected to the community slowness?
Been noticing this in the app I’m working on. Pretty much all POST requests fail to return a response and just timeout after 60 seconds. A quick refresh shows that the new items do successfully get created though.
