F-Droid's maintainer is against shipping builds of their app without rebranding the app id, app name and logo which is itself reasonable. However, F-Droid itself distributes builds of thousands of apps without following those same expectations for them...
matrix.f-droid.org/room/!UAdCANfo
Conversation
Replying to
This is definitely a big issue. I did the mistake of using the same app ID for GitHub and F-Droid builds for , and the users cannot switch between two without uninstalling the other. But I guess most F-Droid users are already aware of this.
2
The idea is to follow the example of projects like Debian, Mozilla, etc and enforce #FreeSoftware. Someone could otherwise easily embed proprietary bits or repos, then ship it as "F-Droid". F-Droid does provide app devs the same option via , shipping their key even
1
Part of our inclusion process is asking the upstream app dev for permission, and they can specify a different Application ID, for example, f-droid.org/packages/com.c
1
I also agree that there should be less signature conflicts in the Android ecosystem, but I disagree using Google Play is a solution. The complete solution the F-Droid community is providing is #ReproducibleBuilds with developer's own signature.
2
It's vaporware that's barely used in practice and doesn't actually work reliably. You expect to impose your outdated and poorly implemented standards / software on others. F-Droid brings down the quality of the whole Android ecosystem and causes serious usability issues in it.
I'm not sure why anyone would choose to trust someone with a long history of abusive, dishonest and malicious behavior like yourself. As has been made clear you before, you are not welcome to post replies on the threads of someone you've been involved in repeatedly harassing.