Snipt.org and Accompanying WordPress Plugin…

The Setup: Which “Snipt” Are We Talking About?

Remember when Snipt was discussed here a few days ago?

To add more confusion to the snippet remote storage controversy, there’s another site (which some of you have already mentioned) called Snipt.org, which does not appear to be the same as Snipt.net.

Although the two sites are not the same, they offer code/content fragment (snippet) storage. But Snipt.org posits that Twitter distribution is the way to go, with your snippets… and they offer a code embedding feature to pass your code around to other sites. There’s even a tumblelog (cutely named org.snipt.SniptBlog, like a Java package) that offers advice on styling your embedded code display to your audience, and other news about Snipt.org…

The Premise: What About That Plugin?

Yesterday, a guy named Dan Wasyluk submitted Version 1.0 of a new WordPress plugin that allows Snipt.org snippets to be included/embedded into WordPress blogs. Sure, you can roll your own integration with the code embedding feature, but now that there’s a plugin available, why bother, right?

Now, the term “embed” may be a bit misleading: it is presumably not intended to be a code include. Instead, it is a way to display the code stored on the Snipt.org service elsewhere. In the case of the plugin, the target location would be a blog running the plugin.

The Action: What’s Next?

Having more ways to get access to code snippets, and to provide different ways of apportioning code as “snippets”, is certainly an entertaining endeavor. It opens up quite a few interesting possibilities.

More on this a bit later…

Tagged as: open source, Snipt, Snipt.net, Snipt.org