• DarkThoughts@fedia.io
    link
    fedilink
    arrow-up
    1
    ·
    3 hours ago

    What do you mean by making it a proper hyperlink? I just posted the URL without any special formatting to make the URL itself visible, since they get automatically converted into hyperlinks. At least from my end on mbin. I’ve learned that Lemmy does not properly format line breaks / paragraphs so maybe that doesn’t even work either. But if I’d have to format them as hyperlinks I’d effectively double the @ signs in those URLs too, since I’d add them once as text and once as a link.

    Though, I only had one user name with the @ signs in the title, but afaik titles do not ping users. The rest were the @ signs to the various community / instance links.

    I can repost it as it was originally since I saved it before removing it myself. Although I also did a quick ninja edit in the title to include “(Album)” at the end, to make it clear that it is more than one image. Not sure if that triggered something too.

      • DarkThoughts@fedia.io
        link
        fedilink
        arrow-up
        1
        ·
        2 hours ago

        Done, although I’m not a fan of obfuscating hyperlinks. Same issue though. Immediately eaten and part of the modlog.

        Here’s the link: https://fedia.io/m/yepowertrippinbastards@lemmy.dbzer0.com/t/1347598/at-BonesOfTheMoon-at-lemmy-world-in-at-insanepeoplefacebook-at-lemmy-world-quietly-removes-thread-that-didn-t-fit-into As you can see, it does not even show up as “removed”, unlike the linked original thread. So from my end I did not even realize that it got removed.

        Edit: Well, slight error as I linked the original album as the thread instead inside the body. I just got up a couple hours ago… I won’t remove it for now for you to look into what’s happening though.

        • db0@lemmy.dbzer0.com
          link
          fedilink
          English
          arrow-up
          1
          ·
          2 hours ago

          I manually approved it now. I have to see how to prevent this on our threativore rules without allowing that same spam attack through