On balance, if you use 2FA, you should have at least two SMS numbers numbers associated with your (insecure) Apple ID. Since SMS is an essential part of Apple’s 2FA, and SMS is a poor way to do 2FA, Apple’s 2FA is fundamentally insecure (mac bloggers seem universally unaware of this incidentally).ĭamned if you do and damned if you don’t. Apple’s recommended mitigation is to use multiple SMS verification numbers, not just the one mandatory number. Click Didn’t Get a Code on the sign in screen and choose to send a code to your trusted phone number…Īpple 2FA implementation has a high risk of account access loss (Google has better 2FA recovery options). … If you're signing in and don’t have a trusted device handy that can display verification codes, you can have a code sent to your trusted phone number via text message or an automated phone call instead. If your iPhone is your only trusted device and it is missing or damaged, you will be unable to receive verification codes required to access your account… Consider verifying an additional trusted phone number other than your own phone number. … To use two-factor authentication, you need at least one trusted phone number on file where you can receive verification codes. You can use this number if you temporarily can’t access your primary number or your own devices…. …You should also consider verifying an additional phone number you can access, such as a home phone, or a number used by a family member or close friend. (As near as I can tell Mojave has the same list and it still doesn’t include HEIF/HEVC, which seems a vote of some sort.) OpenEXR was from Industrial Light and Magic but it’s as dead as old JPEG-2000. Incidentally, the image formats Preview can export to in Sierra when you use the Option key trick ( apple doc) - prior to Mountain Lion they were all shown. Basically everything sucks, which is very 2018. In terms of a practical archival image format we basically have PNG and JPEG with no metadata standard and perhaps some flavor of TIFF. HEVC is likely to lose out in the long run to AV1 and disappear - with no comment from Apple when it converts. I suppose HEVC is an improvement over RAW, but only by a bit. In 2018 some SLRs shoot DNG (not Nikon or Canon of course), Apple’s cameras shoot patent-encumbered HEVC (not HEIF, that’s the container damnit), and there’s lots of proprietary RAW. I think cameras have gotten better at making the best use of JPEG, which itself has iterated over time. We never did, partly due to patents and partly for reasons I don’t understand. Twenty ago I was sure we’d get one of many better lossy image formats, of which JPEG2000 is the only one I can remember now. Since I already use Image Capture to bring images off my devices rather than Aperture the extra conversion step is a modest cost. I suspect DNG is only a minimal archival improvement on CR2 so I’ll mostly continue to shoot JPEG (because everything sucks ), but now I have the option to do CR2 when I want better results. Aperture opened it a bit more slowly than I remember it processing my older Canon RAW files, but there no real issues.Īdobe DNG Converter has a truly ugly Mac UI, but I have no problems with that. It was extremely fast and produced a DNG a few MBs smaller than the CR2 file. So I downloaded the app and tried it on a CR2 file from my SL2. Today, through Facebook’s Aperture User Group, I learned that Adobe DNG Converter output can be treated by Aperture in Sierra as a type of RAW format. I tried using Canon’s RAW to JPG converter but it was achingly slow and it defeats the purpose of shooting RAW in the first place. I don’t know if there would be any support if I upgraded to High Sierra or Mojave, but I think not. Aperture on Sierra doesn’t support RAW files from my Canon EOS SL2.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |