I suggest returning 404 Not Found instead of 422 Unprocessable Entity on failed GETs: <a href="https://jsonbin.io/b/2342342" rel="nofollow">https://jsonbin.io/b/2342342</a> as well as Content-Type: application/json instead of current text/html.<p>"Entity" in "Unprocessable Entity" refers to request body and for GETs there is no request body: <a href="http://www.restpatterns.org/HTTP_Status_Codes/422_-_Unprocessable_Entity" rel="nofollow">http://www.restpatterns.org/HTTP_Status_Codes/422_-_Unproces...</a>
Really sleek and clean, love the design. A simple but useful product, nice job :)<p>The link to your Twitter on the about page is broken by the way, it should have a protocol.
Wait. So this just stores arbitrary byte blobs right. What exactly is the JSON bit about? Can I use jq syntax to query and transform whatever JSON is stored?
I made the exact same thing couple of years back, but shut it down because I couldn't think of sustainably maintaining such a "free" service.<p>I have a lot of ideas like this, but I am super confused on the sustainability part. What ways are there to sustainably maintain such services?
Cool. I really like the UI. Response times are slow-er than I would have originally thunk, but I'm sure that's a side effect of the HN hug.<p>Are you saving these "bins" as files, and then serving them? Or are you putting them into a database? Mostly curious. :)
For a similar service which is entirely encrypted, consider: <a href="https://safepaste.org/" rel="nofollow">https://safepaste.org/</a>
Nice. This is basically my usual "How does this language/framework work?" test project.<p>I've still never built a twitter clone...