My apologies. This may just be a combination of an error on my part and Lemmy not working as I had thought it worked.

There are two retrogaming communities, one on lemmy.world and one on kbin.social. I had thought that I was subscribed to both, but I was only subscribed to the one on kbin.social. lemmy uses subscriptions to determine whether to cause posts to propagate.

What I still don’t understand is why being logged is a factor. I definitely could see the posts when not logged in, so they made it to lemmy.today.

I just subscribed with my lemmy.today account, made a post with another account (on kbin.social), then unsubscribed and made another post with that second account. Both posts were visible to my account.

So I still don’t understand why being logged in is a factor for the earlier posts, but at the time that I was seeing the problem, I wasn’t subscribed, and lemmy doesn’t guarantee that propagation happens in that scenario, so I’m not going to complain about that.

thinks

Maybe when you browse a remote community not logged in – since it’s not possible for a guest user to subscribe – lemmy fetches the posts directly when the community is viewed, rather then having them pushed to it. Otherwise, it wouldn’t be possible to do much as a guest user with remote communities. And if nobody on lemmy.today was subscribed, that would explain the lack of popagation. That’d produce that behavior, where a guest user can see posts, but a logged-in user can’t unless they’re subscribed.

I don’t know why different logged-in accounts would see different sets of posts, but.

Well, I’m sorry for bothering you. Probably just user error, and me being too ready to flag something as a bug after seeing earlier federation breakage. Thanks for your time.