We’ve implemented a new “Report this Snippet” link that’s located beneath each code snippet box. Clicking on this link will notify us if you think the snippet is spam. There’s also a built in threshold to take the snippet offline if enough unique users click the link.

We’ll see how this system works and will adjust it accordingly. As always, thank you for using Snipplr!

First, thank you for your feedback on the new design, both positive and negative. It’s hard to be all things to all people, but we’re going to give it our best shot. Trey is busy working on an alternate style that is more minimalistic, smaller, and has more room to view code. We’d love to give you more control over your preferred interface. In the meantime, I’ve made some small changes to the interface - like making the code editing block more suitable for code on both the new and edit snippet pages.

Aside from the design, I’ve been working to make some system changes:

• Search. Searching now works more like how you would expect. I’ve also added an advanced search, which allows you to search source code and filter by language.
• Languages. I added some new languages that were requested and also upgraded GeSHI (for syntax highlighting) to the latest version.
• Spam. I replaced the math captcha for new user registration with reCAPTCHA and haven’t seen any spam bots try to create an account since.
• Details. There are lots more minor changes and fixes around the site on both the front and back end. As always, please contact us with any bugs or suggestions you have.

We have lots of more ideas and things in the works, so keep checking back here for the latest news.

The website has come a long way since Tyler Hall first built it. In the beginning, Snipplr was called Caffeine and it looked like a bare bones Web application from 37 Signals.

Since then, it’s come a long way. The new website has several new features, including the ability to expand the code view. The search has also been completely overhauled and works much better than the last version of the website.

We have some very big features that we’re planning to introduce later this year. Subscribe to our blog and also our Twitter account to keep up with the latest Snipplr news, including beta announcements.

Thanks to everyone who has contributed code snippets to Snipplr over the years. You are what makes Snipplr so great.

Read more about (and download!) the Gedit plugin here.

Many thanks to Francisco and all the other plugin developers!

Now that the move is behind us, we’ll be focused on a new development. We expect to launch our new design in the next few weeks, and after that we’ll be focused on some cool new features for Snipplr.

I received an email from DreamHost Support notifying me that they had disabled the Snipplr database because they had identified some slow queries running on it. Instead of contacting me directly to resolve the issue they simply turned off the database. No warning, no email, no phone call, nothing. Snipplr simply went down.

I’m working as fast as I can to get Snipplr moved to a new web host who won’t go to such extreme measures without giving advance warning. What DreamHost did is reprehensible, lazy, and the sure sign of a shitty web host.

In the meantime, I’ve gotten Snipplr back up and running until I can move it. Will the site go down again if DreamHost decides to disable it? Probably. So please bear with us as we work past this latest hurdle. I hope you never have to deal with a situation like this on your own website.

Tyler

PS - The site may go down, but none of your snippets will be lost.

• Preference page to insert and validate your Snipplr API-Key
• Post a snippet from the eclipse editor to snipplr.com
• Search your snippets and favorites at snipplr.com
• Open your snippets and favorites
• Drag and Drop a snippet from the search result
• Ctrl+C to copy a snippet from the search result into the clipboard
• Deleting a snippet at snipplr

Thanks to Oliver for his great work. You can download snipplr4e here.

This post from Daniel Jalkut’s blog was the first I had heard of other websites (like every WordPress blog) having similar issues. Turns out, a bug in PHP 5.2.2 makes $HTTP_ RAW_ POST_DATA not set by default. And since the XML-RPC library I rely on uses that variable, kablooey! Goodbye API!

In any case, it’s fixed now.

Previously, it would pop-up a box for you to type in some keywords. Then it would search Snipplr and show you a list of matching snippets you could insert into your document. That worked pretty well, but you had to be online for it to communicate with Snipplr. You’d lose access to your snippets if you weren’t connected to the net.

This new version syncs your snippets and favorites directly into TextMate’s bundle menu - giving you offline access to all your code stored in Snipplr. If you don’t mind me saying so, this rocks. Here’s a screen shot:

Keep in mind that this bundle is still in development. Everything is working fine for me, but your mileage may vary. You can download the new bundle here. Note: You must be logged in to Snipplr for the download to work. Also, make sure you uninstall the old bundle from TextMate before installing this one.

For the nerds in the audience…

This bundle was a lot of fun to write because it forced me to dig into TextMate’s bundle format. I’ve written some advanced bundles before (at least I consider them to be . . . at work we use a bundle that lets us stage and deploy our clients’ websites on remote servers via TextMate) but nothing like this.

When you download the bundle from Snipplr, PHP generates a custom bundle on the fly based on the snippets in your account. It creates all the .tmSnippet and .tmCommand files as well as the OS X property listings. It’s by no means brain surgery, but it definitely took some tinkering to make it come out right.

The bundle also includes a command to refresh itself. It does this by downloading a new bundle in the background and rsync’ing it with the pristine copy stored in TextMate. I consider this a cheap hack - I’m hoping TextMate 2.0 provides an official API for bundles to self-update. (Ideally, each bundle .plist would contain a URL and version number that TextMate could use to search for updates and, if available, update the bundle à la Firefox extensions. You there, Allan? :)) It tells TextMate to update its bundle listing using a quick AppleScript command (osascript -e 'tell app "TextMate" to reload bundles').

There’s probably a better way to do all this - I need to search the TextMate mailing list.

Next up, I’m going to try and register the update command with launchd so the bundle can stay in sync automatically - preferably when TextMate isn’t active.

I’d appreciate any feedback from the Snipplr community on this bundle. Bugs and feature requests are always welcome.

Also, if anyone is interested in beta testing the new version of Snipplr we’re working on, let me know.