Hey all, I am having trouble submitting requests this morning to Lemmy.ca. Creating posts (like this one) I attempted 3 times all of which failed to complete their requests after minutes of waiting.

Beefier servers needed? More caching? Sure, let’s do that. That said, I think there should be some UI improvements on the client side that improve the experience when we do encounter flakey servers.

My suggestion is to time out on the high-request-count workloads on the client side so that you’re not accidentally hammering the server with requests that won’t complete. Client side js code should convert a request like the create post green button to a error / retry button with text explaning what happened (hey the request timed out after x seconds).

I don’t imagine /create_post is a high throughput endpoint, but suffice it to say that my request continued to wait in the queue patiently for the server to never respond and it was also a frustrating client-side experience. Other endpoints are probably the culprit behind any excessive server use.

Client-side it should time out after 15-30 seconds, if not less, so that I’m not just waiting and re-typing everything into the create post form again (because there’s no way to retry if it’s still waiting for the server response!). Re-typing everything in is the worst!