Just because you can’t think of another reason why they didn’t listen to you
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 !lemmyperformance@lemmy.ml 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.
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 !lemmyperformance@lemmy.ml 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.