if only I had known this earlier
this post was submitted on 04 Jul 2023
735 points (98.7% liked)
You Should Know
33116 readers
483 users here now
YSK - for all the things that can make your life easier!
The rules for posting and commenting, besides the rules defined here for lemmy.world, are as follows:
Rules (interactive)
Rule 1- All posts must begin with YSK.
All posts must begin with YSK. If you're a Mastodon user, then include YSK after @youshouldknow. This is a community to share tips and tricks that will help you improve your life.
Rule 2- Your post body text must include the reason "Why" YSK:
**In your post's text body, you must include the reason "Why" YSK: It’s helpful for readability, and informs readers about the importance of the content. **
Rule 3- Do not seek mental, medical and professional help here.
Do not seek mental, medical and professional help here. Breaking this rule will not get you or your post removed, but it will put you at risk, and possibly in danger.
Rule 4- No self promotion or upvote-farming of any kind.
That's it.
Rule 5- No baiting or sealioning or promoting an agenda.
Posts and comments which, instead of being of an innocuous nature, are specifically intended (based on reports and in the opinion of our crack moderation team) to bait users into ideological wars on charged political topics will be removed and the authors warned - or banned - depending on severity.
Rule 6- Regarding non-YSK posts.
Provided it is about the community itself, you may post non-YSK posts using the [META] tag on your post title.
Rule 7- You can't harass or disturb other members.
If you harass or discriminate against any individual member, you will be removed.
If you are a member, sympathizer or a resemblant of a movement that is known to largely hate, mock, discriminate against, and/or want to take lives of a group of people and you were provably vocal about your hate, then you will be banned on sight.
For further explanation, clarification and feedback about this rule, you may follow this link.
Rule 8- All comments should try to stay relevant to their parent content.
Rule 9- Reposts from other platforms are not allowed.
Let everyone have their own content.
Rule 10- The majority of bots aren't allowed to participate here.
Unless included in our Whitelist for Bots, your bot will not be allowed to participate in this community. To have your bot whitelisted, please contact the moderators for a short review.
Partnered Communities:
You can view our partnered communities list by following this link. To partner with our community and be included, you are free to message the moderators or comment on a pinned post.
Community Moderation
For inquiry on becoming a moderator of this community, you may comment on the pinned post of the time, or simply shoot a message to the current moderators.
Credits
Our icon(masterpiece) was made by @clen15!
founded 1 year ago
MODERATORS
I mean you have 2 comments total (this one and a duplicate of this one) it isn't really too late ;)
I hope you have learned the error of your ways
lol
load more comments
(1 replies)
if only I had known this earlier
lol
This is good to know. Upvoted for visibility.
This is the way
This is the way
People are forgetting that a lot of these Lemmy servers are being run by just a couple people, sometimes with a server in their basement lol
Or literal closet. >_>
This is good to know. Upvoted for visibility.
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 Because the server is sending an error explain for a human to read displayed in browser 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?
load more comments
(1 replies)
load more comments
(4 replies)
This is good to know. Upvoted for visibility.
You should also know you can join smaller instances to help alleviate this problem. You'll still see most of the same content, especially if the instance has active users. Don't be too shy to sign up on some random instance, worse case scenario you just don't get approved.
I joined my instance after being on Lemmy.ml about a month ago for a day, and there was so much lag because it was the largest instance at the time. I then switched to my current instance when it only had ~50 users on it and it made the world of a difference. I went from seeing the site crash every 5 seconds and posts taking 30 seconds to submit, to having a stable connection to the Fediverse.
Overall, I feel like everyone should try to join smaller instances to distribute the load so that you don’t have a bad experience, and the instances don’t get overwhelmed. It’s a win-win for everyone.
Just to add to this, at least in wefwef, I sometimes get an error when I tap Post, saying that it failed. I am then left on the page, and can hit Post again. But it didn’t fail the first time, the post was made.
So this is not just users being impatient. There is a bug.
Might be due to either the websocket removal, or the sluggishness that does it.
The post processes, but the app doesn't get a response confirming that the post has been made, so it sits there until the app times out.
I have not written real code for a very long time, and I don’t know the lemmy code base at all… but I described this bug to GPT-4 and it just turned me on to idempotency.
https://stripe.com/blog/idempotency
The call could succeed, but the connection breaks before the server can tell its client about it.
Seems like it’s non-trivial to implement in rust.
I've had the same on Liftoff
See what I did there....?
I've had the same on Liftoff
It's just Lemmy admins trying to give us the true Reddit experience
You know, we don't have to copy everything from Reddit. Although it is pretty funny that we have exactly the same bug lol
I expect some aspects of the internet will never change
Funny enough, this post is still "submitting" Image of the submit button still spinning on this post
Just get off .World and onto another instance and it’s smooth sailing with mobile apps working great too.
Unless you try to interact with .world
programming.dev is getting to be pretty damn slow too...
Comments post in 5-30 seconds, and up votes can take 30+ seconds to post. Searches are pointless, and loading comments can be a repetitive painful process of reloading till it works (504 gateway timeout)
Yes! The Lemmy devs should make it so that you can't hit the submit button 10 times in a row. People hit submit and nothing happens so they hit it again and again and again. Now there's a bunch of identical posts.
I remember the old days where sites would have a message saying "only hit submit once". That's gone now since sites prevent users from hitting submit more than once. I don't think Lemmy is doing that though!
You should be able to hit the submit button as many times as you want, but it should have a single transaction ID so the server can ignore duplicate submissions.
load more comments
(1 replies)
It's problematic because often you'll get an error that says it failed to post the comment. In which case it's fair to try again, but it actually posted anyways.
I can confirm this is true in Jerboa; learned the other day the hard way.
Sounds like a bug to be that needs to be ironed out on the backend 😉
...And I learned that I need to copy the whole comment I type before submit jic my comment didn't upload, at least I have my comment restored.
I said I was sorry... Gosh
Resubmitting is the reasonable response to an error that said it failed. Lemmy should add some sort of duplicate message prevention when they have the time to improve the ux.
Admin needs to sticky something to this effect.
What I do (web browser) is simply refresh the community to see if the post has posted yet. If it hasn't, I try again. Around a third of the time you get spinny wheel though, it actually did submit, and just forgot to let you know.
Also note that if a large amount of time has passed while you're writing a response, you'll sort of time out, and the first attempt to post won't work, but because it's refreshing your session. The second attempt will post
Even for short ones, it seems to happen always for me if I reply to one person, then try to write a top-level reply after that.
load more comments
(1 replies)
I literally posted the same comment 8 times because of that 💀💀💀
The problem is a UI thing too. In wefwef for example half the time you go to post something and it says ‘error posting’, your comment actually did post. But sometimes it doesn’t.
I typically go until I see success and then delete any duplicates I left on accident.
Only sometimes. Other times it won't post your comment at all. I still check to make sure my comments don't post more than once but sometimes the lag is so bad it's impossible to do even that.
I've been finding uploading images to be very confusing as the 'upload file' and 'From url' buttons don't seem to do anything
view more: next ›