I've seen it aaaages go on youtube thumbnails once or twice, I wonder if it's a weird edge-case that bsky happens to trigger. Whatever it is, seems like some kinda non-deterministic memory corruption bug within the jpeg decoder which is kinda spooky.
so here's a fun observation. I have a screenshot of one of the corruptions I saw. I downloaded the image and re-created the same corruptions - the first corruption at least is consistent with a ~1400 byte chunk being missing from the file!
however, if there was a dropped packet, TCP along with TLS1.3 etc. really ought to prevent that from causing any application-level issues, so clearly there's a bug *somewhere*
reminds a bit of bugs I recall that were ultimately due to some malfunctioning network hardware on path between hosts – consistently losing bits in particular (often but not always reproducible) patterns with just certain remote-hosts/streams. …
The TCP maximum segment size option is supposed to be advertising the the largest TCP payload it can accept *assuming no TCP options*. The sending host is responsible for subtracting the space its TCP options take from that.