Comment on Google's shocking developer decree struggles to justify the urgent threat to F-Droid
rumba@lemmy.zip 3 weeks agoIt’s still Android kernel and drivers :/ but it is private. For Linux you’d need postmarket or one of their derivatives and they are fighting to get cameras and power under control.
prob the best we have at the moment.
WhyJiffie@sh.itjust.works 3 weeks ago
and what’s the problem with android other than google’s fuckery?
rumba@lemmy.zip 3 weeks ago
Assuming google’s fuckery doesn’t affect them, nothing.
But we’re relying on google to keep up that code and not see them as a threat. Right now AOK, but in the future that makes longevity questionable.
It’s something to be noticed and understood so there’s no surprises when the company that did no evil now does all the evil.
WhyJiffie@sh.itjust.works 3 weeks ago
they can take down the code today and not much will happen, as the code is mirrored elsewhere.
rumba@lemmy.zip 3 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.
FreedomAdvocate@lemmy.net.au 2 weeks ago
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.