PieFed Meta

1997 readers

16 users here now

Discuss PieFed project direction, provide feedback, ask questions, suggest improvements, and engage in conversations related to the platform organization, policies, features, and community dynamics.

Wiki

founded 2 years ago

MODERATORS

rimu@piefed.social

124

New: Automaticlly turn remote fediverse links into local links (peertube.wtf)

submitted 6 days ago by rimu@piefed.social to c/piefed_meta@piefed.social

21 comments fedilink hide all child comments

One of the long-standing issues we have in/on the fediverse is that when I have a link in my post that goes to another post on my instance, people on other instances will click that link and be taken to MY instance, where they can't comment, don't have an account, aren't logged in, etc and they will try to log in using their login credentials for their home instance then wonder why it doesn't work.

When someone links to https://lemmy.world/post/39832275 and I'm on piefed.social I want to see https://piefed.social/c/news/p/1544770/national-parks-ordered-to-check-gift-shops-for-dei-type-items not the copy on lemmy.world!

As of PieFed v1.4, links like that will automatically be converted to link to the local copy of the post, where 'local' is whatever is local for the reader. See the linked video where I demonstrate this in action.

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

[–] sem@piefed.blahaj.zone 1 points 6 days ago (3 children)

I have the reverse problem that when I'm on PieFED using blorp and I want to share a post, it always shares the blorp version of the post. When I would ideally like to share the canonical URL and give credit to the original source. Voyager and lemmy has a way to specify this option for sharing, but as far as I can tell blorp does not.

[–] moseschrute@lemmy.world 3 points 4 days ago (1 children)

Sorry I should have fixed this a long time ago. Though I was considering having it open in Blorp and then showing “continue on Blorp” or “view original”. Something like that. Basically, let the receiver decide instead of the sharer. But maybe that’s not the right move. Anyway, I stalled on fixing it because I couldn’t decide the right solution. What I wanted to avoid was over complicating the share menu.

[–] sem@piefed.blahaj.zone 1 points 4 days ago* (last edited 4 days ago) (1 children)

I can appreciate that! Keeping share to minimum actions needed is very appreciated!

This is how it looks like in Voyager settings (for the sake of discussion). What did you think of having a preference in the settings?

[–] moseschrute@lemmy.world 2 points 4 days ago (1 children)

That could work! What should the default option be? I think it would either have to be “ask” or “chose one of these options which can be changed later from settings”

[–] sem@piefed.blahaj.zone 1 points 4 days ago

IMO the current behavior could be default -- the blorp link.

I usually end up changimg it to the community.

[–] wjs018@piefed.social 5 points 6 days ago (1 children)

@moseschrute@lemmy.world FYI

Something about this feature @rimu@piefed.social is showing off is that it is only doing the link substitution in the web frontend. Any links in posts/comments will remain unchanged in the API that clients like blorp and voyager. This lets the different clients deal with this as they would like.

It might be possible to do this substitution on PieFed's side for API responses, but I think it should not be the default. We would need some way for an API client to indicate that this is what would be desired.

[–] moseschrute@lemmy.world 1 points 4 days ago

Thanks for the heads up!

[–] rimu@piefed.social 3 points 6 days ago (1 children)

I think you can get the canonical url using 'view post source' in the 3 dot menu?

[–] sem@piefed.blahaj.zone 1 points 5 days ago

Mine doesn't have that.