3 ms·
Yeah, this. I really can't fault Zoom here. They used an existing tool provided by a company that is, allegedly, reputable. Though, thinking about it more per
by remarkEon 7y ago
Yeah, this.
I really can't fault Zoom here. They used an existing tool provided by a company that is, allegedly, reputable.
Though, thinking about it more perhaps Zoom should get some more scrutiny here because this isn't the first time Facebook has said eff it to user privacy. Distrust of Facebook should be the default.
- xiphias2 7y agoActually Apple and Google should not allow this in their app store policy. An 3rd party SDK sending data if it’s not needed should be a BIG no-no....I expect at least Apple to require this. There are probably thousands of other apps that have the same problem.
- remarkEon 7y agoGreat point. If Apple or Google enforced what you're saying in their app stores this problem would disappear overnight.
- mgoblu3 7y agoWould be pretty hard to scan for, but I agree that there should be something at least outlined. Privacy policies clearly are aren’t useful enough.
- yjftsjthsd-h 7y agoHard in the general case, but I'll bet it's trivial to scan for the Facebook SDK, or any other blacklisted libraries, unless they're intentionally obfuscated.