I hope they can bring the site back up soon and that it is not gone forever.

  • Boz (he/him)@lemmy.one
    link
    fedilink
    arrow-up
    7
    ·
    1 year ago

    I think that’s a good sign. It probably means the problem is being dealt with by admins. Any communities on the affected instances that have subscribers on other instances will be backed up on those other instances, so most of the content is safe no matter what. I just hope the users on those instances know they can come to others in the meantime.

      • megane-kun@lemm.ee
        link
        fedilink
        English
        arrow-up
        2
        ·
        1 year ago

        it sounds like the issue is spreading through comments and involves the markdown parser.

        What do you mean? Is there something that us normal users can do to mitigate this? Or do we just hope that the devs and admins resolve this?

          • megane-kun@lemm.ee
            link
            fedilink
            English
            arrow-up
            3
            ·
            1 year ago

            Thanks for the explanation.

            I’ve already made the decision earlier to change my passwords (on all my accounts on different instances) after this has been resolved.

            • spiderplant@infosec.pub
              link
              fedilink
              English
              arrow-up
              4
              ·
              1 year ago

              FWIW, right now it seems unlikely that your password was accessible to anyone. Your login cookie may have been taken if you accessed Lemmy on a web browser (apps are likely fine), so you would want to clear your Lemmy cookies and cache once this is over.

              But I’m speculating, and changing your password is never a bad idea!

          • KSP Atlas@sopuli.xyz
            link
            fedilink
            English
            arrow-up
            3
            ·
            1 year ago

            Looks like it could be some kind of markdown parser injection, where they manage to forcefully close the HTML src property and enter their own