> see smartphone announcement
> "the most privacy-friendly smartphone"
> look inside
> mediatek
> proprietary components in userspace
every time
@weirdtreething it's not the soc vendor where this matters (every mobile soc has proprietary bits and uses a downstream kernel).
Unfortunately, where we can run modern kernels and upstream userspace, (e.g. postmarketOS) we don't have all the other pieces necessary to build a fully secure OS.
For privacy though, it's still gonna be better than de-googled AOSP. Android kinda has tracking/telemetry so baked in that it's really hard to avoid
@weirdtreething proper sandboxing, immutable rootfs, and realistically several rounds of professional security review. probably 2 years before it would make sense to think about going for that (since we need to get our architecture a lot closer to how we want it).
also security review for all our processes around stable, how we build and distribute packages and images, etc etc. If we want to be serious about it.