I have sort of given up in fixing the problem, and will instead work on auto-detecting and auto-recovering when the problem happens.

    • jerry@fedia.ioOPM
      2·
      28 days ago

      thanks. I think the name of the instance is the most important part - I can test of federation with them to see what went wrong.

      • DarkThoughts@fedia.io
        1·
        28 days ago

        I can repost it. I just didn’t want to end up with it federating when it was a day or two old already.

      • DarkThoughts@fedia.io
        1·
        27 days ago

        Okay, I had to actually go to the instance as the modlog here did not show anything, but apparently my post was removed… But only on their side? It did not show “removed by moderator” on my end:

        reason: Threativore automatic post removal: image spam

        Not sure how that works or why. I used an external imgur album link, an additional imgur image link in the body, along with some various thread & modlog links.

        At least I now also see the pure extend of the mod abuse and terrorist simping on Lemmy as I filtered through my account.

        • jerry@fedia.ioOPM
          1·
          27 days ago

          The modlog function in lemmy/mbin can be a bit confusing. I don’t think the moderation actions of one instance propagate to the modlog of another instance. I think that is only really problematic in cases where the moderation action was taken on the home instance of a magazine/community.

          • DarkThoughts@fedia.io
            1·
            27 days ago

            I’ve seen issues with that too, where it does not show a lot of moderator actions on mbin but on the actual community modlog of the Lemmy instance. In this case it seems to be some sort of instance wide automod / spam protection though, but I don’t know what exactly triggered it.