Lemmy.ml front page has been full of nginx errors, 500, 502, etc. And 404 errors coming from Lemmy.
Every new Lemmy install begins with no votes, comments, postings, users to test against. So the problems related to performance, scaling, error handling, stability under user load can not easily be matched given that we can not download the established content of communities.
Either the developers have an attitude that the logs are of low quality and not useful for identifying problems in the code and design, or the importance of getting these logs in front of the technical community and trying to identify the underlying patterns of faults is being given too low of a priority.
It’s also important to make each log of failures identifiable to where in the code this specific timeout, crash, exception, resource limit is encountered. Users and operations personnel reporting generic messages that are non-unique only slow down server operators, programmers, database experts, etc.
There are also a number of problems testing federation given the nature of multiple servers involved and trying not to bring down servers in front of end-users. It’s absolutely critical that failures for servers to federate data be taken seriously and attempts to enhance logging activities and triangulate causes of why peer instances have missing data be track down to protocol design issues, code failures, network failures, etc. Major Lemmy sites doing large amounts of data replication are an extremely valuable source of data about errors and performance. Please, for the love of god, share these logs and let us look for the underlying causes in hard to reproduce crashes and failures!
I really hope internal logging and details of the inner workings of the biggest Lemmy instances is shared more openly with more eyes on how to keep scaling the applications as the number of posts, messages, likes and votes continue to grow each and every day. Thank you.
Three recently created communities: !lemmyperformance@lemmy.ml – !lemmyfederation@lemmy.ml – !lemmycode@lemmy.ml
I like your posts and hunt for performance issues, I just think that developers decided (wether you and I agree or not) some other features are more important.
Until few weeks ago communication was clear since there were not many people here, so there was no need for some specific notes you are mentioning.
Now we do need them and reminding developers of it, or even better doing it would be much appreciated I expect.
I have seen developers on some threads here or on github issues commenting on repication problems and they are hard at work for those.
Even caching is discussed, as I understand, they first need to implement cache control headers so that admins can set up caching, as they see fit, outside lemmy.
There is a lo of good will around, please have understanding and be part of it. Give the time to grow up to this opportunity.
Where? On Lemmy? Why do they think Lemmy isn’t good enough to discuss Lemmy?
Sure a lot of people in denial that"eat your own dogfood" is a concept in development. You are creating a messaging system, why aren’t you using it?
End-user comments not making it out of a server to peer servers is unimportant. That is how I would describe the Lemmy Release Notes for 0.18 - that is how I would describe the response I got to the GitHub issue I opened…
I see you want me to shut my mouth up and not be honest about how unreliable Lemmy is. I’ve been authoring social media messaging apps since 1984. But tell me to “grow up”. The project management doesn’t need to “grow up”, when you can’t even see them using Lemmy to discuss Lemmy programming and database design?
So far, this community is insular and “Feedback not welcome” has been the response. Lemmy branding mania with no reality about how unstable and unreliable Lemmy is right here, right now.
I understand their GitHub comment is a little confusing, but interpreting it as telling you to grow up is… telling.
Please explain it to me then, if I misinterperted?
The creators of Lemmy have misinterpreted how to read books on when to add caching layers to a webapp, and how to test with significant amounts of data.
Am I misinterpreting the project management’s incompetence and areas that need improvement?
Help me out in interpretation please, i have autism, and I don’t always interpret things the same as other people. In fact, i question if people take interpretaiton for granted and like mocking and insulting each other as a way to deflect truth and honesty in social matters.
I interpreted the 500 errors on the front page of Lemmy.ml with 40 years of social media application development expertise under my belt. Maybe it is you who is interpreting the code development, server operations and how badly it iis being done wrongly? Do you know how to interpret the pattern of nginx 500 errors and missed federation comment replication?
Are you gaslighting me,m intimidating me as a human person, dehumanizing me?
Yes I was trying to do exactly all those things, you got me.
And I’m autistic too. That doesn’t preclude you from having a superiority complex or just being an asshole.
Yes, I did get you, as you obviously can not talk about the lack of sharing logs from the busy server that was crashing hourly / falling over itself under moderate load.
Yes, check yourself, you already admitted “yes” that you are gaslighitng me. That you are trying to intimidate me. I’m sorry you have been abused so much for being autistic and are afraid of facts and truth about an open source project that’s being mismanaged. That your identity with a software application exeeds your love for human persons. Maybe read BIble page “1 John 4:20” for inspiration. You clearly seem like a damaged individual that society has harmed.
My name is Stephen Alfred Gutrknecht, what’s your name since we are sharing personal details about our mental health? I created community !autistic_adults@lemmy.ml as one of the first things when I joined lemmy.ml - and I also run a information website, because I find many autitics hide behind a ‘tough guy’ personona and don’t stand up for truth and honesty about the situation. www.GutknechtAutism.org - nice to meet you, and I hope you can turn away from using intimidation and gaslight tactics about obvious and serious problems in an open source Rust software project.