June 4, 2023 is when I felt I had to get involved. And June 8, 2023 is when I crated my own testing-focused experimental Lemmy install that compiled Main from GitHub source and ready to test the changes I thought were surely going to come to the SQL because of GitHub issue 2910. I wanted to test the code that that developers who had been working and running lemmy.ml for over 4 full years - would surely address. It was June 4 with Issue 2910, the June 30 Reddit API cutoff deadline countdown was well under way. Lemmy.ml put in major hardware upgrades on June 13, 2023 - and I was puzzled why such an easy 2 or 3 hour fix for Issue 2910 wasn’t put in… but I still had hope that everyone would see the pending countdown to June 30 API deadline and a fix could go in within 10 days - by June 23… for some slack time before June 30…

Watching Beehaw, up and running for 17 months on Lemmy - crashing constantly… I thought, surely the developers were seeing Issue 2910 happening over there… but June 28 came, June 29 came, June 30… nothing. With 4 years of experience on the Rust code base and such, they were the ones to fix Issue 2910… but from June 4 to June 30, it just didn’t happen.

  • RoundSparrow @ BTOPM
    link
    fedilink
    1
    edit-2
    11 months ago

    My regrets compounded when I sort of forgot about https://github.com/derivator/tafkars like everyone else did by early July… a month after it had been created… and it would have been a way for me to channel my skills instead of hoping the situation with Issue 2910 would turn around quickly. Even after 30 days, a few-hour fix to 2910 hadn’t been put in.

    Did I get caught up in all the “Fuck Spez” negativity of Lemmy community? Beehaw was the most positive and had been up for 17 months with their positive approach. Did I get sucked into the hate of Reddit and hate of Elon Musk emotions and not see it?

    I really regret when I go back and see the June 7 creation of https://github.com/derivator/tafkars - that I didn’t either think of it myself or jump in with contributions to a fully independent project that would offer a solution that didn’t require the two entrenched developers of lemmy_server to change their pace or focus. Beehaw was on fire, and tafkars project would at least have been a way to view all this from an API perspective.

    Did the negativity of hating Spez and corporate power - even the massive hate that everyone was screaming on Lemmy platform about Zuckerberg and “Threads” coming along on July 5… did it get into my head?

    1. May 20 2023 - a huge amount of hate surging with “Fuck Spez” and mod community planned outages protest
    2. June 30 the massive community hate towards Reddit
    3. July 5 - Zuckerberg and Threads. Massive hate response from the Lemmy platform.
    4. July 23 - Elon Musk pulls another massive change, the Twitter to X rename - a world-wide mind-fuck given how many news organizations have made Twitter one of the most-repeated words on the planet.

    I should have been reading my Finnegans Wake and keeping my mind clear. The Reddit HiveMind clashes, the Lemmy platform HiveMind hate towards Threads and Twitter…

    Beehaw is like a lighthouse in all the hate-oriented surges of people motivated by anger and hate, and I see now I lost my way in the competing waves of hate-focused HiveMind reactions.

    • RoundSparrow @ BTOPM
      link
      fedilink
      1
      edit-2
      11 months ago

      https://github.com/derivator/tafkars

      This API proxy approach could be useful for more intelligent rate-filtering than built-in Lemmy has, API redirection for specific calls, and even the basis for spam filtering. I haven’t seen people remark about the lack of spam on lemmy. On Reddt, I’ve seen routine bots hit communities with t-shirt selling spam, etc. I wonder if other parts of the federated network have had to implement spam filtering.

    • @adminsagMA
      link
      fedilink
      111 months ago

      This is a test comment to see how front-end gets notification.