For example, this comment links to another community on another instance, but when clicked on, you’re not actually able to interact with anything on that community, because you’re suddenly not logged in.

It’s doesn’t function like linking to a subreddit, and I understand that that’s because of federation, but is there a better way of doing this? It seems… very stupid that linking to a page would suddenly “log you out” for all intents and purposes, while searching that same community wouldn’t.

Does this make sense?

  • bdonvr@thelemmy.club
    9·
    1 year ago

    I don’t think so. I’m on 0.18 and links to posts and comments still go to the linked instance.

    However COMMUNITY linking is working great! Clicking on a link to a community on a different instance keeps you on your own instance :)

      • TWeaK@lemm.ee
        5·
        1 year ago

        You made your link to a fixed instance. Your source: [!lemmy@lemmy.ml](https://lemmy.ml/c/lemmy)

        This is a functional instance agnostic link for older versions: [!lemmy@lemmy.ml](/c/lemmy@lemmy.ml) - like this: !lemmy@lemmy.ml

        The new version should just let you type !lemmy@lemmy.ml and automagically make it instance agnostic. However the actual links need to either be /c/ or /u/.

        • maegul (he/they)@lemmy.ml
          2·
          1 year ago

          What is in my post is what the UI’s autocomplete provided. If it’s problematic or wrong, you should probably report a bug to the UI repo (I don’t know the details about these links).

          • TWeaK@lemm.ee
            2·
            1 year ago

            I just checked on sh.itjust.works, the only other instance I’m on that is on 0.18 yet, and your link works there. Edit: However the source of your link, made on 0.18, is different to my link on 0.17.4.

            Yours: Sounds like a big or missing feature. You might want to write it up on GitHub if you can or the [!lemmy@lemmy.ml](https://lemmy.ml/c/lemmy) community.

            Mine: The new version should just let you type !lemmy@lemmy.ml and automagically make it instance agnostic.

            It looks like 0.18 creates an actual link in your comment when you make it, as a fall back for older versions, however that link is not agnostic. However if you view an old comment in 0.18 it will make an agnostic link for you, in spite of the old source. 0.18 apparently ignores the source in the comment where the link is not agnostic and just makes its own agnostic link out of the displayed text.

            So maybe it would be better if 0.18 made a link like [!lemmy@lemmy.ml](/c/lemmy@lemmy.ml) to ensure full compatibility.

            • maegul (he/they)@lemmy.ml
              2·
              1 year ago

              Coupled with the new rendering of links, into what I believe are instance agnostic formats for 0.18, the system seems it will to work well.

              • TWeaK@lemm.ee
                2·
                1 year ago

                I dug deeper and made a few edits lol it’s not quite perfect. More than anything I don’t get why it creates a non-agnostic link in the source.

                • TWeaK@sh.itjust.works
                  1·
                  1 year ago

                  Test: !lemmy@lemmy.ml

                  Edit: !lemmy@lemmy.ml

                  Yep, that happens when you select it from the dropdown box. So it’s the dropdown box that is making non-agnostic links to the host, however 0.18 ignores this and makes an agnostic link based on the text.

                  • TWeaK@lemm.ee
                    1·
                    1 year ago

                    Oh strange, that was made on sh.itjust.works in 0.18 but didn’t create a link in the source.

                    Are you sure you didn’t manually create yours? Or did you maybe select it from the dropdown box?

          • TWeaK@lemm.ee
            2·
            1 year ago

            I think maybe because my instance is still on 0.17.4 the !comm@instance type of link doesn’t work. /c/ and /u/ did work on the old versions though, you just had to make them manually.

            So there’d be no point reporting the bug. Not unless we check on another 0.18 instance to see if your lemmy.ml link is agnostic there.