4 ms·
> tricking users into providing access to their data on Facebook by installing apps > same scheme with chrome extensions These are very different things. One
by Reelin 6y ago
> tricking users into providing access to their data on Facebook by installing apps
> same scheme with chrome extensions
These are very different things. One took place via Facebook's own platform while the other did not.
If their own platform officially allowed for third parties to collect user data, it is reasonable to complain about that being the case.
If their own platform explicitly forbid collecting user data in such a manner but they stood by and let it happen anyway, it seems reasonable to object to that.
I don't see how it's any of their business what a legitimate user does with their own data after it's been sent to them (ie the page loads). I suppose they could add a provision to their ToS disallowing such use; if a violation were discovered they could ban the user in question. But a third party almost certainly never agreed to such a ToS. It's not the existence of the program that violates the contract but rather a specific instance of its usage.
- anfilt 6y agoI agree. However, I suspect facebook is gonna try and claim some sort of tortious interference between the TOS the user agreed too.
- shajznnckfke 6y agoI think the dichotomy you’re pointing will affect Facebook’s legal tactics, but has no bearing on the privacy risk they need to defend against. In both cases, Facebook has an API that served data for some authorized client for a specific purpose (users browsing Facebook, users taking a quiz), but really there’s some entity pulling the strings and misusing the client to amass user data (collecting data associated with users who took the quiz, collecting data associated with users browsing on Facebook).