You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The fediverse does not guarantee consistency of any kind. It's possible to be missing replies in a thread or to not have the full history of a user's post when you look at their profile because the content was simply never federated to your server for various reasons.
It's common for users to check the thread in their browser or open a user's profile on their instance so you can see their entire post history. You have to do this outside of Fedi which is difficult when you can't even get a link to a post, for example.
The text was updated successfully, but these errors were encountered:
/api/v1/accounts/:id/statuses and /api/v1/statuses/:id/context have OAuth: Public (for public statuses only) visibility, so I think it is possible to fetch statuses even without valid authorization header on this server. But I am not sure about Pleroma support for this. I can explore more this issue, but it looks like low priority. @feld what do you think?
partially implemented in 2.0.17. It is possible to open thread and account at the origin instance browser. However, it is possible to load data from origin instance via API, so it should be implemented as Fedi feature in the future
The fediverse does not guarantee consistency of any kind. It's possible to be missing replies in a thread or to not have the full history of a user's post when you look at their profile because the content was simply never federated to your server for various reasons.
It's common for users to check the thread in their browser or open a user's profile on their instance so you can see their entire post history. You have to do this outside of Fedi which is difficult when you can't even get a link to a post, for example.
The text was updated successfully, but these errors were encountered: