10 ms·
The fallacy is that AOSP (which GrapheneOS forks from), and Chromium used to install it, are both dependendent on Google engineers, money, and the willigness to
by pjmlp 1y ago
The fallacy is that AOSP (which GrapheneOS forks from), and Chromium used to install it, are both dependendent on Google engineers, money, and the willigness to keep the platforms open, to some extent.
- gradientsrneat 1y agoA fallacy which the author acknowledges. > "I guess the best way to degoogle right now is to buy from Google" Google has a monopoly on sort-of-open-but-not-really smartphones. And interoperability on ARM desktop isn't looking pretty either.
- pjmlp 1y agoThis looks the same kind of situation when I noticed FOSDEM corridors started to be full of Apple laptops, but apparently the irony is lost on new generations.
- hungmung 1y agoI remember about 10 or 15 years ago somebody pointed out that a big chunk of the GNOME devs used Apple laptops, even at public appearances, and it answered a lot of my questions about the state of the project. (and I say this as a user of GNOME)
- estimator7292 1y agoI think that perfectly explains why GNOME is the way it is. Funny enough, that's also why Windows is in the state it's in. Funny how that works.
- jajuuka 1y agoThey really don't. It's just that development of custom roms like GrapheneOS are centered around Pixels. Plenty of other devices have unlockable bootloaders. The custom rom scene though is so small that concentrating on a couple devices is the only way to keep development moving forward though. Same reason why Asahi Linux is the only option on Apple Silicon Macs.
- wkat4242 1y agoMany have unlockable bootloaders (though the number is rapidly declining with Samsung closing up). But not many have relockable bootloaders. This is one of the things that grapheneos have set as a minimum standard, hence the reliance on pixels. There's a few other specific things that the titan chip provides which they rely on but the relocking is the main thing.
- ycombinatrix 1y agoTo be more specific - relockable with a custom AVB key. I think most devices can relock with the default Google AVB key.
- wkat4242 1y agoWell they can but not with custom firmware installed. As grapheneos is custom firmware, the google key makes no sense in this context.
- subscribed 1y ago"unlockable bootloader" is the requirement to flash anyone alternative on the phone, yes, but the GrapheneOS you mentioned will support _any_ device that is "flashable" and secure enough: https://grapheneos.org/faq#future-devices https://grapheneos.org/faq#future-devices Currently it's only Pixels from 8 up. Other alternative firmware projects don't seem to be too concerned about security (eg they don't support relocking bootloader, don't support secure boot, don't release patches for months), so they're not really in the same ballpark ALTHOUGH I agree that they still might be better option than stock OS on the device abandoned by the vendor.
- subscribed 1y agoThere's simply no choice with hardware now if someone wants it to meet some secure baseline. No other vendor makes secure android hardware.
- neodymiumphish 1y agoIs your alternative that someone should build a complete from-scratch alternative OS that can still be booted on the same hardware? For the time being, AOSP and Chromium are still open source, so why not piggy-back off of all that labor and development to provide what GrapheneOS users want at minimal cost and effort?
- pjmlp 1y agoIf the goal is to be fully free from backdoors and development being cutted out at any time, yes.
- neodymiumphish 1y agoIf the source is fully open (it is) than detecting and disabling backdoors is completely possible. Not to mention the fact that other OS projects face the same risks. If Google cuts development of AOSP in favor of some closed-source alternative, the GrapheneOS team could simply continue development of AOSP on their own.
- wolvesechoes 1y ago> If the source is fully open (it is) than detecting and disabling backdoors is completely possible There exists a possible world where a group of underpaid FOSS devs forked Chromium and AOSP and effectively developed it further. But it is not our world. > the GrapheneOS team could simply continue development of AOSP on their own. They won't be able to do so.
- neodymiumphish 1y agoWhich makes the idea that a group like them could build their own OS from scratch all the more unattainable... That's the point I'm trying to make. At least if Google ever drops AOSP, it would be when it's still an intact OS available to continue development on. Additionally, I suspect a group like Graphene could get a lot more support developing AOSP's replacement in that instance, considering how many other manufacturers and devices utilize AOSP-derived software.
- phendrenad2 1y agoNah I consider that a fallacy. I'll call it the fallacy of the oranges. Let's say I control all of the orange trees in town. People resell my oranges. I begin using really strong insecticide that resellers try their best to wash off. I keep upping the strength and they keep trying to remove it. At the same time, there is one banana tree in town, and conveniently for my analogy, no pesticides are needed for bananas. As oranges continue to become worse, people will keep eating them, and saying that "there's no way people can switch to bananas. If they could, they would have already. And besides, there's only one tree..." Yes but these things can change. And eventually, people will switch to bananas en masse. People will truck in bananas. And we'll all act like we predicted the great banana switch the whole time. Like MySpace to Facebook, or Digg to Reddit. Or GSuite to Outlook. Or Skype to Zoom.