![]() Or maybe it really shouldn’t matter where the code runs provided it respects boundaries, or better, those boundaries of intentionality and access are technically guaranteed inviolate.Ĭreating a novel on-device scanning mechanism and claiming that is somehow more privacy is a lie, and therefore shady. Perhaps the line is too blurred between client and server, thanks to emergence of concepts like node.js (“run same code on client or server”) that make this sound like a feature. At least, they profess surprise and drop these SDKs when the user behavior harvesting is pointed out to them.įor whatever reason, everyone’s OK with this. If you study the cesspool of user tracking and other privacy violations on iOS devices, it’s mostly developers using the same client-side SDKs across their apps, and users none the wiser. It’s the client SDK operating the same algo on an upload event image at the client end of the upload API as it would run at the server end, just not having to decrypt it to do it.īut to your theme - there’s no clear bright line in client SDKs.ĭevs do not think of these or handle these as if they belong to the user. Framing as “on device scanning” is contrary to facts.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |