Wow, so excited! Best sequel ever!

A noteworthy thing some may be unaware of:
At some point in time, the bloatware on Chinese stock systems most likely hit some really frustrating levels. Chinese government got mad and mandated the ability of uninstalling it.

Result?

Global stock ROMs now contain a significantly higher number of bloat you can't casually uninstall. You can disable it, you can uninstall it over ADB, but you can't expect the same level of ease given to you by Chinese stock ROMs. The screenshot you see is Chinese RealmeUI with nearly everything uninstalled directly from app drawer (ignore Google Play).

https://tuta.com/blog/how-to-disable-gemini-on-android

Don't login into your OS vendor's account. The capabilities and incentives of screwing you are way too high. "There was a contract which you accepted" is less of a working defense when a given contract is mandatory to use your device, rather than as optional as Google, Microsoft or Apple account. Corporations know it and will never screw an unlogged user as much as a logged one (even if they'll try either way).

Obviously you don't need an unlocked bootloader no matter how useful it'd be to unbrick when recovery dies (or a fixed build isn't available yet), to make sure the users won't say it's for nobody as it can't pass Play Integrity

https://developer.android.com/about/canary

https://www.reddit.com/r/NothingTech/comments/1lwqiob/nothing_phone_3a_camera_post_processing_adds_hair/

Usual stock camera experience.

If you find an issue with Nothing Phone 3 just because it's pricey and ugly, you're just a hater.

If you find an issue with Nothing Phone 3 because it's unergonomic, has a generic display, offers upper midrange cameras, entry level high-end SoC, the brand grifts off the "poweruser friendly" image and asks solid money for all of it despite the economies of scale, that's where it's at.

Pic

A phone stopped being usable because server said no :(
https://fixupx.com/developeruwu/status/1945021367939666004

(yes, I'm aware that you can probably bypass that in plentitude of ways, I just hope that activation mechanisms will be abandoned through an OTA whenever the servers stop handling them, but one could dream)

So Google already acknowledges the feasibility of proxying PIA results to/from (a good linguistic question...) vulnerable devices

To run an untouched (just kidding, the toggle in question and GP signing cause your app to be far from "untouched") original app enrolled into this unnecessary restriction, use:
pm disable com.your.app/com.pairip.licensecheck.LicenseContentProvider

https://github.com/pperez39/google-keys/

This repo is either a very high quality fake or Google's own leak of keyboxes they managed to obtain (not from themselves), divided into ones they decided to revoke and ones which they didn't. The details you can see in csv tables don't look like anything a third party would bother to catalogue.

Essentially, could say it's a mix of current state of revocations and a roadmap of future revocations.
It'd be exceptionally odd for any third party to mark the source of compromise in the level of details you can see in the csv, since it wouldn't really matter as long as you have a bunch of valid keyboxes around that would be obtained directly by you with no means of guessing how likely your gray market competitor would be to possess them.