I will be updating the instance to v18 at 20:00 22:00 UTC.

See https://programming.dev/post/181191 for the changes

edit: Lemmy.ml updated and seems to have gone down. We’re going to wait and see what the outage was caused by and then proceed from there.

edit 2: lemmy was down due to a ddos attack. We will upgrade at 22:00 UTC

edit 3: we had issues with the email setup getting overridden again. If you tried to sign up in the past 8 hours please try to just log in. If you can’t, please message me (discord, matrix, or mastodon)

  • snowe@programming.devOPMEnglish
    1·
    1 year ago

    Hm. I’m not sure I understand the problem. I don’t see anything like this in the current issues list. Maybe if you could describe it a bit more I might be able to log something?

    • nieceandtows@programming.devEnglish
      1·
      1 year ago

      The report issue seems to have resolved itself now, but the moderator issue is still present. I created a bunch of communities on lemmy.world, and I want to see if I can move over here as my main instance. I thought I’d make myself mod on those communities. I did that for 4 communities, but I only see two of them in my profile as being moderator. However, if I open my programming.dev profile on lemmy.world, it shows that I’m moderating 4 communities. Does that make sense?

      • ruffsl@programming.devEnglish
        3·
        1 year ago

        I didn’t know one could mod for communities on remote instances, that’s cool! I’ve also noticed some slow or loss of synchronization between instances, e.g where the vote count for a remote post when viewed locally never steady states with the vote count when viewed directly from the remote instance.

    • nieceandtows@programming.devEnglish
      0·
      1 year ago

      One other thing I noticed now, is that if I mark a message as read, it doesn’t disappear like it used to. It goes away if I refresh the page, but it used to disappear right away when I marked a comment as read.

      • ruffsl@programming.devEnglish
        2·
        1 year ago

        That’s because websockets were probably used to relay the state change to the browser. With websockets now removed to improve server performance, that state change may have to be conveyed using something else to replicate that UX.