@nprofile1q... New major releases of Android resolve major privacy weaknesses and greatly improve security with new features.

High/Critical severity patches are backported to older releases, but not new protections. Near zero Low/Moderate patches are backported. Android is moving to no longer backporting most High severity patches and many Critical severity patches due to AI accelerating vulnerability discovery.

Pixels driver and firmware updates also require the latest release, currently Android 17.

@nprofile1q... See https://eylenburg.github.io/android_comparison.htm for a third party comparison between operating systems based on the Android Open Source Project (AOSP). It doesn't cover the many connections added by operating systems and doesn't cover a lot of added privacy or security features but it gets across how different the overall approach is across these.

Keeping up with standard updates is very important. GrapheneOS moved to Android 17 on day 1. None of the others there has moved. That's required for many patches.

@nprofile1q... GrapheneOS greatly improves both privacy and security compared to the Android Open Source Project while CalyxOS does the opposite by lagging far behind standard patches and protections. They're not in the same space.

Nearly every Android app is compatible with GrapheneOS. It has our sandboxed Google Play compatibility layer to run apps depending Google Play. Banking apps are a special case but most work. App compatibility is much work on operating systems using microG including CalyxOS.

@nprofile1q... You can clear the app data for Seedvault and do it over again. We know the user interface for it needs a lot of work. It needs a massive overhaul and at least a partial rewrite.

@nprofile1q... @nprofile1q... It was eventually suspended there too a while after this discussion.

@nprofile1q... mastodon.social has suspended it now.

@nprofile1q... It was suspended by the infosec.exchange moderators, not mastodon.social. An instance can suspend an account from another instance to block any of the content being visible or any direct interactions with the account such as replies. It got reported by a bunch of people even before we replied so some instances have blocked it, but not the one it's actually hosted on. We would prefer if the person who made it renames the website and the accounts themselves so we reached out here.

@nprofile1q... As an example, our Vanadium browser is a play on the name Chromium. Stainless steel is made by adding chromium and vanadium is often added to give it further strength. Vanadium is a very distinct name from Chromium so there's little room for confusion but it also shows the basis for the project. You could make your own name for this that's similarly distinct but it could be some variation of carbon, another nanomaterial or something like that if you want it to be tied to it.

@nprofile1q... It needs to be made much clearer that this is an independent organization and not part of GrapheneOS. It should have a separate name that's distinct from GrapheneOS.

The website and social media accounts for it should use a distinct name after coming up with one. The website should be moved to a new domain with the distinct name and the previous domain can be temporarily redirected for several months.

As shown by the replies, many people think it's official or pretending to be.

@nprofile1q... He's a GrapheneOS user who makes video content about it. He isn't part of the GrapheneOS project himself and we aren't partnered in an official way. Our community manager is doing a live stream with him.

@nprofile1q... We arem't affiliated. He's someone with no official involvement with us doing an interview with our community manager.

@nprofile1q... We arem't affiliated but rather he's doing an interview with our community manager.