{"title":"jod.al","subtitle":"Personal blog of Stein Magnus Jodal","link":[{"@attributes":{"rel":"self","type":"application\/atom+xml","href":"https:\/\/jod.al\/atom.xml"}},{"@attributes":{"rel":"alternate","type":"text\/html","href":"https:\/\/jod.al"}}],"generator":"Zola","updated":"2019-12-23T00:00:00+00:00","id":"https:\/\/jod.al\/atom.xml","entry":[{"title":"10 years of Mopidy","published":"2019-12-23T00:00:00+00:00","updated":"2019-12-23T00:00:00+00:00","author":{"name":"\n \n Unknown\n \n "},"link":{"@attributes":{"rel":"alternate","type":"text\/html","href":"https:\/\/jod.al\/2019\/12\/23\/10y-of-mopidy\/"}},"id":"https:\/\/jod.al\/2019\/12\/23\/10y-of-mopidy\/","summary":"

Ten years ago today, on December 23, 2009, Mopidy was born. While chatting with\nmy friend and then-colleague Johannes Knutsen, we came up with the idea of\nbuilding an MPD server that could play music from Spotify instead of local\nfiles.<\/p>\n

This is the story of the first decade of Mopidy.<\/p>\n"},{"title":"pathlib and paths with arbitrary bytes","published":"2019-12-10T00:00:00+00:00","updated":"2019-12-10T00:00:00+00:00","author":{"name":"\n \n Unknown\n \n "},"link":{"@attributes":{"rel":"alternate","type":"text\/html","href":"https:\/\/jod.al\/2019\/12\/10\/pathlib-and-paths-with-arbitrary-bytes\/"}},"id":"https:\/\/jod.al\/2019\/12\/10\/pathlib-and-paths-with-arbitrary-bytes\/","summary":"

The pathlib<\/code><\/a> module\nwas added to the standard library in Python 3.4\nand is one of the many nice improvements that Python 3\nhas gained over the past decade.\nIn three weeks, Python 3.5 will be the oldest version of Python\nthat still receives security patches.\nThis means that the presence of pathlib<\/code>\ncan soon be taken for granted on all Python installations,\nand the quest towards replacing os.path<\/code> can begin for real.<\/p>\n

In this post, I\u2019ll have a look at how pathlib<\/code> can be used to\nhandle file paths containing arbitrary bytes,\nas this is valid on most file systems.<\/p>\n"},{"title":"Pykka 2.0 released with better ergonomics and performance improvements","published":"2019-05-07T00:00:00+00:00","updated":"2019-05-07T00:00:00+00:00","author":{"name":"\n \n Unknown\n \n "},"link":{"@attributes":{"rel":"alternate","type":"text\/html","href":"https:\/\/jod.al\/2019\/05\/07\/pykka-2.0\/"}},"id":"https:\/\/jod.al\/2019\/05\/07\/pykka-2.0\/","summary":"

I\u2019ve finally released Pykka<\/a> 2.0, the\nfirst major update to Pykka in almost six years.<\/p>\n

Pykka is a Python implementation of the actor model. The actor model\nintroduces some simple rules to control the sharing of state and cooperation\nbetween execution units, which makes it easier to build concurrent\napplications.<\/p>\n

Pykka 2.0 is a major release because it is backwards incompatible in several\nminor ways. However, the backwards incompatible changes should only affect\nquite narrow use cases.\nMopidy and its extensions,\nwhich is the largest open source ecosystem I know of that uses Pykka,\nruns unmodified on Pykka 2.0.<\/p>\n

In this blog post I\u2019ll go through some of the more important improvements in\n2.0.<\/p>\n"},{"title":"Mopidy-MPRIS 2.0 released","published":"2018-12-07T00:00:00+00:00","updated":"2018-12-07T00:00:00+00:00","author":{"name":"\n \n Unknown\n \n "},"link":{"@attributes":{"rel":"alternate","type":"text\/html","href":"https:\/\/jod.al\/2018\/12\/07\/mopidy-mpris-2.0\/"}},"id":"https:\/\/jod.al\/2018\/12\/07\/mopidy-mpris-2.0\/","summary":"

I\u2019ve released Mopidy-MPRIS<\/a> 2.0, the\nfirst major update to Mopidy-MPRIS in about 3.5 years.<\/p>\n

Mopidy-MPRIS is a Mopidy extension that makes Mopidy<\/a>\ncontrollable from other programs on the same machine through D-Bus. This makes\nit possible to control Mopidy from various widgets in GNOME\/KDE\/etc, as well as\nwith keyboard media keys.<\/p>\n"},{"title":"Four years of JavaScript churn: Mopidy.js 1.0","published":"2018-12-02T00:00:00+00:00","updated":"2018-12-02T00:00:00+00:00","author":{"name":"\n \n Unknown\n \n "},"link":{"@attributes":{"rel":"alternate","type":"text\/html","href":"https:\/\/jod.al\/2018\/12\/02\/4y-of-js-churn\/"}},"id":"https:\/\/jod.al\/2018\/12\/02\/4y-of-js-churn\/","summary":"

Yesterday, I released v1.0.0 of the Mopidy.js<\/a>\nJavaScript library. Even though the library serves as the basis for most Mopidy\nweb clients and has been in active use since 2013, this was the first release\nin almost four years.<\/p>\n

Four years is quite a long time in the world of JavaScript.<\/p>\n"},{"title":"Bringing the Mopidy music server to the browser","published":"2017-08-26T00:00:00+00:00","updated":"2017-08-26T00:00:00+00:00","author":{"name":"\n \n Unknown\n \n "},"link":{"@attributes":{"rel":"alternate","type":"text\/html","href":"https:\/\/jod.al\/2017\/08\/26\/mopidy-in-the-browser\/"}},"id":"https:\/\/jod.al\/2017\/08\/26\/mopidy-in-the-browser\/","summary":"

Note: This is a blog post draft that was originally written in January 2013,\nleft unattended for 1689 days, and rediscovered and published unedited in\nAugust 2017.<\/p>\n

During the five years since Mopidy entered the browser with its HTTP JSON-RPC\nAPI and the Mopidy.js JavaScript library, many successful Mopidy web\nclients have been built on top of this foundation. The APIs themselves have\nsurvived the test of time and have required minimal maintenance, just as I\nhoped when implementing the APIs back in November 2012.<\/p>\n

\n

Mopidy<\/a> is a music server written in\nPython. It plays music from various sources, including local disk and Spotify.\nMopidy can be remote-controlled by, among others, MPD<\/abbr> clients.<\/p>\n

In Mopidy 0.10, released in the middle of December, we added an HTTP frontend.\nThe HTTP frontend takes Mopidy\u2019s full core API and makes it available from\nJavaScript in the browser. This means that you now can make your own web\nclients for Mopidy in JavaScript, and Wouter van Wijk has already started on\nhis client<\/a> (updated\nlink<\/em>).<\/p>\n

I\u2019d like to write a bit about how we made the HTTP client.<\/p>\n"},{"title":"netsgiro: a parser and builder for AvtaleGiro and OCR Giro files","published":"2017-05-21T00:00:00+00:00","updated":"2017-05-21T00:00:00+00:00","author":{"name":"\n \n Unknown\n \n "},"link":{"@attributes":{"rel":"alternate","type":"text\/html","href":"https:\/\/jod.al\/2017\/05\/21\/netsgiro-released\/"}},"id":"https:\/\/jod.al\/2017\/05\/21\/netsgiro-released\/","summary":"

Today I released the first stable release of\nnetsgiro<\/a> to\nPyPI<\/a>. netsgiro is a Python 3.4+ library\nfor parsing and building Nets<\/a> \u201cOCR\u201d files.<\/p>\n

AvtaleGiro is a direct debit solution that is in widespread use in Norway, with\nmore than 15 000 companies offering it to their customers. OCR Giro is used by\nNets and Norwegian banks to update payees on recent deposits to their bank\naccounts. In combination, AvtaleGiro and OCR Giro allows for a high level of\nautomation of invoicing and payment processing.<\/p>\n

The \u201cOCR\u201d file format and file format name originates in days when giro\npayments were delivered on paper to your bank and then processed either\nmanually or using optical character recognition, OCR. I\u2019m not sure how old the\nformat is, but some of the examples in the OCR Giro specification use dates in\n1993, and the specification changelog starts in 1999 and ends in 2003. A couple\nof decades later, the file format is still in daily use by Nets\u2019 AvtaleGiro\nand OCR Giro services. In other words, I have high hopes that this will be a\nvery stable open source project requiring minimal maintenance efforts.<\/p>\n"},{"title":"March and April contributions","published":"2016-04-30T00:00:00+00:00","updated":"2016-04-30T00:00:00+00:00","author":{"name":"\n \n Unknown\n \n "},"link":{"@attributes":{"rel":"alternate","type":"text\/html","href":"https:\/\/jod.al\/2016\/04\/30\/march-and-april-contributions\/"}},"id":"https:\/\/jod.al\/2016\/04\/30\/march-and-april-contributions\/","summary":"

The following is a short summary of my open source work in March and April,\nalmost like in previous months, except that I haven\u2019t spent as much time as\npreviously on Open Source the last two months.<\/p>\n"},{"title":"February contributions","published":"2016-03-01T00:00:00+00:00","updated":"2016-03-01T00:00:00+00:00","author":{"name":"\n \n Unknown\n \n "},"link":{"@attributes":{"rel":"alternate","type":"text\/html","href":"https:\/\/jod.al\/2016\/03\/01\/february-contributions\/"}},"id":"https:\/\/jod.al\/2016\/03\/01\/february-contributions\/","summary":"

The following is a short summary of my open source work in February, just like\nin<\/a>\nprevious<\/a>\nmonths<\/a>.<\/p>\n"},{"title":"A guide to poor API management","published":"2016-02-18T00:00:00+00:00","updated":"2016-02-18T00:00:00+00:00","author":{"name":"\n \n Unknown\n \n "},"link":{"@attributes":{"rel":"alternate","type":"text\/html","href":"https:\/\/jod.al\/2016\/02\/18\/guide-to-poor-api-management\/"}},"id":"https:\/\/jod.al\/2016\/02\/18\/guide-to-poor-api-management\/","summary":"

This is the story of libspotify, as experienced by a Spotify customer and\nlibspotify developer for six years.<\/p>\n"},{"title":"January contributions","published":"2016-02-01T00:00:00+00:00","updated":"2016-02-01T00:00:00+00:00","author":{"name":"\n \n Unknown\n \n "},"link":{"@attributes":{"rel":"alternate","type":"text\/html","href":"https:\/\/jod.al\/2016\/02\/01\/january-contributions\/"}},"id":"https:\/\/jod.al\/2016\/02\/01\/january-contributions\/","summary":"

The following is a short summary of my open source work in January, just like I\ndid back in November<\/a> and\nDecember<\/a>.<\/p>\n"},{"title":"December contributions","published":"2016-01-01T00:00:00+00:00","updated":"2016-01-01T00:00:00+00:00","author":{"name":"\n \n Unknown\n \n "},"link":{"@attributes":{"rel":"alternate","type":"text\/html","href":"https:\/\/jod.al\/2016\/01\/01\/december-contributions\/"}},"id":"https:\/\/jod.al\/2016\/01\/01\/december-contributions\/","summary":"

The following is a short summary of my open source work in December, following\nup on my first report in November<\/a>.<\/p>\n"},{"title":"November contributions","published":"2015-11-30T00:00:00+00:00","updated":"2015-11-30T00:00:00+00:00","author":{"name":"\n \n Unknown\n \n "},"link":{"@attributes":{"rel":"alternate","type":"text\/html","href":"https:\/\/jod.al\/2015\/11\/30\/november-contributions\/"}},"id":"https:\/\/jod.al\/2015\/11\/30\/november-contributions\/","summary":"

The following is a short summary of my open source work in November. My hope is\nthat keeping better track of what I\u2019m doing will help me reflect on how I spend\nmy time, and help me to focus my efforts better.<\/p>\n"},{"title":"Building ARM Debian packages with pbuilder","published":"2015-03-08T00:00:00+00:00","updated":"2015-03-08T00:00:00+00:00","author":{"name":"\n \n Unknown\n \n "},"link":{"@attributes":{"rel":"alternate","type":"text\/html","href":"https:\/\/jod.al\/2015\/03\/08\/building-arm-debs-with-pbuilder\/"}},"id":"https:\/\/jod.al\/2015\/03\/08\/building-arm-debs-with-pbuilder\/","summary":"

The goal of this post is to help myself reproduce this pbuilder setup in the\nfuture. If you find it useful too, then that\u2019s great.<\/em><\/p>\n

Building ARM packages on older ARM devices like the Raspberry Pi 1 is slow, so\nI want to use a single amd64 machine to build Debian packages for all my target\nplatforms:<\/p>\n