For work, or for hobby?
Hobby: have AI document what it’s supposed to do, then work through it like the ship of theseus one function at a time replacing it with not bad code.
Work: use it, document the bugs, ninja in and clear them out one at a time until it works. Keep blinders on and ignore anything not directly related to each bug. Same strategy as legacy code.
Exactly, seems like this should be up to the consumer. The devs can say: pixels have best security, here’s a 2nd and 3rd option, here’s their pros and cons.
Because as much as I approve of privacy measures and security, my phone doesn’t have any lock screen. No pin, no biometrics, nothing.
I work from home, I don’t really travel, I have 4 children. Physical security is annoying. I want grapheneos for data security. I don’t have people trying to steal my phone, I do have people constantly stealing my data.
And without a non-pixel option (fuck google), I’m likely to go for to a competitor because, while their data security might not be as good as graphene, it is better than what I currently have.
Bring on support for more devices, and I’ll likely switch with my next phone.
Oh, is that why everyone hates matrix so much? I’ve been rocking it for years for me and my wife to communicate. It’s been pretty solid. Calls/video calls are hit and miss, but the chat has been great. I’ve never federated it. Account creation is locked down, local auth, etc.
From the Article:
GrapheneOS has historically maintained tight integration with Google Pixel hardware, citing security features like Titan M chips, verified boot implementation, and firmware transparency as critical requirements. Expanding to non-Pixel hardware represents a major strategic shift.
Motorola, meanwhile, has been investing heavily in enterprise mobility, device lifecycle management, and security solutions. Integrating GrapheneOS into that portfolio would give the company a strong privacy-focused differentiator in both consumer and enterprise segments.