Funny you've gone all quiet now that Apple's published their side of the story eh? AppleScruff1
Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Steve Jobs on iOS Location Issue: 'We Don't Track Anyone'
- Thread starter MacRumors
- Start date
- Sort by reaction score
Funny you've gone all quiet now that Apple's published their side of the story eh? AppleScruff1
Funny you've gone all quiet now that Apple's published their side of the story eh? AppleScruff1
I said yesterday that I'd wait for Apple's official reply.
Funny you've gone all quiet now that Apple's published their side of the story eh? AppleScruff1
Most people wanted :
- Apple to address the issue by updating iOS.
- Apple acknowledge the problem
Apple has now done both. I personally said that I would like for Apple to prune the database and not back it up. The promised update will do both.
What else is there to talk about ? All that's left is to wait for the update and tell Apple "thank you, good job".
Indeed. My post was directed at AppleScruff1, the individual who labelled people as 'Apple apologists' when they cited information given by an Apple engineer at WWDC which explained this very issue. Funnily enough, what the engineer said last year is exactly the same as the explanation given in the press release today...
Indeed. My post was directed at AppleScruff1, the individual who labelled people as 'Apple apologists' when they cited information given by an Apple engineer at WWDC which explained this very issue. Funnily enough, what the engineer said last year is exactly the same as the explanation given in the press release today...
Actually I called the people who defend Apple at any cost apologists, not just the ones citing an engineer from last year. It is funny that if the engineer said and new this last year that Steve said Apple needed a few days to look into it and then a few days to prepare a statement. So you and the engineer knew this but Steve didn't and had to check it out.
Indeed. My post was directed at AppleScruff1, the individual who labelled people as 'Apple apologists' when they cited information given by an Apple engineer at WWDC which explained this very issue. Funnily enough, what the engineer said last year is exactly the same as the explanation given in the press release today...
Uh ? I hate to admit but I agree with AppleScruff1. Anyone trying to point to engineers and patents "explaining" the issue weren't understanding the issue.
In every thread like this you'll have a group of people that are quick to deny any fault on Apple's part. They sort of are trying to "apologize" for mistakes Apple does. They tend to make the threads longer than they should be as much as the people who jump on anything to go off on long rants about Apple being "bad".
There's always a white to a black. There will always be apologists to haters. Extremists exists on both sides and neither is good. My ignore list here gets longer and longer.
Anyway, the issue wasn't about the database's existance itself. It was about the lack of pruning and the backing up of it. Apple agrees it seems. Now we can enjoy the location service and have none of the privacy concern if we lose our phones or it gets stolen.
Uh ? I hate to admit but I agree with AppleScruff1. Anyone trying to point to engineers and patents "explaining" the issue weren't understanding the issue.
In every thread like this you'll have a group of people that are quick to deny any fault on Apple's part. They sort of are trying to "apologize" for mistakes Apple does. They tend to make the threads longer than they should be as much as the people who jump on anything to go off on long rants about Apple being "bad".
There's always a white to a black. There will always be apologists to haters. Extremists exists on both sides and neither is good. My ignore list here gets longer and longer.
Anyway, the issue wasn't about the database's existance itself. It was about the lack of pruning and the backing up of it. Apple agrees it seems. Now we can enjoy the location service and have none of the privacy concern if we lose our phones or it gets stolen.
I agree with you-I suppose if there weren't folks checking these things out and calling companies to task they would never get corrected.
I'm glad there are "watchdogs" out there.But thats another problem in of itself. There have been too many of these "oops, sorry" from major companies incl google. The FTC should do privacy audits, or some other means of check up.
actually, its a major part for its 3rd party developers. The devs that make the iPhone/iPad what it is(pandora, facebook, etc) all gather this information for that sole purpose. although, not directly related to Apple, but it is the cause of its success with these devices
In the simplest of terms - on purpose or not, Apple provided a kill switch for recording/transmitting/using Location in apps and the OS.
The kill switch did not work.
Would there be any argument here if that same kill switch that didn't work was the Data Roaming switch that failed to turn "off"?
I imagine all the people who have data roaming turned off would care if they got hit with a bill. And I doubt anyone would start blaming the user on that.
Privacy issue aside (at least for this part of the argument) - Apple's "bug" is and was a liability for the company. And whether you agree with them HAVING or NEEDING to fix it or not - it's smart business because of potential future lawsuits for not doing so.
The kill switch did not work.
Would there be any argument here if that same kill switch that didn't work was the Data Roaming switch that failed to turn "off"?
I imagine all the people who have data roaming turned off would care if they got hit with a bill. And I doubt anyone would start blaming the user on that.
Privacy issue aside (at least for this part of the argument) - Apple's "bug" is and was a liability for the company. And whether you agree with them HAVING or NEEDING to fix it or not - it's smart business because of potential future lawsuits for not doing so.