I mean, I get annoyed when I see the same thing posted to two communities back to back, but 5 is ridiculous and extremely poor fediquite.

Edit: Seems the poster is some kind of spam bot. As one commenter pointed out, they seem to have spammed this to any community with “music” in the name. And it’s more than shows up in the screenshot. A LOT more.

        • Andrew@piefed.social
          2·
          8 months ago

          Something’s not quite working btw. It’s tricky to chat about because various front-ends auto-convert absolute links to instance-specific ones, so I’ll surround them in code blocks and hopefully they’ll leave 'em alone. Anyway: the fedi-link for this post is https://dubvee.org/post/1007192 which is where it is, but if you try to visit that with a browser you’re re-directed to https://tesseract.dubvee.org/post/lemmy.world/1007192 which isn’t correct - it should either not re-direct you or re-direct you to the correct URL at https://tesseract.dubvee.org/post/lemmy.world/14138451

          • Admiral Patrick@dubvee.orgOPEnglish
            1·
            8 months ago

            I don’t want to take over the comments with this, lol. I’ve got a community you can post that in if we want to discuss it further. Community: https://dubvee.org/c/tesseract

            I think it’s a glitch with the guest instance being set and unable to determine the post ID on the remote instance. When I clicked the first link (https://dubvee.org/post/1007192) in incognito mode, it took me to the expected post (https://tesseract.dubvee.org/post/dubvee.org/1007192) . When I switched guest instance to Lemmy World, and retried the same original link, it did redirect to the wrong link (using the post ID from my instance on LW which doesn’t exist).

            Yeah, I should not have it redirect when you’re browsing as guest since it requires an authenticated call to resolveObject to determine the correct post ID on the remote instance. Should work fine if you’re logged in, though. I’ll address that in 1.3.0.

            Thanks for pointing that out!

            Edit/update: I believe I have this fixed in the 1.3.0 latest dev branch.