Conversation

GrapheneOS version 2022080300 released: grapheneos.org/releases#20220. See the linked release notes for a summary of the improvements over the previous release. Forum discussion thread: discuss.grapheneos.org/d/373-graphene

grapheneos.org

GrapheneOS releases

Official releases of GrapheneOS, a security and privacy focused mobile OS with Android app compatibility.

Replying to

As always, thanks for all your work 👏 One thing I couldn't find out in the channel: are you planning to update the backup app? Upstream has some important changes (e.g. using davx5 webdav).

Replying to

and

Only after Android 13, and we don't trust the people who took over the project upstream so we can't simply take their changes unreviewed. In the long term we plan to replace it completely even if that means temporarily losing features.

Replying to

and

Yeah, I heard there were some tensions between the projects. As an open source developer, I understand how these things happen 😔 As an open source user, otoh, I just want all the shiny things developed anywhere of course 😇

Replying to

and

In the case of Seedvault, the original dev is an old friend of mine. So if I can be of any help in resolving issues or questions, let me know.

Replying to

and

The issue is that the original developer made it for GrapheneOS (when it had a different name) and shortly afterwards there was the failed takeover attempt on our project. Things were in very bad shape for over a year and it took a long time just to revive / restore what we had.

Replying to

and

Having a backup/restore app was a low priority at the time. Even now, doing something about it is a low priority. Despite all the massive advances, we've had to cut back in areas. There's a lot more focus on user-facing features now: sandboxed Google Play, Storage Scopes, etc.

7:04 PM · Aug 3, 2022Twitter Web App

Replying to

and

We've been focused on survival since 2018. The people who took control of that backup project are far worse than my former business partner. I trust them less. They portray it as something they originally made and use it to cause harm to us. We may remove it with no replacement.

Replying to

and

Every time I see it used in attacks on GrapheneOS, it's another step towards simply removing it with no replacement ready. That may happen just because we do not trust them and they have a history of downplaying, covering up and not fixing security bugs in their projects.

Show replies