Over the past few months I've written entries here which have elicited some interesting replies. I ranted about poor support from SuSE and received personal emails from company representatives who wanted to help me out.
Last week I wrote about LinuxGazette disappearing (turned out to be DNS errors on my side) and received a comment from Heather suggesting I was mistaken.
Interesting that so many people see what I write, and also slightly intimidating given that my sense of humour has repeatedly been misintepretted in the past .. online and offline.
I don't really have a good conclusion here, but I suspect I just got lucky. I tend to write fairly trivial things, and rarely take any of it very serious.
ObDebian: I'm in the middle of turning a spare bedroom into a real office. I now have three low-end machines in a line across two desks, and a decentish desktop machine too.
It looks likely that I'll have a lot more time to contribute to Debian over the coming months (although this isn't confirmed yet). Either way I'll have a much nicer "working" environment at home.
ObSocial: The postcards I sent to Debian folks seemed to all arrive, except for the one I mailed to Amaya (despite having several rounds of back and forth to get the address right). That was returned to me yesterday. Try again tomorrow I guess.
Cross-Country postal-services suck. Although I know they handle a lot of letters/parcels I seem to always get the unlucky straw.
ObDebian-Admin: The Debian admin site now allows users to submit tags. Took a while to get right, but I'm happy with the Web 2.0 ajax code. How very ..
22 March 2006 21:50
Is it possible to uniquely identify an audio CD-ROM? I've "stolen" the disc ID code from the various CDDB clients I've seen, but I wonder how unique those values are.
I'm looking at setting up a simple CDDB/FreeDB-esque server to store audio information which can be queried in a sane manner. The results will be XML data.
Using XML data I can have individual details for each track. Ideal for soundtrack albums. Plus I can require clients to ignore attributes they don't understand to allow for future growth.
I could use the ID + sha1 hashes of the song lengths I guess …. or even a SHA1 hash of the track-data (but I'm worried that read-errors could cause problems with data summing, plus reading each track will be slowish).
I see comments like this a lot:
Conceptually very similar to the ISBN number used for books, the ISRC (acronym for International Standard Recording Code) is a 12-character code defined to uniquely identify a music track song). Unfortunately, over the years very few authors have adopted this standard and currently less than one percent audio CDs use the ISRC.
The UPC (Universal Product Code) is a 13-digit number that uses the UPC/EAN bar coding standard to uniquely identify the whole CD. The same ISRC considerations apply to the UPC code: very few audio CDs currently use the UPC.
In related news two tickets for Radiohead + Beck are mine :)
25 March 2006 21:50
I think it is safe for me to mention this now.
I will soon be starting to work for the Debian-friendly hosting company Bytemark, working with their Xen + UML systems &; etc.