Hacker News Reader

Comment by IlikeKitties | Hacker News Reader

Fairphones consistently doesn't support a quarter of what graphene os requires. See their FAQ:

https://grapheneos.org/faq#future-devices

Unless Fairphone becomes significantly better in their security and update policy and integrate a whole lot of new features it's not gonna happen.

View on HN

>Fairphones consistently doesn't support a quarter of what graphene os requires

I expect it's not just a matter of feature support: Fairphone in general seems rather horrible on security, doing things like using test keys for production signatures [1].

[1]: https://forum.fairphone.com/t/bootloader-avb-keys-used-in-ro...

To be fair that's from 2022, I thought they fixed those issues on newer devices.

This is the whole point, they should stop nitpicking and start to do it (GrapheneOS side), even if it is not going to be THE most secure phone, there is enough of features that are far more useful then just security (like privacy). I don't mind if they make it payable. With money they will get (I suspect there will be quite a bit less pixels sold) they can make a new phone that will have all the bells and whistles GrapheneOS wants and on the other side, Fairphone developers will figure out it is $$$ worthy to do it.

GrapheneOS has bunch of requirements that are expensive while Fairphone has zero chance to figure out, if investing would make any economical sense, while their normal users dont really care about that security but might regarding privacy. This is a stale-mate position.

Found info about GrapheneOS installations, 250k users(1). Lets say 25% are on old pixels. This is 60k sold pixels.

All Fairphones sold by 2022 were 400k(2).

1. 2024, https://discuss.grapheneos.org/d/12281-how-many-grapheneos-u...

2. 2022, https://en.wikipedia.org/wiki/Fairphone

> This is the whole point, they should stop nitpicking and start to do it (GrapheneOS side), even if it is not going to be THE most secure phone, there is enough of features that are far more useful then just security (like privacy). I don't mind if they make it payable.

This feels super entitled to me. GrapheneOS Devs have a mission and they get to make that. You get it for free and if you like it you can give them money. If they don't support the hardware you like you are free to fork it and get it to run yourself.

And if security isn't something you care about but privacy is and you feel like there's a difference here you can still install /e/os or lineageos and similar on the fairphone.

Sure they have a mission. But sometimes mission can be done by taking 1 step back to later make 2 steps forward in fast pace.

At the end all profit. While in current state, the culprit, Google profits.

And please keep fallacies like "do it yourself" for yourself, I am talking about collaboration, feel free to open another thread on top level about forks.

Same goes for /e/ ... they just dont compare.

GrapheneOS has two use-cases that are they excelling with, security and privacy.

While security is not really my threat model (some rubber-hose cryptography aka large wrench, solves this issue for any attacker), privacy violations are everyones issue. Even if they dont care.

Reply on news.ycombinator.com