-
InfluxDB
Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
Someone asked this question in a ticket in the F-Droid client repo.
The app manager in question (which btw is one of the best ones I have ever come across) lists individual tracker components on this particular page. If one clicks on the red button, it shows "org.acra.dialogue.CrasHreportDialogue" as well as "org.acra.sender.SenderService" as the 'trackers'. On other pages as well as in the scanner, it lists 'ACRA' as the single tracker with '136 classes' and a link to Exodus from which the tracker data is sourced.
Why AM considers ACRA as tracker (and not logger like AppWarden does)? See the README page: https://github.com/ACRA/acra. It explicitly states that ACRA can be used to send not only the crash reports but also other information directly from the app if the app has the INTERNET permission. This is what makes it a tracker because it can send information to the server without any user intervention or consent. F-Droid doesn’t use this feature (and probably many apps don’t) but that’s left for the user to find out. But if people didn’t know about the existence of this tracker, they would never ask F-Droid for an explanation. A tracker is a tracker regardless of who use them. If AM used some form of whitelists, that would raise the question of authoritarianism.