Hacker News Reader

Comment by zihotki | Hacker News Reader

I had a brief look at the tool. It's a pity but it's not a tool, it's a service with unclear ToS. The CLI tool is a wrapper which sends openapi definition to the service. That's a big NO.

In general I get a feeling that it's just a small feature who wants to become a paid product.

View on HN

Co-founder of Zuplo here - we actually created the service to help people get their docs into better shape (we use your OpenAPI to power the dev portal in Zuplo). We find that if folks have a high ratemyopenapi score their docs tend to be pretty good. We have no plans to charge for this service.

Thanks for the feedback, appreciate you taking the time to try it out and comment.

Most OpenAPI specs I work with are effectively under NDA, so submitting them to an external service is not an option, paid or not. There doesn’t seem to be any good reason why this couldn’t be a standalone tool.

I love such low value many words responses! If you have no plans to charge for the service but still provide it as a service instead of making it an offline tool, then it's even bigger NO.

We, some users, find that when there is no price for the service then we're paying with our data. It may be sold or used in unintended ways. It should be mentioned somewhere in ToS what you're going to do with the data, right? Oh wait, there is no ToS...

I'm sorry, but this comment is asinine.

1. Its fine to implement this as a web service. It makes it much more flexible to implement in multiple locations. (CLI, website, other backend)

2. Its something someone spent time making, that could help you, that theyre giving away at no cost. Future aside thats a nice gesture that should be celebrated.

3. OpenAPI specs on average are not precious, not very valuable to other parties.

4. If yours is, and contains super secret proprietary information you can't afford to leak, thats ok, you do not have to use this.

> 1. Its fine to implement this as a web service. It makes it much more flexible to implement in multiple locations. (CLI, website, other backend)

Rating an API specification using a set of rules based on opensource linter is a trivial task which can be easily implemented in such a way so it can be used both offline and online. Relying on a service adds additional latency.

> 2. Its something someone spent time making, that could help you, that theyre giving away at no cost. Future aside thats a nice gesture that should be celebrated.

Feedback was asked, feedback was received. Running the service which does server side processing costs money. There is no free lunch. They are providing the CLI so why not implement it directly there to save the costs?

> 3. OpenAPI specs on average are not precious, not very valuable to other parties. >4. If yours is, and contains super secret proprietary information you can't afford to leak, thats ok, you do not have to use this.

That's why there should be Terms of Service - they need to say how they are going to use/process my data on their servers. I know how much value my data has and I want to know what I am signing for.

Reply on news.ycombinator.com