YSK: Hitting submit more than once will post your comment/thread multiple times, even with the lag
YSK: Hitting submit more than once will post your comment/thread multiple times, even with the lag
With the sluggishness of the site these last few days you can sometimes get slowness or infinitely loading icon when hitting submit. If you aren't sure if your post submitted, refresh the original page in a different tab before hitting submit again to see if it went through. I see double and triple posts in almost every comment section.
You're viewing a single thread.
This is especially bad on really popular instances like lemmy.world. It seems the server can't keep up with all the requests or something along those lines.
Some of the apps like Memmy throw an error and then leave you back at the comment screen. Most people probably try again because the comment and submit button is right there.
What they donât realize is that despite the error, most times the server has accepted the comment.
Donât get me wrong, I love Memmy (itâs been my primary driver) but this one error combined with poor performance of the lemmy.world instance (also not their fault, growing pains are a good problem to have! Hopefully not for too longâŠ.) is probably a significant contributor to this issue since many people probably donât realize what the error means since it only says âsyntax error: JSON Parse Error - unexpected token â<ââ which doesnât mean anything if you donât speak nerd.
(For anyone who might wonder: if you are expecting json data which looks {âlikeâ:âthisâ,âwithâ:âcurly bracesâ} and instead you get a 500 Server Error web page which is an <html><body>Because the server is sending an error explain for a human to read displayed in browser</body></html> then your program gets confused why there is a < at the start instead of a { and now maybe the error text seems a bit less cryptic)
EDIT: Good lord, the irony
Is there a way to load balance these lemmy instances across multiple backend servers?
Yes, and I think they are.
Backend sizes likely need to be larger and more abundant. Depending on hosting provider this could be mean lighting your wallet on fire every month till you either get enough donations to make up for it, or you give up and shut it down.
This problem will only get worse as Lemmy increases in popularity from "extremely niche, extremely low volume"/trivial volume (~50-100k users) to anything other than that (1mill - 100mill users or further). And gets more difficult since economies of scale may be difficult to apply here due to the hosting model of Lemmy, meaning cost/user is likely to stay quite high when normally it would be drastically reduced the more users you have.
I'm gonna guess individual instances are going to be forced to break down into instances that host only a couple communities each as time goes on. This would be the pragmatic choice since it's very likely that individual communities can grow large enough to tank Lemmy instance performance for all others on that instance. Although that presents non-trivial UX concerns.
Though, again, many smaller scale instances means infrastructure costs may stay prohibitively high as a result of over provisioning or a lack of value from aggressive caching, read replicas...etc đ€
Edit: I wonder if an instance can host individual communities on their own hardware. Or if there is some abstraction that lets users browse potentially hundreds/thousands of instances easily as if they where all communities?
I agree that having many smaller instances which serve more distinct communities is by far the most pragmatic choice. The idea of communities distinct from instances is nice on paper, but it gives instance managers the impression a single instance can serve a wide-range of interests without incurring proportional overhead on the resources.
Lemmy is the closest thing we have to the evolution of reddit. So far it's just a matter of handling the backend which was nearly always done by a well-resourced organization instead of individual volunteers. I think instances will naturally become more abundant, and specific to their purposes, and users will be able to distribute their accounts accordingly.
Some of the apps like Memmy throw an error and then leave you back at the comment screen. Most people probably try again because the comment and submit button is right there.
What they donât realize is that despite the error, most times the server has accepted the comment.
Donât get me wrong, I love Memmy (itâs been my primary driver) but this one error combined with poor performance of the lemmy.world instance (also not their fault, growing pains are a good problem to have! Hopefully not for too longâŠ.) is probably a significant contributor to this issue since many people probably donât realize what the error means since it only says âsyntax error: JSON Parse Error - unexpected token â<ââ which doesnât mean anything if you donât speak nerd.
(For anyone who might wonder: if you are expecting json data which looks {âlikeâ:âthisâ,âwithâ:âcurly bracesâ} and instead you get a 500 Server Error web page which is an <html><body>Because the server is sending an error explain for a human to read displayed in browser</body></html> then your program gets confused why there is a < at the start instead of a { and now maybe the error text seems a bit less cryptic)
Some of the apps like Memmy throw an error and then leave you back at the comment screen. Most people probably try again because the comment and submit button is right there.
What they donât realize is that despite the error, most times the server has accepted the comment.
Donât get me wrong, I love Memmy (itâs been my primary driver) but this one error combined with poor performance of the lemmy.world instance (also not their fault, growing pains are a good problem to have! Hopefully not for too longâŠ.) is probably a significant contributor to this issue since many people probably donât realize what the error means since it only says âsyntax error: JSON Parse Error - unexpected token â<ââ which doesnât mean anything if you donât speak nerd.
(For anyone who might wonder: if you are expecting json data which looks {âlikeâ:âthisâ,âwithâ:âcurly bracesâ} and instead you get a 500 Server Error web page which is an <html><body>Because the server is sending an error explain for a human to read displayed in browser</body></html> then your program gets confused why there is a < at the start instead of a { and now maybe the error text seems a bit less cryptic)
Some of the apps like Memmy throw an error and then leave you back at the comment screen. Most people probably try again because the comment and submit button is right there.
What they donât realize is that despite the error, most times the server has accepted the comment.
Donât get me wrong, I love Memmy (itâs been my primary driver) but this one error combined with poor performance of the lemmy.world instance (also not their fault, growing pains are a good problem to have! Hopefully not for too longâŠ.) is probably a significant contributor to this issue since many people probably donât realize what the error means since it only says âsyntax error: JSON Parse Error - unexpected token â<ââ which doesnât mean anything if you donât speak nerd.
(For anyone who might wonder: if you are expecting json data which looks {âlikeâ:âthisâ,âwithâ:âcurly bracesâ} and instead you get a 500 Server Error web page which is an <html><body>Because the server is sending an error explain for a human to read displayed in browser</body></html> then your program gets confused why there is a < at the start instead of a { and now maybe the error text seems a bit less cryptic)
