Open ryan-ricard opened 2 years ago
I'm having basically the same issue except I also have the problem from a mastodon instance. If I manually copy the links to the content from my small pixelfed instance and search on mastodon, it shows up and I can interact. But that doesn't make all the other posts show up.
Identical issue you (are/were) having @ryan-ricard. Did you manage to find the cause/fix? or is this still occurring? Interestingly, I do see the post I published on my small (single user) instance on another pixelfed server (where I have an account that I follow from). Just not on pixelfed.social (where I also have an account and follow from).
Strange.
Cheers
My posts from a new instance are not showing up for followers on pixelfed.social, but they seem to be available after being manually visited by the URL from a user on .social . I'm not sure whether that means the posts are "federating" or not, but it's definitely not what I expect. There are a couple other open issues/bugs around federation but none that seem to cover this exact scenario.
Account/Instance Setup
I have two accounts set up, one on pixelfed.social ("The .social account") and the other on a new instance ("the small instance account") that I've recently installed through YunoHost. Both accounts follow each other, and the small instance account is followed by a few other accounts on .social as well.
Steps to reproduce
Expected: Viewing my home feed on the .social account, I see the recent post from the small instance account.
Actual: I do not see the post on the .social account's home timeline.
Additional info
In prior tests, once I view the post directly by copy/pasting the URL into the pixelfed.social interface and interact with it (I think actually looking at it might be enough), I see it in the .social account's home feed. I'll usually also get some other interactions on the post at that point, presumably from users who saw it on the global feed or via a hashtag. I have not interacted with the above post in any way, in case that helps anyone diagnose the issue
For what it's worth, the posts from the small instance account also show up as expected from a Mastodon instance.