Conversation

Daniel Micay
@DanielMicay
Replying to
@DanielMicay
F-Droid has now deleted their own harassment from gitlab.com/fdroid/fdroid-. It's quite possible they'll delete their dishonest messages and coordination of talking points from their development room. I archived it for a reason. They usually try to cover up and deny their abuse.
gitlab.com
Draft: blog post about android permissions (!834) · Merge requests · F-Droid / Website · GitLab
I came across an article claiming that Google Play stopped displaying app permissions. And since we've been criticized for displaying them. I think it might make sense to...
1
19
Daniel Micay
@DanielMicay
They've continued this across platforms and are coming up with a fake story / spin about what happened, but I have archives of both the initial abusive behavior in their development room and then what they did on the issue tracker after I responded to that which is linked above.
1
9
Daniel Micay
@DanielMicay
I have irrefutable proof that multiple core F-Droid and Calyx developers (substantial overlap) have engaged in bullying, harassment and libel targeting me to advance their own interests. Is anything going to be done by
@hopeconf
and others platforming these long term abusers?
1
10
Daniel Micay
@DanielMicay
Not that it particularly matters, but it's worth noting the topic in question involves them trying to mislead users about the Android platform's app sandboxing and permission system to excuse F-Droid mishandling permissions and giving users inaccurate info about what apps can do.
1
9
Daniel Micay
@DanielMicay
They've been criticized by several privacy/security researchers about their approach to this and other things including serious flaws in their build infrastructure, approach to distributing apps and in their app. Instead of improving, they're putting out posts misleading people.
1
8
Daniel Micay
@DanielMicay
F-Droid will have to be marked with a warning dialog in GrapheneOS explaining the cross-profile install conflicts it causes which place a substantial support burden on us, security issues with their builds, infra and app and the very misleading inaccurate permission listings.
1
9
Daniel Micay
@DanielMicay
They won't fix these problems, and many of our users are using F-Droid. This creates major security issues for our users which they will not address, along with a massive support burden on us where many new users run into the conflicts caused across profiles from app id misuse.
1
9
Daniel Micay
@DanielMicay
Very normal for a new GrapheneOS user to install F-Droid, use their main profile, then attempt to install F-Droid in a 2nd user. This doesn't work due to them not updating the download link. We think they're refusing to fix this out of spite towards OSes not bundling F-Droid...
2
9
Daniel Micay
@DanielMicay
Replying to
@a_j_42
Any number of profiles can have the same app installed. F-Droid is reusing app ids for different apps, which is not supposed to be done, and causes conflicts, since apks are shared across profiles with the apps installed and key pinning / downgrade protection is applied globally.
2
Daniel Micay
@DanielMicay
Replying to
@DanielMicay
I explained why it happens due to their reuse of app ids and also separately because of them posting an outdated download link for F-Droid itself. 2 separate reasons they trigger 2 separate errors (invalid key and downgrade protection) which do have 2 different error messages.