@violet @nightpool not sure if its correlated with the update, but this usually means that at the time cybre.space received the post, it couldnt cache the media, either due to a problem with our media backend or the remote server’s copy of it being unavailable. not much we can do about this unless it turns out it was an issue with mastodon not fetching stuff correctly or something, i’m afraid
@violet @haskal @nightpool i think the problem's down to this commit: https://github.com/tootsuite/mastodon/commit/1045549f85041b13002801808b30a332c3a68c61#diff-9a8cecdf35c00c53c513bfa0592c8631e8369038cccdc16794aee6107d2418abR2551 (which is new in mastodon 3.3). i added some logging to cybrespace to confirm we're hitting the case on line 255
if our storage backend errors out while we're caching a remote image, it'll hit this Seahorse::Client::NetworkingError, which will cause it to just give up on fetching the image.
before 3.3, it would have thrown all the way up to where the request came in, which would probably have resulted in the remote server seeing a 500 error from us and failing to deliver the post. it then would have gone into retry logic and probably come in successfully a few minutes later.
@violet @haskal @nightpool
long story short is in 3.3 we're now seeing posts with missing images because mastodon is handling errors from the media store, whereas before it would have forced the remote server to retry.
the real solution would be to reduce our error rate from our media store, but a temporary solution is to immediately retry media store if they fail. i'll try that and see if that helps.