nostr:npub1ezrn7fluskc992cx6l4hcavz9vpl3g4usmnhq3hjee6u5syafvgqlx8tfr nostr:npub1jmlh72aghydlx785ljqlfsx473068wykyxlmaj829rqrm7t30hdqu2gnlz
I've heard the arguments, it just doesn't jive with me.
I will give them credit for having a somewhat private (God knows what GSF is *really* doing, even when sandboxed) implementation that's fully compatible, even with in-app purchases.
The fact that google apps automatically get your google account info even when everything was sandboxed is what gave me pause, and made me want to go back to MicroG.
nostr:npub1l3gpk6vrudg8r67swqlex5alv9ch59s4lw46kk6hekuxe2n3aczsyqvu48 nostr:npub1jmlh72aghydlx785ljqlfsx473068wykyxlmaj829rqrm7t30hdqu2gnlz That's because you're a moron and have no idea how any of this works.
/s
I hear the GrapheneOS community can be quite toxic.
Who us?
Your Google account is referenced by Inter Process Communication (IPC). A voluntary decision by the user when logged into Play Services.
Running Play Services in a secondary user means you can End Session, put it back to rest and prevent any further running. Play Services and Google API can only run if you use the former or install apps built with Google SDK that include them. You're in total control. Happy to discuss it more if you have concerns, questions etc.
MicroG is there in the system doing it's thing regardless all the time along with Google connectivity checks, network time, attestation key provisioning, SUPL, PSDS (Pixel 6 and 7), eSIM activation. Nevermind that while the 'implementation' is open source the rest is still privileged Google Services on other OS.
Whatever though, we all pays our money and makes our choices, your prerogative to use what fits so long as you're happy alls well with the world.
Take care and be well.
