bookwyrm
bookwyrm copied to clipboard
Updates to remote accounts aren't reflected
Describe the bug Updates to remote accounts aren't reflected. For example, V recently changed their display name and avatar. However, these changes aren't visible in their subsequent replies or local profile.
To Reproduce Steps to reproduce the behavior:
- Interact with a mastodon user from bookwyrm
- Update the mastodon user's display name
- Interact with the bookwyrm user again from mastodon
Expected behavior Updates to displayed information from the mastodon account are propagated to the bookwyrm instance
Actual behavior Updates to displayed information from the mastodon account are not propagated to the bookwyrm instance
Instance reading.taks.garden
I can't swear this isn't a duplicate of https://github.com/bookwyrm-social/bookwyrm/issues/1553
It's a separate issue from 1553.
What should happen is that when a user updates their profile, an Update
activity is sent to the remote instances, and then the remote instances update their record of that user. There are a number of reasons this might not happen:
- The home instance doesn't successfully send out the update
- The home instance sends out the update but not to the remote instance in question
- The remote instance is temporary unavailable and doesn't receive the update
- The remote instance rejects the update because of an authentication issue
- The remote instance recieves the update but has an error updating the user record
I think the 4th reason is the most likely, since we've been seeing other federation issues around authentication, and I haven't seen any errors relating to updating remote users in Sentry. If you can check flower (it runs on port 8888), you should be able to find the task that updates the user, if it was recieved and authenticated. If there was an error, it would be found there too. I think these are also in the celery_worker logs.
It looks like I've updated my instance since then, so there's nothing left in the logs. :neutral_face:
It seems to have updated sometime in the last two weeks (maybe they updated their profile again and the update on my side succeded this time?) - should I close this?
Going to go ahead and close this, glad it got resolved :)