They are either defending themselves against personal attacks / harassment (which was also present in this thread before moderation intervention) or correcting unintentional misinformation about GrapheneOS features. That misinformation is often made by drawing a wrong comparison between GrapheneOS and other OSes. Correcting that isn't harassment, just like defending yourself against personal attacks isn't harassment.

I'm not going to participate in speculation and rumouring about this. I have an idea about who it might be myself but prefer to not talk about it. Negotations/talks are still ongoing.

Timewindow 2026, perhaps 2027 for release of such devices. Talks have been going on for a few months, if it wasn't working out at all that probably should've been clear already.

It won’t apply to GrapheneOS. It only applies to certified OSes and GrapheneOS is not certified because it doesn’t license Google Mobile Services.

It won’t apply to GrapheneOS. It only applies to certified OSes and GrapheneOS is not certified because it doesn’t license Google Mobile Services. It doesn't bundle it and it's also not part of AOSP so that GrapheneOS is built on AOSP doesn't matter.

GrapheneOS still intends to support all the supported devices until EOL. The sideloading change doesn’t affect them. It won’t apply to GrapheneOS. It only applies to certified OSes and GrapheneOS is not certified because it doesn’t license Google Mobile Services. As per the rip out of the device trees for Pixels, that just makes Pixels like other phones. GrapheneOS has been able to expand it’s automation to build that device support themselves. For new devices, making the support will take longer than it did in the past though, but they will still support those Pixels, as long as they meet the hardware requirements and still allow third-party OS support with all security features intact. Besides that GrapheneOS is actively talking with a major Android OEM right now in order to help them reach the security requirements for a subset of their future devices. They are very optimistic about tha

GrapheneOS still intends to support all the supported devices until EOL. The sideloading change doesn't affect them. It won’t apply to GrapheneOS. It only applies to certified OSes and GrapheneOS is not certified because it doesn’t license Google Mobile Services. As per the rip out of the device trees for Pixels, that just makes Pixels like other phones. GrapheneOS has been able to expand it's automation to build that device support themselves. For new devices, making the support will take longer than it did in the past though, but they will still support those Pixels, as long as they meet the hardware requirements and still allow third-party OS support with all security features intact. Besides that GrapheneOS is actively talking with a major Android OEM right now in order to help them reach the security requirements for a subset of their future devices. They are very optimistic about that.

GrapheneOS has largely worked around this by automating creating device support themselves using "adevtool". The current Pixels' hardware supports installing third-party OSes and will continue to do so, they will support those Pixels until EOL. For future Pixels (Pixel 10 series has not yet launched, only available for pre-order), it remains to be seen whether they still fully support installing third-party OSes. If they do, GrapheneOS will also support them, but it might take much longer to implement device support because they need to make this by themselves and this is more difficult doing it from scratch than being able to use the old Android device support for it as a base, like they could do for the existing devices when Google did their rugpull.

They have not really vendor locked themselves for the future. They have hardware requirements listed in their FAQ: https://grapheneos.org/faq#device-support Google just happened to be the only company meeting those requirements, which weren't even that strict, becuase other OEMs just didn't prioritize security.

But, there is good news. GrapheneOS is currently in active talks with a major Android OEM right now in order to help them meet the security requirements for a subset of their future devices. They are very optimistic about that.

GrapheneOS is currently actively talking to a major Android OEM in order to help them reach the security requirements for a subset of their future devices. If that succeeds GrapheneOS will be able to run on non-Pixel devices.

There is a lot of misinformation and harassment material circulating online about Daniel Micay. Notice that they are the victim of extensive online bullying which has spread all the way onto KiwiFarms. Would suggest not consuming that content because it won't give you an accurate depiction at all.

I'm a community member of GrapheneOS and I've not had any bad experiences with the GrapheneOS team or Daniel Micay specifically. They maybe communicate a bit more directly than some other people do but they are not being toxic or aggressive at all. I've found them to be patient and understanding.

Note that the thing many people describe as "toxic behavior" refers to posts made by GrapheneOS social media accounts in response to harassment. Defending yourself against harassment is not toxic. It might not look good in isolation becuase the quality of those conversations often degrades very quickly, which will have an impact on the GrapheneOS responses, but you have to look at those messages in context.

GrapheneOS is not developed by a single individual. GrapheneOS has a team of around 10 full-time developers. They are not on bad terms with all other OSes, they say positive things about iOS regularly. They were also on positive terms with DivestOS before it was discontinued also mainly because it was being harassed by the same groups GrapheneOS is being harassed by.

The founder of GrapheneOS, to person you are referring to, is not mentally unstable. You are making this statement without any basis. You do not have access to their medical file. What you are saying is hugely inapprioriate and the behavior of a high school bully. Even if it were true (it isn't), you are being an ableist, which just makes you a mean person.

GrapheneOS only runs on Google phones currently because only Pixels are able to meet the hardware requirmeents. The hardware requirements aren't a very high bar, other OEMs just don't prioritize security. GrapheneOS in active talks with a major Android OEM right now in order to help them meet the security requirements for a subset of their future devices. They are very optimistic about how that is going.

It won't apply to GrapheneOS. It only applies to certified OSes and GrapheneOS is not certified because it doesn't license Google Mobile Services.