Exciting news! Trackers being built into the Bitwarden F-Droid app for who knows how long have been removed
https://github.com/bitwarden/mobile/commit/f343a2cdbb5895fb518ed963b30c0d9822db2c74
Previously two trackers were introduced: Google Firebase and Microsoft AppCrashes
- Why were there trackers initially? - It’s normal to track crashes and utilization to make software better, I don’t think they tracked to sell data for advertising in bitwarden case - And Google Firebase is what non-degoogled Android uses for notifications - Even more, I think it’s basically the only way. Lichess app got removed from vanilla F-Droid because of that. 
 
 
- It was actually a mistake. They were removed years ago specifically for the fdroid builds, but were reintroduced at some point on accident. Annoying mistake for sure 
 
- That’s great news indeed! - Now if they could consider implementing some sort of sorting and more advanced filtering that would be a huge plus, along with dupe control 
- If the app is hosted at its own F-Droid repository, devs can add whatever they want. I wouldn’t be surprised if that build is the exact same one as the Play Store one. - Nevertheless, good step for users! I wonder how devs will get crash reports and such stuff now, though… 
- Removed by mod - What’s the advantage over XC - Theres so many - DX is for smartphones, XC isn’t - Oh, I’ve been using KeepassDroid. I like that it doesn’t support internet access 
 
 
 
- Just checked F-Droid and nothing popped up. Is it coming this way? Great if it does! - Do you have their self-hosted fdroid repository installed? - Having a repo doesn’t mean its on F-droid. I mean it does but using there repo forfeits the F-droid protections 
 
 
- How? For 2023.10.0 appmanager’s scanner does not show any of those, and it is usually very through (even right now it has identified 54 programming libraries) 
- My F-Droid download keeps failing the hash check. - It does that sometimes. Try clearing the download are starting over 
 









