Highsight@lemmy.worldtoPrivacy@lemmy.ml•De-Google Your Life - Part 1 - YouTube LTTEnglish
51·
5 months agoI used AI to summarize the different Google products and services listed in the video along with their suggested alternatives and timestamps. AI is pretty cool sometimes.
Google Product/Service | Recommended Alternatives | Timestamp |
---|---|---|
Google Chrome | Firefox, Brave, Arc, Ungoogled Chromium | 94-326 |
Google Search | Startpage, Ecosia, DuckDuckGo, Brave Search, Kagi | 328-493 |
Gmail | Tutanota, ProtonMail | 534-671 |
Google Photos | Ente, Stingle | 674-794 |
Google DNS | Quad9, NextDNS, Cloudflare | 827-1074 |
Google Analytics | Not covered in this video, to be discussed in part 2 | N/A |
Google Maps | To be covered in part 2 | N/A |
Google Ad Services | To be covered in part 2 | N/A |
Google Drive | To be covered in part 2 | N/A |
YouTube | To be covered in part 2 | N/A |
When I read this this morning, I had concerns, but then I did some research. The SDKs source is fully available for all to look at and compile. The main issue that people bring up is the license that states:
3.3 You may not use this SDK to develop applications for use with software other than Bitwarden (including non-compatible implementations of Bitwarden) or to develop another SDK.
This part seems to be what most people take issue with, as it makes the sdk no longer modifiable, yet a requirement of the core source itself. The head of BitWarden has come out and stated the SDK being required to compile BitWarden was a mistake, however, and if this proves to be true (which I have no reason to doubt) then I see no reason why any of this is an issue.
From a security standpoint, since the SDK is source available, it can be audited by anyone still (and compiled) so personally, I’m fine with this.