• jrubal1462@kbin.social
    1·
    1 year ago

    I thought it worked if you just linked /c/asklemmy@lemmy.ml
    With the only caveat being that users on kbin will need /m/asklemmy.ml
    With the only caveat being that users on kbin will need /m/asklemmy@lemmy.ml

    I would normally test the crap out of these before posting since I really don’t know what I’m doing, but I’m on my phone and mostly busy at the moment. Sorry if it doesn’t work.

    • CoderKat@kbin.social
      1·
      1 year ago

      Kbin needs /m/asklemmy@lemmy.ml (domain is important) or a bit simpler is with an @ symbol in front: @asklemmy (note: the domain is here but kbin currently renders it without the domain – that needs to be changed as it has potential to confuse and mislead)

      Downside to the /m/asklemmy@lemmy.ml format is that it doesn’t currently auto linkify. Gotta do [/m/asklemmy@lemmy.ml](/m/asklemmy@lemmy.ml) (/m/asklemmy@lemmy.ml)

      Hopefully kbin soon fixes the !asklemmy@lemmy.ml syntax. It’s currently broken. Once fixed, that should work for everyone.

      • ChemicalRascal@kbin.social
        1·
        1 year ago

        An outstanding problem, though, is linking to specific posts and comments. And, after that, I would argue both kbin and Lemmy should support more nuanced parsing of cross-instance hyperlinks, to reduce friction and UX pain without requiring users to memorise new syntax just to make links work.

        • jrubal1462@kbin.social
          1·
          1 year ago

          I’m the problem. As feared I fudged it up as I was rushing to type it up on my phone. As @CoderKat mentioned, the problem with typing it out as /m instead of using @, is that you have to manually enter the visible text in [ ] and the hyperlink in ( ). I got the hyperlink correct and beefed it on the visible text.