…and why is it often PAINFULLY slow to acknowledge an up/down vote or to open the reply dialog?

  • mr. ed's butler alfred@lemmy.world
    link
    fedilink
    arrow-up
    31
    ·
    11 months ago

    I’ve never admined a lemmy server but rate limits are probably why it feels slow.

    Federation works by each server sharing new activity with each other and rate limits help not crash the server or accidentally DOS smaller servers.

  • Zak@lemmy.world
    link
    fedilink
    arrow-up
    23
    ·
    edit-2
    11 months ago

    Your server sends a message to other servers saying what you voted or replied.

    A reply dialog being slow to open sounds like an issue with your client, not federation.

    • Agrivar@lemmy.worldOP
      link
      fedilink
      arrow-up
      9
      ·
      11 months ago

      Huh. I’m just browsing Lemmy in a Firefox tab - and the reply dialog sometimes opens right up and other times leaves me wondering if I really hit that button! I wasn’t sure if that was another thing where my instance had to “ask” the federation if I could reply before giving me the dialog or something.

      • can@sh.itjust.works
        link
        fedilink
        arrow-up
        15
        ·
        11 months ago

        As far as I understand it federation shouldn’t have anything to do with commenting on your own instance but rather after when it gets sent to other instances.

        • NaN@lemmy.sdf.org
          link
          fedilink
          English
          arrow-up
          6
          ·
          11 months ago

          It doesn’t. Even if you defederate with an instance, you can still comment and vote on posts from that instance that predate the defederation and people on your instance will see them, it just won’t go to the original one.

          • can@sh.itjust.works
            link
            fedilink
            arrow-up
            3
            ·
            11 months ago

            it just won’t go to the original one.

            And for clarity it won’t go to any other instances’ copies either.

  • brenno@lemmy.brennoflavio.com.br
    link
    fedilink
    arrow-up
    8
    ·
    11 months ago

    It uses activity pub, a protocol that allows servers to share content. So when you post on an instance, it became available for other instances to consume your content.

    About slowness, it can be that your instance it being rate limited, or it is not powerful enough to process all its users. You can try another instance.

    Activity pub documentation: https://www.w3.org/TR/activitypub/

  • KazuyaDarklight@lemmy.world
    link
    fedilink
    English
    arrow-up
    6
    ·
    11 months ago

    If you’re replying to a community on your home server, all actions should be similar levels of responsiveness, I think replying to another servers community may involve “some” active communication with the instance? Simple way to test this, if you are replying a lot on to another servers community, since you are browsing anyway, would be to just open the server/community directly and click around, if it’s feels a bit slow, then that server is overloaded by a bit and that’s probably the source of your issue. Otherwise we need someone with deeper knowledge in this thread.

    • NaN@lemmy.sdf.org
      link
      fedilink
      English
      arrow-up
      6
      ·
      11 months ago

      Everything you do on your own instance is against a cached version of the original post that is saved on your instance. Your instance sends updates in the background, the other instance can be entirely down and you can still browse, comment, and vote as normal on your own. The updates will just stay local though.

      • Valmond@lemmy.mindoki.com
        link
        fedilink
        arrow-up
        4
        arrow-down
        1
        ·
        11 months ago

        There seems to be a federation bug on version 0.19.x too.

        My posts gets like 1-2 upvotes since I upgraded versus 10-20 before. I just hope the posts get out there…

        • Ategon@programming.dev
          link
          fedilink
          arrow-up
          2
          ·
          11 months ago

          its fixable temporarily by restarting the server

          I just have a cron job set up to do that every day