Inspired by Rob T.&#0xa0;Firefly’s transit schedule app for cameras, Roasted Vermicelli, LLC is proud to announce its entry into a new app space:

Download Video: MP4, WebM, HTML5 Video Player by VideoJS

The video is also available on YouTube for your embedding pleasure.

The Guardian published a piece I wrote on the recent Gawker attacks, Anonymous, and related topics:

This past Saturday, a group calling itself Gnosis broke into Gawker’s website, obtaining and releasing among other things a database of 1.3 million of the site’s users and their email addresses.

Though the passwords in the database were encrypted, making it impossible to read them directly, the encryption used was apparently quite weak, and many of these passwords have been exposed. More than 2000 Gawker users apparently chose the password “password”, second only in popularity to the presumably Mel Brooks-inspired “123456”. Revealing Gawker’s password database may at first seem harmless, but given the likelihood that many people use the same passwords for Gawker as for their Facebook accounts, email or even online banking, the potential for harm is real.

Read the rest on the Guardian’s site.

The Cage Against the Machine campaign aims to make John Cage’s 4′33″ the number one single in the UK this Christmas. This is a campaign which I support wholeheartedly, and I wished to participate.

However, UK digital music vendors limit sales to computers with IP addresses actually in the UK. Here is a summary of the steps I took to purchase the album anyway. (Note that the operative word here is “summary”; some degree of technical skill may be needed to follow this procedure.)

WARNING: Even though this post explains how to purchase music, not how to pirate it, it is entirely possible—maybe even likely—that following the steps described here violates some terms of service agreement or is otherwise illegal.

When I began freelancing and formed a company, I called it “Roasted Vermicelli” more-or-less at random: I had previously purchased the domain name vermicel.li, and sticking the word “roasted” in front was required to make the business name unique within New York State.

After some years of this—plus a blog tagline which promises musings on pasta but has yet to deliver any—when I cooked dinner the other day, it was time to cook using some roasted vermicelli.

For one of our projects, we’re using beanstalkd in combination with the async_observer plugin for Rails to run slow tasks in the background.

This is a nice setup. Although we’re not using all of its more advanced features, beanstalkd is a very powerful and efficient queueing system, and async_observer provides a clean integration with Rails. (On other projects, I’ve happily used delayed_job for similar purposes, but it was not suitable for this project due to its heavy dependency on a ActiveRecord and a SQL database. By contrast, async_observer’s support for ActiveRecord was quite easy to rip out.)

However, we would like to be able to queue async_observer jobs from cron or the command line. Why launch a new process with a copy of the Rails stack when there’s already a long-lived one running? So, I wrote a ruby script with minimal dependencies which can stick tasks in beanstalkd for our async_observer worker to run.

For a number of reasons, we want to convert one of ours Rails applications so that it is backed by PostgreSQL rather than MySQL. Although Rails and ActiveRecord abstract many of the differences between the two database engines, there are still some issues to be aware of and no one-size-fits-all solution to the problem. Here are some of the challenges we encountered in making the switch.

Tobis Timemachine is a very useful tool for bringing websites back to “the amateur web of 1996.”

However, there is is some overhead with the Timemachine: it requires your users to have already installed it in order to be useful, and those visitors need to be using a compatible version of Firefox. What if you want to make a 1996-era website for all your site’s visitors?

Thus, timemachine-fu, the Timemachine plugin for Rails.

As I’ve mentioned before, I’m working on a Rails project where we’ve dropped ActiveRecord in favor of a CouchDB database.

One thing I miss from ActiveRecord, though, is the ability to do migrations. While SQL migrations in their most conventional use—to modify the schema of our database—are of course not needed in schemaless CouchDB databases, there is still sometimes a need to have a block of code which runs exactly once on every installation of our codebase. For example, we might have a key in our documents which becomes so important that we want to break its values off into new documents, or vice versa, we might have a bunch of documents which should all get combined into attributes of one master document.

Cloud computing is supposedly all the rage these days: the idea is that instead of running your own infrastructure, you just outsource everything.

There are some cases where this is almost self-evidently a good idea: renting a VPS is much cheaper and more reliable than sticking a server in your home and then dealing with the noise, electricity, and bandwidth that such a thing would consume. This blog, for instance, is hosted on a VPS at Panix. On the other hand, an Amazon EC2 instance at the seemingly low price of $0.10 per hour will cost $72 if you leave it on for a whole month—more expensive than many low-end dedicated physical machines.

But the cloud, we are promised, can do more for us than just save us money: it can run our services for us. Programmers no longer need know how to do anything but program the things specific to their application: everything else will be taken care of by “the cloud.”

I’ve traditionally run all my services on machines (usually VPSes) that I administer. But it would be nice to get out of the system administration business.

Presented without (much) comment.