By “Google’s fuckery” you mean “Google doing all the updates and giving it to them” though, right?
Until these alternative AOSP-derived OS developers stop relying on Google and start doing their own stuff, Google will have the ability to break their OS’s. This isn’t a Google issue, it’s a OS developer issue.
WhyJiffie@sh.itjust.works 2 weeks ago
they can take down the code today and not much will happen, as the code is mirrored elsewhere.
rumba@lemmy.zip 2 weeks ago
Obv, they can’t take what we have, which is why for now we’re OK. The winds are shifting, though. I expect at some point, I expect android will require a deal with the devil from manufacturers. Start actively combatting linux phones.
For now, it’s a quick path to privacy, long term, we’re going to need friendly hardware
mfed1122@discuss.tchncs.de 2 weeks ago
I think the big problem with this, as far as I know, is that this code needs pretty rapid security updates that require a fairly huge and experienced team of people to both find, understand and implement the security changes. Otherwise it becomes very insecure very quickly. So yeah we can always use 2019 Android, etc. But it would just put you at a huge security risk.
WhyJiffie@sh.itjust.works 2 weeks ago
doesn’t the same apply to any operating system, including the linux phone distributions? android has security measures that may be breached, but mobile linux has much fewer security measures at all
mfed1122@discuss.tchncs.de 2 weeks ago
Yes, it does apply to every operating system - hence, the differentiator becomes whether the operating system has hundreds of millions of dollars to spend on dedicated security development. This is why a lot of companies now don’t even let you use Android devices for BYOD aside from Google or Samsung, because they’re the only companies with the resources to keep their security really up to date.