LemmyNet
Resolve proxied objects
Requirements
- [X] Is this a feature request? For questions or discussions use https://lemmy.ml/c/lemmy_support
- [X] Did you check to see if this issue already exists?
- [X] Is this only a feature request? Do not put multiple feature requests in one issue.
- [X] Is this a UI / front end issue? Use the lemmy-ui repo.
Is your proposal related to a problem?
Currently, when calling /resolve_object, we're able to resolve directly-corresponding URLs, such as https://lemmy.world/post/117881.
However, when giving it https://lemmy.ml/post/1248487, which is lemmy.ml's view of the above post, it chokes.
This is entirely understandable, however, this is confusing to users when it does not correctly "search", and more importantly, for non-browser native apps, there is no (easy) way of resolving these proxied post URLs.
Describe the solution you'd like.
Make /resolve_object be able to resolve "proxied" posts like this, via some mechanism, with which it can fetch the original post ID and instance from this proxied post.
Describe alternatives you've considered.
Scrape the HTML and reconstruct the original URL, throwing that at /resolve_object as well.
This falls apart as soon as there is a change in lemmy-ui, or if there's a different frontend.
Additional context
With Mlem, we're currently considering using /resolve_object to "guide" users to posts natively, instead of having to present a safari/browser context for the same post, which is confusing and frustrating to the user.
Are you sure that's how the API works? For me, both the local post link and the original post link just lead to a generic site info return, but the API will resolve community links. I think that the /post is the path for the API that returns post information.
Edit: Actually my API may just be erroring. I need to look more into it.
Edit 2: Yeah, it was just my local API acting up.
I'm currently working on a solution to this. Someone else might beat me to it, but I'll try to see if I can get something going.
