I could add something like this. However, for most power users that are scrolling that far to encounter this issue, I recommend using the "hide read posts" feature. This will essentially keep your spot in the feed until reset. It also allows you to pull to refresh, keeping your place (essentially) while also being able to see new posts that percolate up your feed.
This also helps with other things - if you restart the app and/or device you won't lose your place until you reset hidden posts.
I might be able to add a long press the hide button to reset hidden posts for those that just want hiding posts to be super temporary. Would that help?
Try to login to any instance and submit with blank username/password.
Alternatively, (bit more complicated but provides a nice interface to browse) you can select an instance in the signup flow, and press the (...) icon in the header to "connect as guest"
On voyager it links to the updated content that is crossposted. Might be good to update for other clients though (although this is the Voyager community haha).
This also explains why the image works for some people and not others. Because at some point the original image link broke, and some instances had the image cached by then, but not others.
That's also why usually the image will work on the origin server (in this case, feddit.org). Because the image was originally posted there, and that server was the first one to cache it (before the origin image broke).
I've thought about some workarounds for this scenario. Voyager could theoretically request the post payload from the origin lemmy instance (AP URL) and then use that cached image URL. However, this reduces privacy somewhat because your lemmy app is now connecting to an arbitrary lemmy instance.
Maybe it will be a setting in the future.
As others said, other apps are also affected by this issue because it's not a Voyager specific issue.
Another side note, this could potentially be fixed in Lemmy backend. Lemmy devs could fetch the cached image from the upstream Lemmy server instead of using the original image URL, if it is broken.
hmm, I don't think Lemmy's API allows for filtering communities by instance. That would be a really cool feature though!
Edit I found this open issue: https://github.com/LemmyNet/lemmy-ui/issues/1298