logicuce

The team is great and clearly shows in the product they have built. However, at current pricing I would rate them expensive. Other enterprise offerings which go by per user pricing, like Google Apps, are much affordable for instance.

I hope with time their economics work out and they could offer more affordable plans.

Its great Govt is finally understanding the need for 'Accessible' data and solutions.

Hopefully this will bring in more transparency and efficiency in otherwise slow and opaque system.

Assuming you take care of the essentials like documentation and code samples, following will make your API shine.

* Explanatory Error Responses: Tell what was wrong in a problematic request and, potentially, how to fix the request

* Introspection end points: Which can tell you more about the request (headers/body) and credentials (rate limits, app id, etc) observed by the server. Is very handy in case of debugging.

* API should be able to tell properly when its unavailable. Ideally by returning proper HTTP 503 response.

Agreed. Square would be in best position to take that call and he might be very good at his work there. Hence my comment above was a question rather than a suggestion.

That said, this article doesn't seem to be a tongue in cheek thing. He is the lead security researcher at a payment processing company. A critical position I believe.

I am not sure if such a person can afford to have written that article where people who are not security researcher can easily find conceptual flaws.

I am sure there is lots of interest in such a project but the project website doesn't talk (at all) about the capabilities of the system. Hence such a dull response from the community.

At best it provides sketchy details about how to deploy it but things end there. You are going to have touch time selling it to intended audience this way.

And may be Square should let him go as well?

Bitbucket's no limit on number of repos is what made us take the final call as well. You don't want to be restricted on that when you strive hard to have a more organized code base.

I first tried bitbucket for my personal projects and then moved my work repos to it as well.

Bitbucket charges per user and not per repo (the github model) which scales well while keeping cost in control.

One's proficiency in a language is more important than using a newly learnt shiny thing out there. Given the people who get in the YC batches are deemed to be smarter of us, I would not expect them to be judgmental about these things.

I think you should fight this problem with larger availability. Create a website and put it online for people to download.

Moreover, if you can make it a webapp, even better where you can charge per ID card generated.

I have seen people having this problem and they paid decent money for the ID card generation. You are just targeting wrong audience. Don't talk to people who generate the cards, appeal to people who want the cards.