The following was just posted on api.snipt.net.
A call for help
Houston, we have a problem. We've hit the limit as far as time resources are concerned. We're looking to the development community to help us build a stable, robust, and open-source RESTful API for Snipt.
A little background noise
Snipt is a side project quickly gaining momentum among developers. In order to keep up with the community's demands, and foster Snipt's growth, we need to provide an open, public API.
What we need
The aim of this call for help is to organize a group of developers interested in helping build the official Snipt API. While Snipt itself will remain closed-source, the API will be open-sourced on GitHub.
What's been done so far
We've taken a long, hard look at what we want for an API. We have a very clear high-level vision of what needs to be done, but lack the resources needed to pull it off in a timely manner. We've made public some conversation notes we put together.
Why it matters
It matters because, as users of Snipt, we want to see it succeed in platforms and environments that are not penetrable by the current website-only technology (eg. desktop apps, text editors, CLIs, etc).
How to help
If you're interested in helping, or have any questions or comments, contact Nick Sergeant.