They flag git apps for having github integration with giant "promotes non-free services" ads, even if there is no actual promotion, just API support, and yet they have versions of things where the effort has been made to compile without google libs, but that still ask for device ID. For example, their version f the google sky map app, they go to the trouble to compile with certain libraries replaced, but they leave in the part where it asks for the device ID, etc. It is a totally passive app with no legit use at all for device ID. No warnings.
I've just done a search in F-Droid for 'git' and looked through all the results. I found the following:
- Github, the "official Github Android App" has a red warning that says "This app promotes non-free network services."
- OctoDroid, described as a "GitHub Client" (not a "git client," a "GitHub client") which says that it "supports all the basic github.com features" does NOT have a red warning.
Having never used either app I don't know how fair F-droid's choice to display the warning in one case but not the other actually was, but it at least seems plausible to me that the "official" app would be more likely to "promote" the service than other apps.
As for Sky Map, if the program is indeed using the Device Id for some nefarious purpose, I'd expect a red warning saying "this app tracks and reports your activity" (or whatever message was appropriate). In the absence of such a message, I would assume that either the app isn't actually doing anything (and the F-droid people think it's sufficient to let the Android permissions dialog handle informing the user of a permission that doesn't matter) or the lack of warning is an oversight on F-droid's part (I mean, clearly, if F-droid has an tracking anti-feature, failing to mark an app that does tracking with it is certainly a bug).
I would also say that even if we don't *know* that the app is doing something nefarious, the existence of unnecessary permissions itself merits a red warning message (or at least a yellow caution message), and would like to see such a policy/feature implemented. However, I don't think the lack of such a feature constitutes "false claims" on the F-Droid maintainers' part.
The bottom line is that if your allegations about F-droid are true, then you're justified in being upset, but I'm not sure those issues deserve to be ascribed to malice when there's still enough reasonable doubt (IMO) to ascribe them to accident.