Release 1.6 and the protocol spec

A few weeks ago, before I discovered Groovebasin, I started working on [my own music server and web UI](http://github.com/irskep/summertunes). I've shaved about a dozen yaks by now, including websockifying mpv, writing a REST server for beets, starting to look at mpd instead, and then finding Groovebasin which apparently solves half of my problems.

Your UI and JS style are not to my taste, so I'm going to keep pursuing my project regardless. (I'm a 2007 iTunes kind of guy to your 2008 Amarok.) But if you document and lock down your protocol spec, I would love to just make my project a Groovebasin frontend and finally be done with my frustrating search for a high quality music database + player combo.

Looking at the commit history I'm a bit worried that this project is stalled. That's mostly why I made this ticket instead of just waiting. I could just base my work on the latest master, but it's explicitly marked unstable (despite being a year old).

I know all too well what it's like to make something cool and kind of big for free and then lose time and motivation, so it's okay if you tell me that updates just aren't likely.