HybridStatAnim8

The security features are not niche, you are claiming that arbitrarily. The needed hardware security features are generic and industry standard, OEMs are just lazy and choose to ignore such improvements.

GrapheneOS is not obsessed with google. Other OEMs have simply failed to reach the needed hardware securuty requirements, which will soon change. GrapheneOS also is not interested with maximizing adoption above all else. They will not sacrifice privsec for the sake of broad device support.

None of this is true, you seem to be making it up for the sake of attacking them. Google is often criticized and has been for years. That was never a bannable offense from the community chats. Nobody from GrapheneOS has ever doxxed anyone, for any reason. GrapheneOS has retained support from people in various security fields and that has only improved.

Alternatives to google pixels have been explored since the inception of the project. The only difference now is that an alternative is about to exist where one hasnt before. GrapheneOS was interested in paying an ODM directly before Motorola reached out. GrapheneOS has never been pixel-only for any other reason than limited options.

GrapheneOS has never suppressed criticism or brigaded on social media. What is often described as "criticism" is a thinly veiled excuse to attack the project. Real criticism has always been appreciated.

Motorola devices are the priority but they will support devices meeting the requirements. If pixels fall to do this, no support, but if they succeed, no reason to stop using them. Only time will tell.

They are not interested in shoveling corporate slop. They dont know why, and so, that is what they said. That is a commendable trait and google has many things to answer for. Being silent only serves to benefit google by concealing this behaviour further.

They had to, as many users were purchasing pixel 11 devices before support was announced. Announcing an unclear future is fine and transparency is appreciated. Simply ignoring the problem is not a solution.

Neither of these options would have been chosen. GrapheneOS could have continued supporting existing pixels and investigated options paying ODMs directly for devices that met the requirements. They were considering this option before Motorola reached out.

Because google may have disabled it due to issues/errata. Google willing to enable it is a good sign it is fine, and at worst, affects stock OS as well. Google isnt answering GrapheneOS when they ask why it was disabled, so GrapheneOS cannot know if the implementation is acceptable or not.

Yes. That would remove the need to flash, which is a roadblock for many. Greenboot support and Auditor would ensure your install of GrapheneOS is genuine.

That was not the announcement. This was never stated anywhere. Motorola is making a subset of future devices meet the GrapheneOS hardware security requirements, greenboot and preinstalled options are not confirmed, and may not happen at all for the first few devices.

GrapheneOS is not interested in silencing themselves for the sake of greed and optics. Their image is built on explicitly not doing that.

You are making a false dichotomy, and suggesting they give into sanitized, corporate slop approaches rather than stick to their mission. GrapheneOS has gained the resources and relationships they have because they tell it like it is, not because they bend to the will of others out of fear.

GrapheneOS has no relationship with Google.

AOSP and its derivatives are linux distros.

Citation needed.

Upstream is both very contribution unfriendly and their treatment of GrapheneOS leads GOS to not want to contribute anything to them anymore.

I have no role in the project and that has been stated many times on social media.

Asking for support is not brigading. The vouch button exists for a reason.

Yeah it is. Their infrastructure costs are super tiny, the biggest percent of funding goes to pay the dev team, and many are paid a wage comparable to where they live, they dont get inflated US software dev wages or anything.

Most of what they earn is public as a result of the donation method, like crypto. And most donors are completely anonymous.

GrapheneOS does not accept any funding with strings attached.

GrapheneOS makes 100% of their money off of donations, and have made quite a lot of it. The bottleneck is not funding, but finding talented developers to pay with that money.

The notification the Messaging app produces should have the option to copy the one time code directly.

At least it is now consistent with the rest of the OSs UI.

GrapheneOS has made a big push to hire a bunch of experienced, talented app devs, and they have been slowly chipping away at Messaging for a few months. They now have the resources to take on the AOSP apps and resume with the GrapheneOS apps. The rest of the AOSP apps are also planned to be overhauled.

They also plan to eventually support RCS in the Messaging app.

GrapheneOS wants to eventually support RCS in the default chat app. It may take a lot of time for it to work without google components/google services but it is the eventual plan.

Not yet, but they do plan to add support for it.

It will get ported to kotlin, material 3, and jetpack compose, just like Messaging.

Good news! GrapheneOS has ported Messaging to kotlin, jetpack compose, and material you. The same is planned for the Contacts app, Dialer app, and more. Dont quote me but it seems Contacts and Dialer are up next after Messaging.

Also, GrapheneOS has very recently released automatic call recording for the Dialer.

GPLv2 and Apache 2.0 are not incompatible licenses when bundled together. GPLv3 is the problematic license as it requires all code it is bundled with be GPLv3 as well.

When it comes to AOSP/GOS, bundled apps are not aggregated together, they are built and signed under a singular OS binary.

Whether or not you tolerate using RCS is up to you. Not supporting it for the sake of having a worse default option on the off-chance you can use the to convince them to use a better option is not a good reason to not support RCS.

Either you will have people content with SMS, or you will have people content with RCS. Which is better is obvious.

I am not on the GrapheneOS team but the community does push better options such as Molly/Signal and RCS is usually only advised as a fallback messenger.

Florisboard.

Unsure what you mean by link against it. GPLv3 requires making the entire project it is bundled with GPLv3 as well. GrapheneOS would need to relicense the entire OS and bundled apps as GPLv3 to allow them to use any app with that license.