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.
Copy “Calling all developers! Help build the Snipt API”
(Text is selected. +C to copy.)
One thing that Pete and I have learned is that developers can't remember every scrap of syntax that crosses their keyboard.
The hundreds of programming languages out there leave little wonder as to why this is.
Now, there's a compelling way to keep those bygone commands close at hand.
Snipt is your collection of infrequently used commands or code snippets, because even Subversion gurus forget the 'svn merge' syntax sometimes.
Make your research worth it
Now you'll never again have to search the web for the CVS checkout code for grabbing a Drupal module.
Many people have the command down by heart, but most others do it much less frequently. Typically, people do a Google search for the command, read some reference materials, and probably cut & paste it from a document somewhere on the web.
Now it's a Snipt.
So how does this work?
It's simple. Sign up, and you're awarded your very own private command repository. Paste it, describe it, tag it, colorize it.
Get started now! It's free in every way.
Follow Lion Burger on Twitter for more product announcements and updates!
Copy “Announcing Snipt: long-term memory for coders, a new Django app from Lion Burger”
(Text is selected. +C to copy.)
About a week ago, I released my first Django project, Finisht.com, to the general public. Surprisingly, I've received a stunning amount of enthusiasm and excitement around the product. Along with that great response came many suggestions for feature improvements. Today, I've decided to open source the project to allow anyone download, install, and improve the app.
The code is available at http://code.google.com/p/finisht/. If you're interested in submitting patches or ideas, let me know and I'll get you on the project. Otherwise, feel free to grab the source code and play around with it.
I'd really love it if people were so inclined to give back to the project with some features. There are a few items on the feature list that I just haven't had time to get to, and I'll post those on the project soon.
Anyhow, happy coding, and go get something done!