this post was submitted on 07 Oct 2024
441 points (92.8% liked)

Ye Power Trippin' Bastards

484 readers
36 users here now

This is a community in the spirit of "Am I The Asshole" where people can post their own bans from lemmy or reddit or whatever and get some feedback from others whether the ban was justified or not.

Sometimes one just wants to be able to challenge the arguments some mod made and this could be the place for that.

Rules

Expect to receive feedback about your posts, they might even be negative.

Make sure you follow this instance's code of conduct. In other words we won't allow bellyaching about being sanctioned for hate speech or bigotry.


Some acronyms you might see.


Relevant comms

founded 4 months ago
MODERATORS
 

Also outs your report publicly, nice !

you are viewing a single comment's thread
view the rest of the comments
[–] [email protected] 24 points 2 months ago* (last edited 2 months ago) (1 children)

It's what you are describing, and it's not a client problem. It's impossible for a client to solve. You can't tell whether a timed out request succeeded or not.

Idempotent network requests are a standard feature of many APIs - sending the same request multiple times should result in only one action being performed, but Lemmy doesn't support them yet.

So yes, it's "caused" by retries, but the bug is that the backend doesn't properly support retries. Clients don't do anything wrong.

[–] [email protected] 3 points 2 months ago* (last edited 2 months ago) (1 children)

It could/should be handled by the server but it's technically possible for the client to make due without it. You would need to handle it very carefully. For instance on timeouts, you can issue a get request to see if the comment posted. If it did then you do not issue another post.

[–] [email protected] 2 points 2 months ago

Sure, that would work, but it's a hacky solution, and involves needing to send more requests in a scenario where requests are already unreliable.