Conversation

Google have suspended Element in the Play Store without notifying us; we're reaching out to find out what's going on. Apologies for the inconvenience; in the interim there's f-droid.org/en/packages/im but it's a few versions behind. We'll post updates here.

1,205

1,761

Replying to

and

Maybe a good idea to push the newest versions to f-droid at the same time as you push them to play store in the future?

Replying to

and

That's not how the official F-Droid repository works. Developers don't release their apps through it. The way it works is the F-Droid packagers choose apps to package and are responsible for keeping them updated. They could make their own F-Droid repository to do it themselves.

Replying to

and

The issue with that is F-Droid handles it quite poorly and confuses users since the app releases signed with different signatures are incompatible. Perhaps F-Droid should add an app id prefix when using their own signing keys but they aren't doing that. It's a bit of a mess.

1:33 AM · Jan 30, 2021Twitter Web App

Replying to

and

Huh thanks for clearing that up, didn't know it worked that way. It seems that F-droid needs some improvement considering how much it is quickly becoming critical FOSS infrastructure.

Replying to

and

I don't feel like it's on the path to becoming what's needed. For GrapheneOS, we're going to be making our own app install / update system. One of the apps we'll provide in our repo is F-Droid, but we aren't comfortable bundling it with the OS or giving auto-install privileges.

Show replies

Andrea1 of AWCY? & Weight Forward & Gun CAD Ideas

Replying to

and

Here is some constructive criticism for the future of the app, from the man that makes GrapheneOS possible.

Replying to

and

The best solution is to create own fdroid repo, no ?

Replying to

and

If you want it signed with your keys you can run your own fdroid repo. Having fdroid sign the app is actually something I like as it is a second party compiling your code independently. If I sign the build I need to provide some way to validate I didn't alter the source.

Replying to

and

Reproducible builds would be that validation method, ideally.

Janne Mareike Koschinski

Replying to

and

You can do both. For example I publish quasseldroid (my own app) on the official fdroid repo as well (with at most 24h delay). And you can also package your app for app droid with a package name prefix or suffix. I'm surprised you don't know any of this.

Janne Mareike Koschinski

Replying to

You could even use the reproducible builds solution to have the fdroid and your own builds both use the same signature.