HOWTO: Add TwUp To The Qube

UPDATE: The Qube now has an option to select which audio service to use, outdating the following content unless you are using older source code.

Since a few people have asked me about this, here is how to integrate TwUp into The Qube, the popular non-GUI Twitter client for blind users. Because I am not a user of The Qube myself I do not guarantee that this guide will remain up-to-date, nor do I claim that it is quick and easy to follow. I am not hating on SndUp, although I obviously stay with TwUp because I created it. But really, I don’t know why you’d want to change audio services. Still, people asked me, so in case you know something I don’t, here’s how to it.

For those looking to integrate TwUp into other applications, look here for the terse, generic API documentation. Or, in the spirit of Web 2.0 and cloud buzz, be cool and use the web uploader, which has a progress bar and speed / ETA indicators.

Right, let’s cut to the chase:

  • Install Python 2.7.
  • Get the source code for The Qube (i.e. the zip-file for the master branch).
  • Extract the source code archive if you grabbed one.
  • Located the file “src\core\gui\” and open it in a text-editor.
  • Search for “” to locate the SndUp API URL.
  • Keeping the original single-quotes in tact, replace ‘’ with ‘’.
  • If you are that kind of person, locate and edit the text “Unable to upload audio file to SndUp.” to reflect your recent change.
  • Don’t mind the lines about an API key.
  • Safe the file. Yay for short steps.
  • Install everything from the “dependencies” folder, then launch “src\main.pyw”.
  • Enjoy your newly gained ability to upload to TwUp, or comment below in case it didn’t work for you.
  • Optionally use py2exe (bundled with The Qube) to cook your own executable.

Once again, you’ll probably want to have a look at the web uploader instead, unless you want to stick to The Qube or other Qwitter-clones for some reason. But be aware that TwUp has a public RSS feed, so using this service to have a convenient system for direct / private audio messages probably isn’t a good idea.

Linode vs. Digital Ocean: The Not-So-Scientific Way

UPDATE 2014-04-17: This post is now largely obsolete as Linode announced some big changes. I’m keeping it around for old times’ sake.

When Linode announced their 2013 NextGen upgrades, some people commented that this was high time because Digital Ocean had surpassed them in almost every aspect and was rapidly becoming a fierce competitor. Note that I am not specifically quoting anyone here. I might be overstating a little. Still, being the loyal-but-not-quite-stupid Linode customer that I am, I set up a demo account with Digital Ocean to see what was up. Maybe I could save me some money by going with the admittedly cheaper alternative.
Turns out I was overstating after all…
Continue reading “Linode vs. Digital Ocean: The Not-So-Scientific Way”