Oops: Google admits failing to wipe all Android apps with location-tracking X-Mo
theregister.com
theregister.com
The real problem is corporations trying the destroy the open web, again. We had AOL and CompuServe, now we have app stores. Consumers have been conditioned to install apps for basic things, just so they can slurp up their data.
Unfortunately this round of internet-killers are much better funded. The open web won in the past, but there is no guarantee it will win this time.
It's an unfortunate development, but I wouldn't call it "conditioning", it didn't really look like a coordinated plan - just a textbook case of people with good intentions paving a shiny road to hell. Native apps are intrinsically superior to the web experience; this is true on mobile and desktop alike. The push to native apps came before tracking was so widespread, developers just wanted people to have a great experience.
Unfortunately, the amount of private data exposed by mobile platforms (and one of the two platforms being owned by an advertiser interested in such data) is so much more valuable than what was ever exposed on desktop... when this fact became common knowledge, consumers were screwed.
Though TBH I suspect that was added purely because it's a significant source of battery-drain.
What if library "A" is included in a background app with access to location services, it then locally broadcasts via UDP or listens on a TCP port for incoming local connections, so that a library "B" can either listen to those UDP broadcasts or connects to the local TCP port of library "A" to receive the location data. Is this a possible scenario? Is Android monitoring such a behavior?
The solution isn’t to turn off location services, but to use permissions so that only apps I approve can have access to it. Both iOS and Android have that feature.
So, I have Mozilla location services running on my LineageOS phone instead of Google’s, but only because I'm that tiny minority of nerds who knows how to do all that. Ordinary people might prefer to simply install MicroG’s fork of LineageOS, which avoids Google outright and provides third-party location services.
I'd use GrapheneOS where possible. Consider making it possible where it's not.
I would prefer Apple and Google not receive my 24/7 tracklog. I don't believe that I need to have anything to hide to say that I don't think it's reasonable for an advertising company to know where I am 24/7/365.