microG

“microG having a history of leaking location data to apps which aren't granted access to it.”

“I'd rather have control who to use for my location API and be able to turn it off entirely.”

“MicroG is great because it limits Google's tracking as much as possible.”

“microG's leaks and failure to implement other checks and there's arguably no real gain in privacy”

“worse app compatibility, worse security (especially because of privileged access), and worse privacy (leaks)”

“That would require expanding trust to a 3rd party, and granting privileged access to software that downloads and runs google code.”

“microG still uses most of the same Google services and even downloads closed source Google executables”

“microG has repeatedly had vulnerabilities leaking sensitive data to apps including location data.”

“auditable FLOSS code running on my own device”

“MicroG stubs out the analytics and ads APIs.”

“microG on /e/ downloads and runs Google Play executables with highly privileged access by default”

“MicroG downloads and runs google code in a privileged context and has had many privacy and security issues”

“MicroG is a good compromise between deGoogling and having things work. GrapheneOS is not.”

“microG offers worse app compatibility and is less secure. The cons outweigh the pros by a lot.”

“microG lets you de-Google a phone, but the resulting phone is provably less secure”

“Particular there are contributions of me microG that are helpful if you want to de-Google ones phone.”

“I already addressed that in my comment, right after the line you quoted.”

“Is it better to have microG contacting the Google servers or sandboxed Play Services going through a Graphene-powered proxy?”

“It reimplements the Play Services APIs, but is FOSS and only connects to Google servers when it's necessary for some functionality”

“allowing you to choose your own provider for services where this is possible”

“it downloads Google's proprietary, obfuscated DroidGuard blobs (which they can change between requests)”

“those that run LineageOS/microG without rooting are largely fine”

“given the available options non-sandboxed MicroG is preferable to sandboxed always-on Google services”

“MicroG allows me to disable it when I want to, and push notifications still work when I (rarely) need to enable it.”

“MicroG is not an alternative to not using play services at all = actually avoiding Google, but a open source reimplementation that still has all the privacy and security issues of regular play services.”

“No, microG is definitely not talking to Google all the time, NetGuard would warn me if it did.”

“Micro-G mitigates a large portion of the Google data harvesting”

“MicroG is awesome wrt. that as you can turn it on/off as you wish, and it just works.”

“MicroG has two huge advantages: you can inspect the code it's running, and you're not tied to Google services.”

“does an excellent job at reimplementating most of Google's proprietary APIs on the client side”

“It's not obviously a better option: for instance, some things that are supported in Play Services are not supported in microG”

“provides dummy no-op implementations of Google Play tracking APIs, and allows you to select alternative Location Providers”

“With microG, your apps still connect to the Google servers, so you're not "breaking free".”

“the Android contact tracing APIs were actually reimplemented in microG, allowing these apps to work even on custom roms”

“microG, which is an open source implementation of the Play Services, but it means that it sends Play requests to Play servers”

“Micro G is an excellent Google Play Services alternative which is open source.”

“It runs plenty fine enough even without GApps (or with shims like microg)”

“If you need something permissively licensed, I believe microG also has implementation of the notification protocol”

“microG is a full, open source reimplementation and won't send any data to google”

“IMO, if you use microg you still allow your non-Google apps to contact Google.”