27 comments

[ 4.0 ms ] story [ 54.4 ms ] thread
Seems simple and useful like jsfiddle. I will really use this in my app.
Seems like it might be handy for testing. Certainly good to stay way from it for production apps though.
Neat and simple, but that's exactly the kind of things that makes me go "too bad it's not open sourced, I could use that"
To be honest, the value resides more in the idea and the fact that it's already online than in the code.

A basic implementation of this service would take less than 100 lines in any language commonly used on the web.

Of course. It's just that it's easier and quicker to use something that someone has already developed, than recreate the 100-lines wheel each time.
Which is why I'm confused as to why you want an open-source version? Just use this one.
Anyone can PUT and replace your data.
Maybe ozh wants to host the service on their own server? Or they've found a bug they want to fix?
Neat, but it would be neater if this were open source and running on https.
Working on getting cert today ;). Thanks for the feedback.
For testing purposes, wouldn't using Dropbox suffice as well? It gives a quick way to update the JSON and see changes occur near live in app?
Yep, I've done the same in the past.
I can't see the use case of this. If it was editable after saving then that would make sense, but this is just static. And being static, you're better off just bundling it with the app. Unless I'm missing something?

Nice presentation though, the site looks nice.

EDIT: I see you can create and update through the HTTP API, which makes it much more useful.

Except everyone can update it if they know your identifier.
Could be used for notepad API or something public. That said, it seems that services like Parse and Firebox seem more robust and also have faster response times.
I built http://jsonblob.com for this purpose. It has an HTTP API as well as we nice GUI interface to edit your JSON. It's open sourced and really just a thin webapp on top of mongo, so it's easy to run your own.
A JSON literal is also valid JSON. Therefore 4, "test" and true should be saveable without a object wrapper
To expand on that: only since RFC 7158, earlier versions required the root to be an array or object.

So if you're generating json, it's advisable to wrap it so that parsers written according to the older specs won't choke on it.

However, when parsing, like this, you want to try and accept values.

Could you do this for an excel document (database)?

It would be cool to be able to drag and drop an excel document into here and call it with a url.

Why not use https://www.firebase.com? Seems more reliable (Privacy Policy, ToS, SLA) and easier to start using, and it has a free tier if you need something quick for development.