I notice often people might cross post something and say (for instance) cross posted from https://lemmy.ca/post/1916492 (random example which is the link that I just followed)

Is there any way to format a link like that so your home instance will just open it up so you’re still logged in and can interact with it?

The link I followed goes to the Canadian lemmy server but it’s actually looking at a post from beehaw.org, so it’s extra useless 😒

Eg, if we could use the [email protected] part with an ID? something like 6769052[email protected] and our home instance could parse it to a link, with some tools to make it easy to add?

EDIT: This isn’t a feature, but there is a github issue feature request at https://github.com/LemmyNet/lemmy/issues/2987 for exactly this

EDIT 2: appears to be a userscript solution, but i haven’t tried it. lives here though: https://git.kaki87.net/KaKi87/userscripts/src/branch/master/fediverseRedirector/README.md

  • dbilitated@aussie.zoneOPEnglish
    1·
    1 year ago

    ok sounds like it’s not a feature - the link format i suggested includes both the instance ID and the instance url, so it would be possible for your home server to use that to preprocess to a useable link. I wonder if there’s a suggestions box 🙂

    • marsara9@lemmy.worldEnglish
      8·
      1 year ago

      I just got a PR merged today that might help with this. I’ll start experimenting with it more over the next week or so.

      Basic theory is that I can detect at least lemmy posts in the comment bodies and then rewrite those to your local instance. Primarily question is going to be performance, as remote network calls will be necessary.

      • dbilitated@aussie.zoneOPEnglish
        1·
        1 year ago

        oh that’s awesome! yeah i can see it being an issue especially if that post isn’t already federated. would be a great quality of life improvement though.

        • marsara9@lemmy.worldEnglish
          2·
          1 year ago

          Ya if it’s not federated already, I’m thinking the link will just remain as-is? Then comes the question of what happens after federation is complete? Ideally I’m thinking to do these rewrites as the comment containing the link gets federated so it only happens once, but that prevents updates… If I do it during someone looking at the post, then that becomes a lot of network traffic…

          Still a lot to plan out initially and then propose to the devs for feedback… So it’ll be awhile still.

          • dbilitated@aussie.zoneOPEnglish
            1·
            1 year ago

            Ya if it’s not federated already, I’m thinking the link will just remain as-is?

            yeah that seems entirely reasonable. it’ll still be a big improvement in most cases. also even if it only happens as it federates initially it’ll probably still catch many cases. is it possible to do a follow-up check only for links that weren’t updated the first time? if you could store a cool-off and maximum number of tries that would probably keep it light and as functional as possible.

            when serving posts with un-processed links that haven’t been updated, and it hasn’t been checked in the last 3 hours, re-check for a federated article and update. do this for up to 24 hours after the comment is posted, after that just give up? that gives it a few opportunities but doesn’t continue to waste resources if it’s unlikely the link will be resolved.

            I’m not sure if it’s easy to add columns to track those attempts though.

            • ChaoticNeutralCzech@feddit.deEnglish
              2·
              1 year ago

              Yeah, I was disappointed that federation didn’t automatically log you in everywhere like Google across its services, or that you cannot just “log in with [your home instance]” like OAuth.
              (See my other comment for pondering how this could work)

              I even tried using my feddit.de credentials (with @feddit.de appended, of course) on another instance, assuming the website code would notice the @ and pass them on to feddit.de instead. @[email protected]