|
|
|
|
|
by EvanAnderson
1711 days ago
|
|
The nuance of how "we put up a service ... talk to it on our terms" is enforced is what is deeply concerning to me. Is that up to Facebook to use technical means to enforce their terms or is the force of law behind them? Where is that line drawn? If I modify the DOM with an extension to hide content I don't like am I running afoul of the law? How about using Lynx instead of Chrome? What constitutes "talking to" a service? Is it data I send to that server, or is it how my computer processes the data I receive and how I interact with it? Different people are going to have wildly different opinions, and some of them are very troubling to me. Committing fraud is one thing, but simply using a service without exceeding your authority in a way the service provider doesn't prefer seems like something the service provider should handle without the force of law behind them. |
|
There are limits to both tools, and legislatures can enact new restrictions in response to public demand. But none of that is in play in this story.
If the argument upthread was "we should demand laws that prevent Facebook from locking out extensions to their platform", I wouldn't have a rebuttal (I might or might not support those restrictions). But the sarcastic dunk that was actually made, that it was somehow ridiculous that Facebook would have some say over the terms of how their platform was used, was weird and worth commenting on. It's not only not ridiculous, but actually the world as it exists today.