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 !technology@beehaw.org part with an ID? something like 6769052!technology@beehaw.org 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.zoneOP
    link
    fedilink
    English
    arrow-up
    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.