Lemmy.world is very popular, and one of the largest instances. They do a great job with moderation. There’s a lot of positives with lemmy.world

Recently, over the last month, federation issues have become more and more drastic. Some comments from lemmy.world take days, or never, synchronize with other instances.

The current incarnation of activity pub as implemented in Lemmy has rate issues with a very popular instance. So now lemmy.world is becoming a island. This is bad because it fractures the discussion, and encourages more centralization on Lemmy.world which actually weakens the ability of the federated universe to survive a single instance failing or just turning off.

For the time being, I encourage everyone to post to communities hosted on other instances so that the conversation can be consistently access by people across the entire Fediverse. I don’t think it’s necessary to move your user account, because your client will post to the host instance of a community when you make a comment in that community I believe.

Update: other threads about the delays Great writeup https://lemmy.world/post/13967373

Other people having the same issue: https://lemmy.world/post/15668306 https://aussie.zone/comment/9155614 https://lemmy.world/post/15654553 https://lemmy.world/post/15634599 https://aussie.zone/comment/9103641

  • JonsJava@lemmy.worldM
    81·
    7 months ago

    As a DevOps Architect, let me make it simple:

    With a single front-end, you have a bottleneck. If you have one domain (website) that everybody goes to to get to the front-end, that means that domain is the single point of failure.

    In my line of work, we use load balancers and sub-domains to divide the work and provide resilience (High Availability), but at the end of the day, if the DNS for that site goes down, we’re down.

    Also, as Jet mentioned, whomever whoever controls the domain (website) controls the content. You can’t have multiple groups controlling a single domain. Whomever buys it controls it. If they don’t like content, they could easily block access to it.

    I’m oversimplifying the inner workings, so if you want more details, let me know.

    EDIT: subtext called me out on my crap English. Have nobody to blame but myself. English is my first language.

    • subtext@lemmy.worldEnglish
      5·
      7 months ago

      I just want to let you know that “whom” is only ever used as an object. In your sentences, I think you should have used “whoever”.

      The easiest way to remember which you should use is to think about the difference between s/he==who and her/him==whom.

      She gave the ball to him Who gave the ball to whom

      She controls the domain Who controls the domain

      The domain is controlled by him The domain is controlled by whom

        • subtext@lemmy.worldEnglish
          3·
          7 months ago

          I’m pretty sure most adults suck at writing so you’re no worse than the regular person!

    • Kecessa
      2·
      7 months ago

      In this case the solution, as I mentioned in other comments, is to make the back end the decentralized database that’s accessible to anyone so the people developing a front end don’t host the data and you can use any of the available front ends to connect to your account as it’s not attached to any specific front end (your info is in the database).

      Front end devs would be competing to provide the best UI/UX, but in the end everyone would have access to the same data and front end devs couldn’t get in the way of the data or if they did then people could just go to another website without losing anything.