Live data from Hacker News

iOS 11 Location Privacy: "Only While Using" is now always an option for users

twitter.com

191–193 of 193 posts

Re: iOS 11 Location Privacy: "Only While Using" is now always an option for users

#191

Earlier quoted context omitted.

> I mean let's be honest for once, the gain from removing 32b frameworks is pretty much entirely on Apple's side I've given you multiple concrete benefits to end users. You may not personally care about the code size difference, and you seem to be completely discounting the speed / memory usage issues, but just because you personally don't think those are a big deal doesn't mean they don't actually exist.

> I've given you multiple concrete benefits to end users There are not benefits since they break software . You can get pretty much all of these by just removing remaining 32b software from your system .

Two things:

1) Just removing all 32-bit apps doesn't recover the disk space used by the 32-bit versions of frameworks, and

2) If you remove all 32-bit apps, then there's literally no point to retaining the 32-bit OS support anyway.

Re: iOS 11 Location Privacy: "Only While Using" is now always an option for users

#192
post #152

Earlier quoted context omitted.

There's no good reason it should do so when backgrounded.

>There's no good reason it should do so when backgrounded. Wrong, and it's especially irksome that just because you cannot think of a good reason, you leap to the unfounded conclusion that there is no good reason. When you are driving and not using the app and not even thinking about the fact that you have the app, and not planning to use it, it can still be gathering useful traffic information to help route other us…

I can't think of an example where it would gather useful location data while I'm sitting at my home that couldn't be inferred if it was only allowed to use geo while in-app.

Re: iOS 11 Location Privacy: "Only While Using" is now always an option for users

#193
post #192
post #152

Earlier quoted context omitted.

>There's no good reason it should do so when backgrounded. Wrong, and it's especially irksome that just because you cannot think of a good reason, you leap to the unfounded conclusion that there is no good reason. When you are driving and not using the app and not even thinking about the fact that you have the app, and not planning to use it, it can still be gathering useful traffic information to help route other us…

I can't think of an example where it would gather useful location data while I'm sitting at my home that couldn't be inferred if it was only allowed to use geo while in-app.

Just because you can't come up with any examples doesn't mean that other people can't. You aren't the only person capable of thinking of examples.

Some examples:

It's useful to know when you have arrived home and are no longer moving.

It's useful to know when you have started moving and left home.

It's useful to know where your home is so that it can guide you home and for other traffic related reporting reasons listed above and below.

It's useful to know where other homes are or other places you spend time, where it may be significant that you are arriving and staying for a long time, as opposed to for just a minute or two (as at a traffic light).

It's useful to know that your non-motion is not an indication of traffic being stopped on your road.

It's useful to know that non-motion when you are away from your home may be an indication that traffic is stopped on the road you are on.

All of these are directly relevant to explicit, openly featured Waze use cases.

Post reply on HN