I think saying it’s just as bad is an overstatement. MicroG sends fake data or no data in the majority of data calls from Google servers and only interacts with Google when it needs to in order to make a given app function. Sending drastically less data to Google is a win and fits many people’s threat model just fine.
As long as micro G is a system app in my opinion it is the same why not run it as a sandboxed app. There is probably a reason why it can’t just think it would be more privacy first approach to sandbox it but that is just my opinion everyone’s threat model is different I don’t use Google at all anymore so non issue for me. Still better than stock Google Play true just think micro G could do more.
This interview with the developer of MicroG might be interesting if you’d like to learn more about it’s benefits (or downsides) over sandboxed Google Play services. It debunks a lot of misconceptions or rumours about MicroG.
MicroG collects very little information about the user. It does less data collection than sandboxed Google Play despite it being a system app. MicroG is a more transparent, community driven piece of software that distances people from Google to a greater degree in my estimation, though I don’t have developer level understanding of the software. Just basing my thoughts on interviews and published information like the video above.
Personally I prefer the privacy/open source oriented approach of MicroG, but I also run GrapheneOS so haven’t been able to use it for a few years.
Thank you already seen this and like I said if it’s a system app it’s a no go for me any app to do with Google needs to be sandboxed being a privileged app is why I won’t use it.
MicroG is a fully open source, much smaller codebase (reduced line count) vs proprietary google binaries. I wish I could run microG on graphene, but absolutely will choose microG on calyx vs sandboxed play svcs.
I think saying it’s just as bad is an overstatement. MicroG sends fake data or no data in the majority of data calls from Google servers and only interacts with Google when it needs to in order to make a given app function. Sending drastically less data to Google is a win and fits many people’s threat model just fine.
As long as micro G is a system app in my opinion it is the same why not run it as a sandboxed app. There is probably a reason why it can’t just think it would be more privacy first approach to sandbox it but that is just my opinion everyone’s threat model is different I don’t use Google at all anymore so non issue for me. Still better than stock Google Play true just think micro G could do more.
This interview with the developer of MicroG might be interesting if you’d like to learn more about it’s benefits (or downsides) over sandboxed Google Play services. It debunks a lot of misconceptions or rumours about MicroG.
MicroG collects very little information about the user. It does less data collection than sandboxed Google Play despite it being a system app. MicroG is a more transparent, community driven piece of software that distances people from Google to a greater degree in my estimation, though I don’t have developer level understanding of the software. Just basing my thoughts on interviews and published information like the video above.
Personally I prefer the privacy/open source oriented approach of MicroG, but I also run GrapheneOS so haven’t been able to use it for a few years.
Thank you already seen this and like I said if it’s a system app it’s a no go for me any app to do with Google needs to be sandboxed being a privileged app is why I won’t use it.
MicroG is a fully open source, much smaller codebase (reduced line count) vs proprietary google binaries. I wish I could run microG on graphene, but absolutely will choose microG on calyx vs sandboxed play svcs.