New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Federation questions #4369
Comments
It's same for all users not only Mastodon . It's WIP. Will be fixed in this weekend I hope. |
I am not seeing media-containing posts (not re-posts) from Mastodon users that I follow from my Pixelfed account. Is this related (i.e., a "federation issue") or expected behaviour? |
No ... Looks like an issue with your instance! |
Yeah, my problem must be something different and weird. I noticed that I only have that problem with some accounts, but not all. |
For testing, I created several accounts on different Pixelfed instances. I found an account with a large number of image posts on Mastodon and displayed this account sequentially on each Pixelfed instance on which I am logged in. The effect is that I see different content from each account. I've searched for information on how all this federation stuff should work, but got nothing but headaches. |
It depends on when the pixelfed server was federated with the for example Mastodon server. Pixelfed doesn't display older posts that were created before federating as far as I'm aware. |
Thanks for the info, but this only explains one out of five cases tested.
If it was about the date of federation then from date x all posts would be visible. This is not the case, they appear to be random.
I would very much like to understand this. What is the point of creating new instances if they cannot see past posts? |
I am also definitely not seeing all the posts that I expect to see in pixelfed. This certainly seems like a bug to me, and beside the performance issues (#4367), is one of the major pains for me at the moment.
I understand this problem and agree it is not what most people expect, but I think it is a separate issue from all the other ones, and I am not sure Pixelfed can do anything about it. AFAIK, ActivityPub is built as a push-infrastructure and not as a pull-infrastructure. This means, that unless you want all instances to always push all information to all other instances (lots of data, how do you know who to send to?); the subscribing to someone posts means getting everything from the point in time onwards. There are certain things I could think of to still make the UX better, e.g. when you click on a person's profile, instead of showing whatever is cached on your instance, directly redirect to the person's profile on their instance (so you see everything). Unfortunately, on that person's instance, you have no way of following/interacting, but maybe some kind of overlay could be added or the remote instance be embedded in a frame or so, to still allow this. |
I have just "moved" one of my Mastodon accounts to Pixelfed, and have some questions regarding interaction with Mastodon accounts:
The text was updated successfully, but these errors were encountered: