indieshack

About

Username
indieshack
Joined
Visits
119
Last Active
Roles
member
Points
634
Badges
1
Posts
340
  • Keep your iPhone X safe with one of these protective cases

    As I commented earlier, the Apple leather case is nice but affords zero drop protection based on the one I just received.
    williamlondon
  • Trump using new iPhone to tweet despite prior calls for Apple boycott

    As a liberal Dem I'm no trump booster, but in fairness I don't think the two issue are incompatible. Personally I believe (and I understand this isn't the consensus on this board) that Apple should be helping law enforcement especially with terror-related crimes, but I still use an iPhone.
    SpamSandwich
  • Lengthy iOS 10.3 install time likely due to conversion to new Apple File System

    I see comments are pretty polarized here about this - I'm with the view that Apple is on the losing side with this, they're delaying the inevitable.
    sog35 said:
    took me 10 seconds. 
    My iPhone 3GS upgraded in 13msecs   :D

    I am not sure why the 1st idiot to answer this thread had to talk out of his/her arse. My iPhone 6 took a little over 90 mins.
    is your 6 running about the same speed now, slower, faster?
    williamlondon
  • Apple extends developer deadline to support App Transport Security into 2017

    I think the general goal of ATS is laudable, but the way Apple introduced this, particularly timelines, was bone-headed. Existing apps with the ATS exception in their plists wouldn't have been yanked, but updates to them would not have gotten approved. Many apps using publicly accessible data servers (e.g. train times, etc) would have been effectively orphaned since in many cases the public data servers don't comply with the TLS 1.2 etc. requirements (there's no reason for them to, why use SSL for train times?). I understand Apple was suggesting requesting exceptions on an individual basis, not sure how that would be practical. Unless the app developer proxies them through their own servers, which many they won't because it's not cost effective, they'll abandon the app. I'm lucky enough to mostly be working in enterprise environments where in many cases the data being shifted is neither critical nor confidential and I can tell you that ATS exception use is the norm. Apple needs to re-think the rollout of this, perhaps limiting ATS where logins are used.

    Regarding Soli's suggestion to denote which apps enforce ATS, I think that's a great idea, shaming apps which don't enforce ATS - would you use a shopping or banking app which was highlighted by Apple as having less-than-perfect security? - rather than imposing a timeline.
    Soli