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

you are viewing a single comment's thread
view the rest of the comments

[–] fubo 16 points 11 months ago* (last edited 11 months ago) (3 children)

No, not currently. Post IDs are per-instance.

For instance, this post is:

[–] [email protected] 15 points 11 months ago

Found the feature request issue, it's at https://github.com/LemmyNet/lemmy/issues/2987

[–] [email protected] 2 points 11 months ago (1 children)

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 8 points 11 months ago (1 children)

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.

[–] [email protected] 1 points 11 months ago (1 children)

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 2 points 11 months ago* (last edited 11 months ago) (1 children)

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.

[–] [email protected] 1 points 11 months ago (1 children)

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.

[–] [email protected] 2 points 11 months ago* (last edited 11 months ago) (2 children)

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]

[–] [email protected] 3 points 11 months ago (1 children)

I got very confused and tried clicking all kinds of stuff, ending up with a dozen accounts across the Fediverse. I am not the only one who did, apparently.

[–] [email protected] 3 points 11 months ago (1 children)

You two can stop now. It's not funny.

[–] [email protected] 2 points 11 months ago

YOU

[–] [email protected] 2 points 11 months ago

I think full federated auth across servers is a much more difficult problem - it'd be nice but outside the scope of this request!

[–] [email protected] 1 points 11 months ago (2 children)

What’s this post’s link for beehaw.org? I cannot see it at https://beehaw.org/c/[email protected] although some other posts are visible. I thought that I would see an “Error: defererated” message if that was the case.

[–] fubo 2 points 11 months ago

"Defederation" means that new posts aren't accepted from instance A to instance B; it doesn't (currently) generate an error if you try to access a community c@A on instance B.

[–] [email protected] 0 points 11 months ago (1 children)

Hi there! Looks like you linked to a Lemmy community using a URL instead of its name, which doesn't work well for people on different instances. Try fixing it like this: [email protected]

[–] [email protected] 1 points 11 months ago

No. That’s the point.