I have recently started getting broken images in Mail.app. Often, when someone sent me relatively big pictures (over 1 MB in size), the image ended up being corrupted, with a smaller file size that one would expect. This results in a picture that’s visible up to a certain point, and then rest is usually filled with solid grey by the viewer. While this could happen because the attached image is indeed broken — that is, if the sender is attaching an image that’s already corrupted on his/her machine —, it’s unlikely that the file gets mangled during the transit. To begin with, the base64 encoding adds lots of CRC (1/3 of the file size, and this alone explains why it’s a very bad idea to send big files through e-mail). In addition to that, no MTA will accept a malformed message: MIME parts must be completed with an extra boundary…
Tag: broken
What happens when Twitter switches from basic authentication to OAuth? Clients that relied on the former will stop working, until an update comes to add support for the latter. This has been called the OAuthocalipse and aside from minor glitches with some programs, it happened without much of a problem, much like the infamous millennium bug (ah, those were the good times: free Kevin!) One of the lesser used functions of Twitter has been brutally smashed by the switch to the safer authentication method, however, and in a way it’s quite ridiculous. I’m talking about RSS feeds that are — or should I say were — generated from the timelines and so on. It was probably not very used, given the plethora of dedicated Twitter client, but as a very basic user who is mostly in read mode, I really appreciated it. Of course, to get a feed of your…