cool service, I hope it remains up so we can depend on it.
Currently you can accomplish the same thing using Yahoo's YQL, if you'd rather trust a big company to stay up. Here's an example: http://y.ahoo.it/b7rnO
I'm using it on my website to parse my project's history.json file: http://ruhoh.com/latest-updates/, check the source on that to see how it works.
Be warned that YQL transforms arrays containing one element into strings =/, terrible I know but it works.
that's kind of the point. CORS just tells the browser to block the response, so this proxies the request and simply changes the headers to avoid that restriction.
I tried this once with a proxy script and it eventually lead to inconsistencies. I've settled on using an apache reverse proxy when I need to do cross-domain json posts (typically for dev work).Just put this in your vhost config
One things these services often lack is the ability to change the user agent before making the request. For awhile, if one wanted to make use of Pinterest's API, they would just need to change the user agent to mimic the iPhone app. (Recently Pinterest has made using the API more difficult so such a technique is no longer sufficient.)
I hope you meant, "If you want to pass any secure information that would require HTTPS you can't use it.". POST does not make anything "more secure". (And JSONP should work cross site with HTTPS anyway)
Of course if you want to do multipart submissions or anything too long to fit in a url, you'll be needing POST anyway.
As a general note, GET and POST requests expose their parameters with equal visibility. It's just that the browser makes it more obvious what your GET parameters are
Well, based on the comments it sounds like you've exposed a need. People want it to be stable and don't seem comfortable with the idea of it being your hobby. Make them pay for it before someone else decides to.
Maybe you could make a signup with Stripe or Paypal or something so that people could pay $5 or $10 per month to use it.. that way you would have enough money to at least pay for the server(s) and a reason to maintain it and come up with a way for it to automatically scale.
I mean do you have something like a load balancer or proxy or something that will allow it to scale horizontally in case a few people really take advantage or it becomes popular?
It seems like leaving it totally free would probably end up with it just not being worthwhile to maintain.. but if there is a little money going in and at least one well-known service starts using it then I would totally consider using it.
It was quick for me to make and it doesn't really require maintenance - feel free to donate to the EFF in honor of the project.
In terms of scalability, the app is doing very little processing so it's really just a matter of how many concurrent connections Node can handle in & out, but I've read it's capable of hundreds of thousands or more. Let me know if you are seeing high latency.
1a) feel free to download the source and host yourself or write three lines of PHP
1b) not if you use the AJAX version - any response will come in as a string, so just don't eval()
2) the limit is really how many concurrent connections Node can handle, and the answer is "many"
3) It's at least useful for small mashup sites where you can throw up an HTML file with some JS - no server code needed
no commercial version planned - I threw it up because it was something I was going to use (to build hackerhours.org), and figured it would be useful to others as well
I think number 3 is the biggest point here, i'm all for solving developer pain points but would be interested to see if there really is a market for this?
While I think it is a cool service if a person is just hacking around, it is not something I would use with any revenue generating project.