• Max-P@lemmy.max-p.meEnglish
    0·
    4 months ago

    There’s a bunch of browser extensions as well to add a “show on my instance” link whenever it detects a Lemmy instance page which basically does the same thing automatically for you, pretty useful.

    • mark@programming.devEnglish
      0·
      4 months ago

      Was about to ask if there was a way to do this automatically. Does anyone know why this isn’t baked into the Lemmy codebase? I’m thinking this would be pretty easy with browser cookies. 🤔

      • Max-P@lemmy.max-p.meEnglish
        0·
        4 months ago

        It would have to go through some sort of Lemmy link redirector service because a site can’t access another site’s cookies. And even then, with third-party cookie sandboxing, that still wouldn’t work.

        I don’t think this is solvable without a browser extension. The best the devs could do is let you enter your home instance URL on each instance such that eventually you’ve configured them all and it works. But the extensions are just plain better.

          • Max-P@lemmy.max-p.meEnglish
            0·
            4 months ago

            Because if you’re on say, lemmy.world because you clicked such a link, lemmy.world has no way of knowing what your home instance is. The cookies are all sandboxed for lemmy.world’s use. So even if you used a third-party site whose sole purpose is to know your home instance, it still wouldn’t work because now third-party cookies are sandboxes based on the domain of the site you’re visiting.

            That used to be possible with a third-party. That’s how the Facebook like buttons and Login with Google used to work, and those are also the reason it’s no longer possible. You used to be able to just embed some JS from a third-party on a site, and that JS can access cookies from the third-party site while also being directly callable from the site that embedded it. So in that case, we could agree on a third-party lemmy redirector service whose sole purpose is to store the user’s home instance in a cookie and then the script can be embedded everywhere and it would be able to spit out the URL from the cookie. But that hole’s been plugged. So even if you do that, it doesn’t work anymore because of stronger cookie sandboxes. But that’s why you’d need third-party cookies to pull it off.

            So the only fix left for this is, every lemmy instance you visit, you have to set your home instance on it, which would set a cookie that the site can actually see, then it could redirect you to your home instance to view the post. But that still kinda sucks, because you have to do it for every instance you run across.

            So, cookies are useless for this.

            • AwesomeLowlander@lemmy.dbzer0.comEnglish
              0·
              4 months ago

              You’re missing the point. You should never leave your home instance. Lemmy could automatically remap links to whatever your home instance is before you ever click on them.

              • Max-P@lemmy.max-p.meEnglish
                0·
                4 months ago

                Some UIs do, I have Tesseract on mine and it rewrites the links for me.

                That doesn’t solve sharing a link on Matrix/Discord/Google or wherever. I rarely have this issue on Lemmy itself, but whenever I get a link from elsewhere, that’s when I need to be able to open it on my home instance so I can interact with it.

                Same deal with Mastodon. You’re reading some news, it links so the dev’s Mastodon, you need a way to open it in your home instance.

                There’s no fixing that.

                EDIT: test self link to this comment https://lemmy.world/comment/10561034

                • Max-P@lemmy.max-p.meEnglish
                  1·
                  4 months ago

                  This is what that looks like on a good Lemmy frontend:

                  I forgot the default UI didn’t do that. Both Tesseract and Boost handle those mostly just fine.