Hello.
I'm extremely tired, so it very well could be that this is extremely simple and I'm just not getting it. However, what I would like to know is how to open a post from a community on one instance on another instance.
For example, here's a recent post from [email protected]. I know that to open that community in the instance lemmy.blahaj.zone, I would merely type into the address bar
lemmy.blahaj.zone/c/[email protected]
However, how would I open that particular post in that community on the latter instance? Is it even possible?
Cheers.
P.S.
I did do some searching on both this community as well as the Reddit Lemmy FAQ page but I didn't find anything. However, I could've missed something. If it's something obvious, I apologize in advance.
Edit: Assuming I understand what people are saying, well, evidently, it seems to be a current limitation of the ActivityPub protocol. Perhaps that will change one day. Hopefully soon. ¯\_(ツ)_/¯
The short answer is that you have to ask blahaj.zone to resolve it. lemmy.ml has it as post id 11470168, but it'll be different for other instances - whatever the next number was in their database when the post was announced.
You get different answers depending on whether you're logged in or not though.
From endlesstalk.org, I can search for that post in the web-ui: Communities -> paste the post url into Search -> Change the Type from 'communities' to 'posts'
Alternatively, using the API, I can resolve it with
curl --header 'accept: application/json' --header 'authorization: Bearer MY_LOGIN_TOKEN' https://endlesstalk.org/api/v3/resolve_object?q=https://lemmy.ml/post/11470168I'm not logged into blahaj.zone though, so it won't resolve it. The web-ui only gives me this post as one that mentions the thing I'm searching for, and the API returns 'not found'
I understand. I wasn't sure if it was something that was already possible and I just didn't get it (again, because I'm tired as balls), or if it was a problem with my instance, or hell even a limitation of the ActivityPub protocol itself. If I knew it was the instance, I would have posted for sure there instead. Although judging from others' comments here, it seems the issue really is an ActivityPub limitation.