Hacker News Reader

Comment by josephcsible | Hacker News Reader

The point is it's not fair that Terms of Service can impose that restriction. Just like it wasn't fair when you were only allowed to use phones that you rented from your phone company.

View on HN

Why isn't it fair? They run the service. What gives other people the right to tell them how to run it? If you don't like their terms, there are about 100 alternative projects you can use.

There are pretty clear, practical reasons you might want to control the client of a commercial network service.

What part of your argument wasn't true of the phone company too?

The phone company is the sole-source provider and you couldn't opt for another platform. The more relevant analogy is soda fountains in a restaurant - the provider chose Coke, but I want Pepsi. (My OSS founder wanted Slack, I want discord.)

If Slack isn't the sole-source provider, then neither was the phone company, since you could also communicate by sending letters.

That's a different medium, although I understand your point: Slack is the sole source provider of communicating on the Slack network. Personally, I don't think this is a problem or should be fixed because of how I see the tradeoffs and side effects. Similarly, I want Apple to run their own app store and not allow sideloading because I prefer the set of tradeoffs that come with that, versus the other reality.

Phone companies are different in that they were monopolies with special legal status. Slack, on the other hand, is just one of many private companies offering roughly equivalent services.

You can still argue your case, of course, but phone companies are a bad analogy here.

There are reasons, but it's also not smart. Organizations that pay for Slack pay for the service, not the shitty client.

You want to reduce Slack Inc to an API provider. They want to be a client provider too and they own the API server. Do you see where this won't work?

The value of Slack Inc is their API, which is currently de-facto locked to their client. People would still pay for Slack if they could use alternative clients, because the client is not the value.

You can argue that their client is not as good as it could be, that you have greater skills to deliver a better product, etc. But it has value, otherwise we'd all be using curl to access the Slack API with no downsides. That's clearly not the case by far.

> But it has value, otherwise we'd all be using curl to access the Slack API with no downsides. That's clearly not the case by far.

Only because it's next-to-impossible to call the API, because of the way they lock features to their client!

Author of Ripcord. You’re wrong, and creating and using software compatible with services is fair.

i do agree it's fair, but it's also true that the service provider could argue that they are supposed to be in total control of the service, including the front-end.

It's by societal consensus that this can be made fair, and to convince people that it is fair, there needs to be a logical, indisputable argument that it's fair. Otherwise, the service providers can always just hide behind the counter-argument of being in control and TOS etc.

In the case of Discord, for example, the terms of service doesn't even mention third-party clients. Also, these services are accessible from web browsers, which are made by third parties. There are more reasons, like users being able to run whatever they want on their own computers, but just the ones above are enough.

"You may not copy, modify, create derivative works based upon, distribute, sell, lease, or sublicense any of our software or services"

This seems to make it pretty clear they don't want you to create 3rd-party clients for their service.

Ripcord isn't a derivative work, both practically and in the legal sense. It's implemented from scratch. Ripcord isn't a resell of their service or a sublicense of their service.

If I rephrase it like this, does it make it clear?

"You may not create derivative works based upon any of our services"

In the imaginary world where that's what the terms of service says, that's still fine for Ripcord -- Ripcord isn't a derivative work.

If the terms of service allow it, then it doesn't matter what it's fair or not: you're allowed to make a client for it. The discussion is moot.

I don't agree that fairness requires service providers to provide open APIs. Open APIs are better, ceteris paribus, but that's as far as it goes.

Reply on news.ycombinator.com