So basic usability question here. If I end up looking at a post on a different Lemmy server (say, over at beehaw) and want to comment/vote on it, how can I quickly open it up on my home Lemmy server?
Right now I copy paste the entire title, open my server, search the title, and then find the post. But that seems really cumbersome. Any better way?
Meaning that the domain in the browser URL bar will be a server other than one’s own home Lemmy server, in this case? If so, I haven’t been able to to get this to work; it merely says
which takes me to the login page of that server, even though I’m already logged into my own.
Edit: nevermind, I see @howdy@thesimplecorner.org 's (hmm, how do I tag a user?) post below, which I think was the issue.
Edit 2: sheesh, nope, it’s more complicated. I have an account on server A, the community lives on server B, but the post I’m seeing is actually hosted on server C; i’m basically seeing server C’s mirror of it. I would, somehow, have to find this post on B (or A, obviously) in order to interact with it, it looks like.
Your home lemmy instance syncs content from a remote community after the first user on your home instance subscribes to it (except for a very small subset of posts that your homeinstance pulls on subscription). So if the post you are referring too is before your homeInstances first subscription then your sort of out of luck interacting with it. There is also a chance your homeinstance federation screwed up sometime and didn’t sync something, I’ve seen that some (I host my own instance). You could go see the “missing” content that doesn’t exist on your homeInstance on any remote instance. However, you are not going to be able to interact with it unless it exists on your home instance.
Ah, that adds some useful details – thanks.
What’s the best way to determine whether this has occurred (for a given remote community)?
If you see anything of the community on your homeinstance someone has subscribed to it. You can also see subscriber count by searching the community name on your home instance !community@myinstance.ml
Hope that helps