Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

> The main issue I have with this is I have had the "pleasure" of working with pretty stupid people implementing clients on my API. They easily get POST and GET requests mixed up, HTTP and HTTPS, whether or not the request should be authenticated. I don't want to add something else to confuse them even more...

So you are willing to do the work of those other devs for them, and cripple your own API in the process?



If he wants to expand his user base, yes he is. The essence of a business is doing other people's work for them and then charging them. If doing other people's work for them also brings you money, well, you'd better have a very good reason not to.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: