Izzy

@alalamav my repo is fed by the APKs you provide here. If you tag a new release and attach an APK to it, that should show up in my repo...

Version 1.3.0 added a bunch of trackers (e.g. Crashlytics, Firebase Analytics). I hope this was an accident, and not something intended – because your app is supposed to be dealing...

@fortuna thanks a lot! I'm not a dev and thus don't have the "deep insights" – but if you just need crash reporting, maybe taking a look at [ACRA](https://github.com/acra/acra), which...

According to my library scanner, it seems to have earned the `Tracking` AntiFeature as well (i.e. at least with the default config, doesn't ask the users' consent before uploading things)....

Any news, @fortuna?

@fortuna thanks for the pointer! Then F-Droid could stick to the stable builds. I see no `build.gradle`, so I cannot verify :wink:

PS: it's also pretty hard to find the stable builds on your releases tab, with all those daily development builds published by the bot. Maybe you could link to the...

Thanks to the new tag names, picking only stable ones (`android-v%v`) is now easy. I just re-enabled auto-updates for my repo after verifying the last version (1.2.13), which my scanner...

Thanks Christoph! I cannot tell either. As described, there's no action needed for "Waterfox G4" – it's just "Waterfox Classic" that is affected. I could compare the UserAgents if that...

@ChristophWurst while I wait for answers from caniuse: I've tried making sense of the linked `browserlist.config.js` using the project's readme and would say Waterfox Classic is not covered, while G4...