alt Hacker NewsThere is no such thing as non-Google Android. At most you have people applying tiny patches on top of AOSP, but 100% of the code in the underlying project is still Google-approved, and none of the alternatives have control over that.
It's the same as the situation with Chrome/Chromium. There are a million "de-Googled"/"privacy focused" alternatives to Chrome all using the same engine, and when Google pushed manifest v3 changes to block ad-blockers every single one of them was affected.
Replies
> and when Google pushed manifest v3 changes to block ad-blockers every single one of them was affected.
That's just objectively wrong, both Brave and Opera still support manifest v2 and are committed to continue doing so for the foreseeable future. Even Edge apparently still has it, funnily enough.
At most you have people applying tiny patches on top of AOSP, but 100% of the code in the underlying project is still Google-approved, and none of the alternatives have control over that.
You are making an orthogonal point. Yes, Google maintains AOSP. No, that does not mean that AOSP OSes that are not in Google's Android program (calling it that to avoid semantics games) have to adopt this change. If you want to hear it from the experts: https://grapheneos.social/@GrapheneOS/116103732687045013