Comment on Posting the same thing to like 5 different communities at a time

possiblylinux127@lemmy.zip ⁨1⁩ ⁨year⁩ ago

• andrew_s@piefed.social ⁨1⁩ ⁨year⁩ ago

  Tesseract. You can use it for your own instance by logging in to it at https://tesseract.dubvee.org/ (which is a bit counterintuitive, because there's also a local Lemmy server there, but it works). Or self-host it of course (see https://github.com/asimons04/tesseract)

  source

  • ptz@dubvee.org ⁨1⁩ ⁨year⁩ ago

    Yep. Though that’s my dev version in the screenshot.

    source

    • andrew_s@piefed.social ⁨1⁩ ⁨year⁩ 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

      source

      • ptz@dubvee.org ⁨1⁩ ⁨year⁩ 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: 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 too 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. I’ll address that in 1.3.0.

        Thanks for pointing that out!

        source