johns

47 ms·

481.
Introducing Runscope Radar: Automated API Testing and Monitoring(blog.runscope.com)
1 points by johns 13y ago|0 comments
482.
HTTP/RESTful API troubleshooting tools(blog.developer.bazaarvoice.com)
1 points by johns 13y ago|0 comments
483.
Why the attack on Buffer was a wake-up call for the web(blog.programmableweb.com)
7 points by johns 13y ago|0 comments
484.
Low-latency notification of Dropbox file changes(dropbox.com)
1 points by johns 13y ago|0 comments
485.
by johns 13y ago
http://www.kickofflabs.com/
486.
by johns 13y ago
I love this service. I've been beta testing it for a few weeks and Andrey has figured out just the right metrics to include in a very succinct manor. It's one of my favorite emails every week.
487.
Announcing the Python Datastore SDK and HTTP API documentation(dropbox.com)
3 points by johns 13y ago|0 comments
488.
by johns 13y ago
Previous discussions/submissions: https://www.hnsearch.com/search#request/submissions&q=vinays...
489.
Open Source Currency(lukasa.co.uk)
1 points by johns 13y ago|0 comments
490.
Serf(serfdom.io)
15 points by johns 13y ago|0 comments
491.
WhiteHat Aviator - The most secure browser online(whitehatsec.com)
3 points by johns 13y ago|1 comments
492.
by johns 13y ago
We write ours manually in markdown. I have yet to find a description format worth investing in that saves us enough time and is more expressive than that.
493.
by johns 13y ago
Why is there a length limit?
494.
TeleHash: JSON + UDP + DHT = Freedom(telehash.org)
7 points by johns 13y ago|0 comments
495.
Find Just the API Calls You're Looking For with Runscope's New Live Search(blog.runscope.com)
2 points by johns 13y ago|0 comments
496.
Runnable Aims To Be The YouTube Of Code(forbes.com)
2 points by johns 13y ago|0 comments
497.
Why Stashboard and Pingdom Weren't Enough: The Evolution of a Status Page(blog.balancedpayments.com)
1 points by johns 13y ago|0 comments
498.
Common OAuth Security Mistakes and Threat Mitigations(layer7tech.com)
1 points by johns 13y ago|0 comments
499.
by johns 13y ago
Great post, thanks for taking the time to write it up. I'm curious how the discussions got started with Eventbrite. Were you discussing another kind of partnership first? How close were your existing contacts?
500.
Editing JSON(tbray.org)
1 points by johns 13y ago|0 comments
501.
by johns 13y ago
There are so many scenarios for debugging APIs that don't fall into the "I control both ends, so I should be able to see everything." camp. SDKs, poorly implemented or documented APIs controlled by a 3rd party (frequently eve
502.
The Path of Opportunity(carpeaqua.com)
1 points by johns 13y ago|0 comments
503.
by johns 13y ago
We've (Runscope) tried to make debugging better than what you can do with a simple post catcher like requestb.in. The nice thing about our forwarding setup is that if a webhook fails on your server you have a log of that and can retry
504.
Why We Open Sourced Our Documentation(blog.sendgrid.com)
2 points by johns 13y ago|2 comments
505.
Dropbox opening my docs?(wncinfosec.com)
410 points by johns 13y ago|125 comments
506.
Equipping API-focused OSS Projects with Free API Debugging and Testing Tools(blog.runscope.com)
1 points by johns 13y ago|0 comments
507.
Equipping API-focused OSS Projects with Free API Debugging and Testing Tools(blog.runscope.com)
1 points by johns 13y ago|0 comments
508.
by johns 13y ago
It's not the only reason. PUT is the only way to do retryable creates since it's idempotent. Leaving it out is a huge omission.
509.
by johns 13y ago
Try flask-restful
510.
by johns 13y ago
You can send a webhook to localhost, just in a roundabout way using one of the local tunneling solutions: http://john-sheehan.com/blog/a-survey-of-the-localhost-proxy... Great points though.

More ›