A Dutch bank (Triodos Bankieren NL) has added explicit support for GrapheneOS and will be testing it going forward:

GitHub

Triodos Bankieren NL · Issue #133 · PrivSec-dev/banking-apps-compat-report

Is there an existing issue for this? I have searched the existing issues App name Triodos Bankieren NL Link to app https://play.google.com/store/ap...

They join a growing number of banking apps actively permitting users to use a much more secure device instead of trying to ban it instead.

Vanadium version 138.0.7204.157.0 released:

GitHub

Release 138.0.7204.157.0 · GrapheneOS/Vanadium

Changes in version 138.0.7204.157.0: update to Chromium 138.0.7204.157 change default value for "Protected content" (DRM) site setting to ASK inst...

See the linked release notes for a summary of the improvements over the previous release and a link to the full changelog. Forum discussion thread:

GrapheneOS Discussion Forum

Vanadium version 138.0.7204.157.0 released - GrapheneOS Discussion Forum

GrapheneOS discussion forum

#GrapheneOS #privacy #security #browser

Robert Braxman has published another video spreading blatant misinformation about GrapheneOS in order to promote his highly insecure products and services. In addition to many false technical claims and fabrications about our team, he's falsely claiming the project is dying.

GrapheneOS is currently under a state sponsored attack attempting to misrepresent it as being for criminals, which we covered a bit at

Mastodon hosted on grapheneos.social

GrapheneOS Mastodon

GrapheneOS server for official project accounts and project members.

These poorly researched, biased and inaccurate news stories have led to more harassment towards our community and team.

GrapheneOS based on Android 16 has been through extensive public Alpha/Beta testing and should reach our Stable channel today. We'll continue fixing various upstream Android 16 regressions such as the back button issue impacting the stock Pixel OS we fixed in our latest release.

GrapheneOS based on Android 16 is now available in our Beta channel. There are 2 main known issues which will be fixed in the next release: lockscreen date and media info are not properly displayed due to an upstream AOSP bug and Pixel Thermometer doesn't appear in our App Store.

Android regularly adds and splits permissions for new API levels. Legacy apps are handled by treating them as requesting the permission to provide a toggle for it. For example, Android 13 converted the existing toggle for disabling notifications for an app into a new POST_NOTIFICATIONS permission.

We're having some issues with federation and have temporary removed the previous thread until it's resolved. Can a few people confirm they can see this post being federated to their instance? We'll remove it and post the previous thread again once that's confirmed.