I realized that when searching for python and lzo, my github page is the first link. I’ve also noticed that people keep forking my github version and that there is no PyPI entry for python-lzo.

So, I decided it is fair to consider myself the maintainer for python-lzo and have registered it as a PyPI package. Find it here:

I guess the next steps will be to setup travisci, update the, add python3 compatibility and find out what changes the people forking it are making.

How to convert audio format in a video file:

ffmpeg -i input.mkv -vcodec copy -acodec ac3 -ab 448k output.mkv


I liked’s irccat as an easy way to post events (task completion and errors) to an IRC channel. I was less crazy about the recommendation to use ant to execute it. When I moved it to a OpenVZ VPS that used venet, it stopped working reliably. I’ve actually had trouble with quite of few Java services on that sort of VPS. So, I wrote my own in python, and it can be found on github and PyPI.

An added benefit is that much less memory is now used as well.

Google Calendar drops CalDAV

In January, Google said:

“With the launch of CardDAV, it’s now possible to build a seamless sync experience using open protocols (IMAP, CalDAV and CardDAV) for Gmail, Google Calendar and Contacts. We’ll start rolling out this change as planned across all platforms.” (citation)

Yesterday, Google said they would be moving CalDAV support to whitelisted only on September 16, 2013, and that new developers should use their propriatary API (citation).

Removing an entire service, like Google Reader is fair enough, but open standards access, like CalDAV, from products that are used by default with most new phone and tablets sold is low.

Removing Google Reader made me glad I never switched to it. Removing CalDAV support makes me want to renew my efforts not to use Google services beyond search.

Does anyone know if aCal is still read only?