Feature: integrate instance agnostic link sharing service

[graphit0]

What do you want to see?
Integrate https://github.com/RikudouSage/lemmyverse.link / https://lemmyverse.link/ i.e. instance agnostic link sharing service

Use Case
Instance agnostic links simplify sharing content outside of fediverse
Suppose you come across a link to lemmy post on non-native instance.
Like that https://lemmy.world/post/7284890

How do you open it?
Let's face it, searching in your home instance with post name is very inconvenient
Instance agnostic links address this problem
example of instance agnostic link https://lemmyverse.link/lemmy.world/post/7284890

After clicking this link you can set your home instance and the post will be opened there

Why

• improve discoverability of Lemmy Explorer since a lot of links going to be pointing to it
• allow users to rely on home instance they set on Lemmy Explorer while redirected by instance agnostic link

---

I have no affiliation to the service, I simply like to use it

[tgxn]

oh yeah i get you, basically a redirection service

like:
https://lemmyverse.net/link/lemmy.world/c/world -> https://your.home/c/[email protected]
easy, data is in URL

https://lemmyverse.net/link/lemmy.world/post/7284890
don't we need to know the post ID on your local instance for this to work?

[graphit0]

don't we need to know the post ID on your local instance for this to work?

Yes indeed, we need to API query the target/home instance to get post ID. You can see how author does it in linked github: file LemmyObjectResolver

I realize that it's much more difficult than simple link reformatting, that's why I proposed integrate his solution if it's possible.

[tgxn]

I think community redirection would be doable easily, but maybe the post redirection is a bit out-of-scope, since it would involve realtime scraping of the source and target instance.

[tgxn]

https://github.com/RikudouSage/lemmyverse.link

https://github.com/RikudouSage/lemmyverse.link/blob/master/src/Controller/LemmyLinkController.php

The only way to perform the post ID redirection would be to use a backend service.
Their architecture has a backend component hosted on AWS, and I don't have plans to run a backend for this service.