So I can’t just change the kbin.social link to kbin.cafe and append an @kbin.social to the magazine name. I have to search for the post on kbin.cafe, which often won’t succeed if the magazine the post is on didn’t start federating over until after the post was made. I care about this because I would like to be able to interact with posts with my current account.
I can always just have a sock puppet account on kbin.social that I follow with my kbin.cafe account, and use the sock puppet to boost the post so I can access it on kbin.cafe. For me this is actually realistic option given that I made a kbin.social before I found out about kbin.cafe. But it feels dirty, and I would like to not have to constantly switch accounts to access one post or interact with it.
You are viewing a post that is originating on kbin social. It is then federating to your instance in kbin.cafe. So your instance is receiving a copy in a way to view and interact with the post. Your instance then can send a copy of the replies and comments to the originating instance so they can all work together.
That’s not my question, I understand how federation works. I want to know how to find a post on kbin.social and change the link so I can open it on kbin.cafe and interact with it on my kbin.cafe account. This often happens if I see an interesting post on a magazine that nobody on my instance is subscribed to yet.
You and others on kbin.cafe will have to subscribe to the same magazine on other instances. You would interact with it just like you are now with this post on kbin.social. There is a possibility the same post could appear in the general / all feed of federated posts too.
It would be lovely if posts had a unique ID (UUID of some sort) that was shared between instances. That way, rather than using the thread ID, a unique ID is used that points at that particular thread, comment, or microblog. But alas, this doesn't exist, and we're here.