I'm not big on this general line on argument, but one point in particular:
> And of course, fairphone’s hardware and OS are nothing to write home about. For the freedom and security nerds they’re better off with GrapheneOS on Pixel or whatever upcoming Motorola phones will support it.
For the "freedom nerds", FP is one of the only (if not the only?) vendor to have official support for microG-based operating systems, seamless OTA updates and everything included. The Murena e/OS offering in particular is simple enough that the non-nerds that (perhaps less outspokenly) care about freedom can just pick it up with little change in habits.
I guess that’s true, although we could possibly split that camp into two sides: the folks who believe that Play Store sandboxing is going to be more functional, and the folks who prefer microG are willing to accept the issues that come along with it.
To be fair on either side of that debate, getting a phone that comes with /e/OS installed from the factory is going to be easier than flashing GrapheneOS on a Pixel or LineageOS with microG on another device.
Devices are sold with GrapheneOS installed. Installing it with the web installer is very easy and safe so that's the recommendation for nearly everyone.
> For the "freedom nerds", FP is one of the only (if not the only?) vendor to have official support for microG-based operating systems, seamless OTA updates and everything included.
I am not sure what you are trying to say here. I have never had an Android system that did not have OTA updates. Everything included... I usually like to install the apps I want?
As for microG, I think it's debatable. Is it better to have microG contacting the Google servers or sandboxed Play Services going through a Graphene-powered proxy? And say you have microG going through a Murena proxy (do they do that?), is that significantly better than sandboxed Play Services? At the end of the day, your system is made mostly of code written by Google (AOSP).
> The Murena e/OS offering in particular is simple enough that the non-nerds
Yes, I think it's what makes Murena successful. It's surprisingly simple to install GrapheneOS on a Pixel (you follow a wizard on a Chromium browser and click "next" a bunch of times), but many people are scare just by the idea.
> I am not sure what you are trying to say here. I have never had an Android system that did not have OTA updates. Everything included... I usually like to install the apps I want?
The last bit of my sentence could easily be misread as an enumeration of three things ("microG", "OTA updates", "everything included"), but it was actually an elaboration: FP is the only vendor to support microG, and (in contrast to "unofficial" microG setups) it doesn't require sacrifices in convenience because standard features like OTA updates work just like with your average Android. Perhaps that's clearer?
(Notably "Everything included" does not mean it ships a thousand apps or something. To the contrary, FP stock OS is mostly vanilla Android)
Point being: I could install LineageOS on my last phone, but it was a poorly documented process, updates were a hassle (having to flash through custom recovery for lack of OTA), and I had virtually no confidence in data integrity when running major updates.
> Is it better to have microG contacting the Google servers or sandboxed Play Services going through a Graphene-powered proxy?
How about microG not contacting Google servers at all?
In any case you're presenting an unnecessarily binary argument though. Letting Google handle push notifications is different from using them as your location provider, and both are different from letting all Play Services lose on your system.
> How about microG not contacting Google servers at all?
I already addressed that in my comment, right after the line you quoted.
> Letting Google handle push notifications is different from using them as your location provider, and both are different from letting all Play Services lose on your system.
And what would you say GrapheneOS does of those? Do you know, or do you just assume that GrapheneOS does the worse there?
> I already addressed that in my comment, right after the line you quoted.
Where? You suggested it would go through Murena instead, but you can fully disable third party services by disabling external push providers and by using on-device databases for GPS. e/OS directly offers this configuration during initial setup.
> And what would you say GrapheneOS does of those? Do you know, or do you just assume that GrapheneOS does the worse there?
I'm not necessarily trying to present either as "better" or "worse" since they both have their merits depending what exactly you're after (which I don't feel this is the right time/place to have a detailed rundown of). It was the root comment that posited e/OS was strictly inferior for people who care about freedom.
> And of course, fairphone’s hardware and OS are nothing to write home about. For the freedom and security nerds they’re better off with GrapheneOS on Pixel or whatever upcoming Motorola phones will support it.
For the "freedom nerds", FP is one of the only (if not the only?) vendor to have official support for microG-based operating systems, seamless OTA updates and everything included. The Murena e/OS offering in particular is simple enough that the non-nerds that (perhaps less outspokenly) care about freedom can just pick it up with little change in habits.