Hacker News Reader

Comment by War_Machine | Hacker News Reader

After Power's IP addresses were blocked by Facebook, couldn't Power use the user as proxy to access Facebook instead? In other words, have the user (through some Power provided tool I suppose) access Facebook and feed Power the information it wants to send.

View on HN

The problem is that this probably violates Facebook's TOS. Enabling a TOS violation for users as a business model would make for a pretty easy tortious interference lawsuit by Facebook against Power.

It seems like it would be pretty hard to draft TOS that prohibit the user from running a program on their own machine that requests, processes, and outputs data on the user's behalf without banning more traditional user agents like web browsers and proxies.

If I remember correctly, Facebook prohibits users from supplying third parties with their Facebook Login credentials for the purpose of that third party logging in on their behalf.

Edit: From Section 4(8) of the Facebook TOS [1]:

"You will not share your password (or in the case of developers, your secret key), let anyone else access your account, or do anything else that might jeopardize the security of your account."

[1] https://www.facebook.com/legal/terms

How does that apply to the suggested workaround of the user running the necessary content scraping on their own machine and pushing the results to Power?

To be specific, we mean like a chrome plugin or something at that level, right?

Such a tool wouldn't need to provide the FB credentials to the third party, only in the application, or as-mentioned a browser itself, with an extension.

Usually the trick is to add in something like "...at Facebook's discretion...".

What would be at Facebook's discretion? Are you suggesting that their TOS could dictate what web browsers you're allowed to use to access Facebook, or whether you're allowed to store and make other personal use of the information they send you?

It's impossible for something like Facebook to use a whitelist model for determining what you use to interact with their service, and they can't retroactively add things to their blacklist. They usually have to rely on generic rules about causing harm to the service, but then it's no longer a pure whim.

No, I'm suggesting that the TOS could dictate that whether you are allowed to do it or not is entirely at Facebook's discretion, and they could choose to say that it isn't okay.

A lot of software licenses have a clause that basically allows the licensor to revoke the license on a whim.

Facebook can always give themselves the option to unilaterally decide to no longer serve you going forward. But that's not the same as Facebook being able to declare that arbitrary behavior is retroactively in violation of an open-ended clause of their TOS and therefore grounds for lawsuits and CFAA prosecution.

You could probably do so with a browser extension.

I made a quick hack to demonstrate this a few years ago. I didn't maintain it and couldn't find another developer to take over, so it doesn't work anymore. http://devesh.github.io/SuperShareBox/

Reply on news.ycombinator.com