Hacker News new | ask | show | jobs
by lelandfe 1711 days ago
> One of the reasons this extension was sent a C&D was that it was sending some data home to the author’s server

I think that this is incorrect.

The C&D included that as an example of banned things - beneath the actual list of what the extension had done wrong.

Per the wording, what they had done wrong was automation of actions, and unlicensed use of trademarks.

The letter: https://louisbarclay.notion.site/Unfollow-Everything-cease-a...

1 comments

“Accessing and/or collecting users content or information” is the first bullet point in the C&D. The Reddit install instructions even include a note to remove the phone-home code before running the plug-in.

The plug-in author also explained his data collection in his interviews. He said they collected a lot of data for study participants and less data for normal users to confirm the plug-in was “working”.

The first paragraph is the only one that includes a list of what their extension had been doing wrong. I haven't seen it typed up anywhere else, so here are the salient bits:

> Facebook has gathered evidence that your Chrome extension “Unfollow Everything for Facebook” facilitates unauthorized functionality on Facebook. Specifically, your extension automates actions on Facebook, including mass following and unfollowing of Friends, Pages, and Groups. Your extension also impermissibly makes use of Facebook’s trademarks. These activities violate Facebook’s terms.

> Facebook demands that you stop these activities immediately.

The bullet point you've pointed out lives beneath that list of issues, under a title of, "Facebook's terms prohibit, among other things." Things that Facebook's terms prohibit ≠ stuff the extension was doing.

Otherwise it would be curious indeed that Facebook isn't demanding they cease the collection of data :)

> The plug-in author also explained his data collection in his interviews

That could well be – I'm just saying that the C&D does not include it as a basis.

Is the author of the extension bound by the FB EULA? I'd guess no.