446
Lemmy.world down, probably following the upgrade. A reminder to move to smaller instances for a better experience
(files.catbox.moe)
this post was submitted on 29 Jul 2023
446 points (93.1% liked)
Fediverse
17779 readers
39 users here now
A community dedicated to fediverse news and discussion.
Fediverse is a portmanteau of "federation" and "universe".
Getting started on Fediverse;
- What is the fediverse?
- Fediverse Platforms
- How to run your own community
founded 5 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
You're rocketderp based on your instability I'm guessing? Looks like your the only one that is nonsensical in that thread. Your PR isn't a PR. You were rushing to someone that was being helpful but you still acted like a child with your advise of GitHub bugs and PRs and not using them properly. The other person in agreement with you at least is calm and rational. I'm guessing you never worked on a group project before or have had anyone disagree with you. Your commits broke the pipeline. Someone even tried calling you down, but you wouldn't listen.
You aren't the victim here. You're the bully.
Yes. My name is Stephen Alfred Gutknecht. It is clearly detailed here on my profile that I am "RocketDerp" on GitHub.
Issue 2910? The word "nonsense" is being discussed about a Lemmy TRIGGER on June 4, 2023.
You would be guessing wrong. Since late 2019 I am in constant mental anguish and barely surviving. My communications is a constant struggle and I openly disclose this so that it is understood, I am not attempting to cover it up.
The "i'm guessing" game. And I note you can't actually cite the Github issues by number (2910) or keep details here in fact. A lot of "guessing" going on.
"guessing" again. Should I guess you do not know how difficult or easy it is to remove a TRIGGER in PostgreSQL that is causing server crashes?
Why do you think this is about "me"? I haven't donated money to the project or had blind faith in the developers.
I'm beyond frustrated that they seem to be going so far out of their way to have servers crash that their motives for doing so need explanation. "Social hazing" is the best answer I can come up with. I've now outright asked why they are dong it, because the pattern of behavior with trying to let server crashes has been going on now for months.
I have to admit that it's amazing the number of people they have attracted with the server crashing. It's been a social experience in some ways like Elon Musk is doing with Twitter. Perhaps it bothers me when other people actually seem to enjoy it. That seems to be the hiveMind reaction here. In that sense, if it is "social hazing", it has worked very well.
No.
The feature you suggest be ripped out is one that many people like. I've seen people say they hate Mastodon because "Likes" are only counted on the local server and they feel it's useless. You can't just suggest rip it out without a fix in its place.
Do we even know the read/write operations of the database are what's pulling it down when it crashes? Sure it's not the best code I've seen, but on large instances it still manages quite the uptime. Without insight into the cause of the crashes, you can't honestly say "this, this right here." Could it help? Probably. Do you need to suggest someone enjoys murdering people because they don't immediately implement something? Probably not.
Just because you can't think of another reason why they didn't listen to you, it doesn't mean that the one you thought of is correct. That's not how logic works. It's narcissistic to believe that you can think of every explanation for something that's happening.
ok, I've come to terms. I posed an apology just now on github, and I apologize to you.
I see now that people value the social outcomes of how they run the project far more than I realized.
I didn't say anything, I was entirely silent, when the June 4 2023 issue 2910 was opened. So I don't grasp why you think this is all about me. I never thought this was about me. The June 30 Reddit API deadline was what I thought this was all about when I was witnessing this.
I didn't do pull request and add a new developer in the mix in June because it was such an easy problem to fix. It was when on June 13 that they still had not responded to the June 4 issue 2910 and did hardware upgrades on lemmy.ml that I started to interpret the situation differently. Instead of responding to Issue 2910 on Github, that same day on June 13 I started organizing Lemmy-specific PostgreSQL instructions on [email protected] because servers were crashing even after the hardware upgrades.
I now realize, today, that my whole approach to this comes from experience running PostgreSQL in "mission critical" applications. What I have done with DB/2 and PostgreSQL wasn't driven by social loyalty and "Taking on the Big Guys of Reddit and Twitter" that happens here. I've been all wrong to think that the developers don't know exactly what they are doing. It's like criticizing Hollywood for spending 3 million dollars on sets and clothes for 90 seconds of a film. I should have realized I was not understanding that social media sites run by social behavior models, not by technology concerns.
Elon Musk has done wild things since he took over Twitter and I didn't take it so personal. I guess it was my memories and personal experience with PostgreSQL that haunted me too much. I was wrong. And i see how the lemmy community is loyal, so I can see just how wrong I am about the choices being made.
You jumping to politics and weird accusations of folks supporting murder as being the only reason they didn't fix a postgres bug because, by your own words, you couldn't think of any other reason.
You clearly have issues communicating and you are admittedly self aware yet you refuse to ever believe maybe those issues are the root of your arguments.
I could list 50 reasons I could think of. Many of which would be even more offensive. I didn't sit patiently by watching June 4 issue 2910 go ignored because I was trying to over-react. In fact, I couldn't believe what I was seeing as they upgraded hardware June 13 and continued to ignore the June 4 issue on Github. Even further when June 30 deadline for Reddit API came.
I have been very wrong in how I dealt with it this past 10 days, as I did not come to understand how much the community has come to enjoy the environment of Lemmy. Talking to you has enlightened now just how socially driven the whole platform is and that any training and experiences I have running mission-critical apps with PostgreSQL and DB2 on production servers do not apply here and I should have realized just how wrong my social interpretation of the situation has become.
It's like watching the recent Nolan film release of Oppenheimer on IMAX. The massive size of the platters and how projectors have run into problems on opening night / first few days of showings. It's about the style and cool factors, just because Lemmy uses PostgreSQL I considered reliability to be important, but now I clearly see I socially failed to understand how much the community here has come to adore Lemmy history and progression.
Rock Stars being criticized about their style and use of the technology was a huge mistake on my part. It's all about putting on entertainment people like and the fans of the project are loyal to how it is done. I have been far too slow to recognize the "cool factor" of the Rock Star cultivation happening in front of me. I'm worried about the tire engine maintenance costs on an exotic sports car that draws huge crowds. Sorry I did not grasp that the crowds were so enamored and how that drives the project choices.
Heavy drinking, first time since New Years, reset my brain and I now re-interpret everything I learned about Lemmy history in a new light.