- Last Active
adamc said:Has the word 'finger' becomes offensive?
Still trying to figure out.
I hope they can sort it out. Putting the on the back of the phone would be a non-starter for me. The way I use my phone, how I mount it in my car while driving and using it as my music source, the type of case protection I prefer, etc, mean putting the sensor on the back is just not going to work for me. Id that's what they decide to do, I'll just be keeping my iPhone 7 for the time being.
wiggin said:AppleInsider said:
While the exact purpose of the IC remains unknown, iFixit surmises that it's likely a digital-to-analog converter accompanied by an an amplifier and an analog-to-digital converter. Those are necessary to convert digital audio from the Lightning jack to analog sound that can be heard by human ears --?and also to convert input sources, such as sound through the EarPods microphone, into digital audio that the iPhone can use.
If this is true, bad form on Apple's part to not be more clear about the limitation.
On my work Windows machine I finally had to give in and move from Firefox to Chrome as a bunch of internal company tools have a lot of interface anomalies in anything but Chrome (despite our internal devs insisting there's no issue the tools are totally browser agnostic), so I'm stuck with it. Don't love it, but no significant problems for what I do. On my personal Mac stuff, it's Safari all the way, with the main important feature for me being easy icloud sync of bookmarks and currently open windows between all my Macs and iOS devices.
I think it's pretty short-sighted to say things like "oh they get what they deserve if they're illegally downloading torrents" or "I used reputable software, I don't have to worry about this". This could have easily happened with some other piece of mainstream software. Pretty much any software where someone could recompile it with the added malware and also somehow get upload access to the primarily used download server for the software could be compromised like this.
All it took was 3 things:
1. Access to the source code to be altered and recompiled
2. Access to the distribution server to upload the infected version
3. A valid dev cert to use in the recompile, whether the actual dev's cert, or some other one
Beyond that, I'm not knowledgeable enough about this stuff to say how Apple can change things in the future to avoid this sort of thing from happening.