I copied my previous comment permalink and posted it to another comment. (see example on my profile)
Instead of opening the link inside the app it opened it on browser. I understand there are many instances available and it may not be easy to code everything into the app. But i don’t know how but Please look into this.
That has to do with how Android handles links.
So on a system level it knows that HTTP and HTTPS link should be open with a browser. Now as an app builder you can say to android “let me open X”, but the thing is, due to sheer amount of servers, you can never define all Lemmy URLs. A subset of the URLs sure, but not all.
Not until Android gets some things in place to make it happen.
The same issue applies exist with Mastodon and it’s servers.
There is an effort to get the cross-instance link format fixed so that they first have the home instance handle it, but it would also contain the remote post ID in order to fetch it if not yet done. IIRC, so Jerboa might also be able to do a direct request if there is some indication of it being a network-internal link?
Automatically stay on an instance, when given a link to another #1048edit: somewhat noob mock-up
(https//)sopuli.xyz/post/12345?net=lemmy&[email protected]&opost=98764
I’m pondering putting this as a comment on the issue, that’s why i ask if this makes sense.That would also work… Especially since the app knows about a user plus the instance they are on.