Tuesday, 26 August 2008
Saxon joy!
Not only does saxon run take much less memory, it also speaks XSLT 2.0.
Sunday, 10 August 2008
Tuesday, 5 August 2008
moving back to google reader from bloglines
OMPL just worked. I was able to move my RSS "reading list" from google reader to bloglines and back again with no fuss, no hassle and no duplication.
The advantages of google reader over bloglines are:
- AJAX - whereas bloglines marks all items on a page as read when you browse to it, google reader marks them as read when you scroll past them.
- Ordering - google entwines items from all feeds in time order, bloglines presents items feed by feed
- Better integration with other services
- Fast scanning of voluminous feeds
- Fast browsing (it seems _much_ faster when there are thousands of items)
- Less integration with other services
The fact that I have several google accounts and and only one of them is tied to my RSS reading means that there are tasks I can't multi-task between, even at the coarsest of levels and also means that contacts from the google account almost never get forwarded articles I discover via RSS.
The fact that my blogger.com account and my google reader accounts magically know about each other is great, as is being able to sign in once to a whole suite of tools.
In the end the reason for changing back was ordering. I read too many RSS feeds that cover the same topic for reading them out of order to make sense.
I've also just culled some of my RSS feeds, with the a prime criterion being the quality of their RSS. A number of web comics require one to click a link to read the strip and I no longer read them, but I still read Unshelved, which has the strip (and an ad) in the RSS.
Monday, 4 August 2008
Decent editor for blogger.com?
Before it drives me insane...
KDE/Gnome Māori localisation on the rocks?
stuartyeates@stuartyeates:~/tmp/mi$ svn co svn://anonsvn.kde.org/home/kde/trunk/l10n-kde4/mi/messages
svn: URL 'svn://anonsvn.kde.org/home/kde/trunk/l10n-kde4/mi/messages' doesn't exist
stuartyeates@stuartyeates:~/tmp/mi$ svn co svn://anonsvn.kde.org/home/kde/trunk/l10n-kde4/mi/docmessages
svn: URL 'svn://anonsvn.kde.org/home/kde/trunk/l10n-kde4/mi/docmessages' doesn't exist
stuartyeates@stuartyeates:~/tmp/mi$ svn co svn://anonsvn.kde.org/home/kde/branches/stable/l10n-kde4/mi/messages
svn: URL 'svn://anonsvn.kde.org/home/kde/branches/stable/l10n-kde4/mi/messages' doesn't exist
Things don't look good for the upcoming 4.* releases, with the stats for translation at 0%: http://l10n.kde.org/stats/gui/trunk-kde4/team/
Gnome Māori localisation is not much better: stable at 1%: http://l10n.gnome.org/teams/mi
In the medium/long term there is hope that much of this localisation can be bootstrapped by application-centric localisation that appears to be thriving, particularly with respect to firefox, thunderbird and OOo.
Sunday, 3 August 2008
Leaving catalyst :( joining NZETC :)
Exciting things about the NZETC from my point of view:
- We Will Not Cease by Archibald Baxter, a first hand account of conscientious objection in the first world war by the father of New Zealand's greatest poet
- Works by John Cawte Beaglehole, including letters that mention him meeting my grandfather ("Jack Yeates") at Cambridge
- Work with Learning Media, (who I've previously published poetry with) on their publishing process
- Extensive use of the New Zealand Creative Commons Attribution Share-Alike License (CC BY-CA) license for works
Wednesday, 9 July 2008
Who should I nominate for the NZ Open Source Awards?
Kiharoa Dear for excellent work in getting firefox, thunderbird and open office working in Māori contexts:
http://kiharoa.dear.maori.nz/
Standards New Zealand for sanity control in the OOXML fiasco:
http://www.standards.co.nz/news/Media+releases/NZ+maintains+negative+vote+on+OOXML+Standard.htm
Hagley Community College for rolling out Ubuntu in a secondary school:
http://computing.hagley.school.nz/about/opensource
Who should I nominate? Is there someone I've missed?
Monday, 30 June 2008
I'm confused about hardy heron and default applications
export EDITOR=/usr/bin/emacsThen along came the wonderful debianness of the apt-family and the alternatives system.
update-alternatives --config viNow this system too is being undermined by various systems, leaving me uncertain where to set things. What I'm trying to do is:
- have Sound Juicer and not Music Player (RhythmBox) launched when a CD is inserted. There is an entry for "Multimedia" under the "Preferred Applications" menu option, but this seems to be about opening files, not responding to newly-mounted media and Sound Juicer is not listed as an option. There doesn't seem to be anything about CDs under the "Removable Drives and Media Preferences" (although this is where the setting are that automatically load F-Spot when I attach my camera, which seems like the same kind of thing).
- configure which applications I can launch on the .cr2/TIFF/Canon RAW files produced by my digital camera I want the same applications to appear in both the file browser and F-Spot (which look like they're presenting the same interface but apparently aren't). ufraw seems to be the tool of choice here (either standalone or as a gimp plugin), but I'd like to pass it some command line args. I can find no entry or this under the "Preferred Applications" menu option.
Mike O'Connor at Friday drinks
Some of them turned out better than others.
Sunday, 29 June 2008
What should the ohloh homepage look like?
In a previous post I criticised ohloh homepage for being completely useless for current users of the site. This was somewhat unfair, since I provided no concrete constructive suggestions as to what should be on the page. This blog post, hopefully, fixes that.
To my mind there are two classes of information that should be on the homepage: (a) things that lots of users are confused about and (b) things that are 'new' (think customised rss feeds) (c) combinations of both.
Finding out what people are confused about is easy, just look in the forums, where people are most confused about:
- changes in their kudos
- why their enlistment hasn't been updated
- why version control system of choice isn't supported
The list of 'new' things is:
- new / updated projects
- new / updated users
- new / updated enlistments
- new forum posts
- new RSS items in projects RSS feeds
These (1), (3) and (5) can be filtered by the users connection to the project (contributor/user/none).
So the trick now is to find combinations which help users understand what's going on and encourage users to engage with ohloh and the projects.
Idea X: A feed of updated enlistments a user is a contributor or user of:
- Project A's enlistment at http://example.com/git updated 24st June 2008 at 24:50 GMT. A, B and C are the biggest commiters to this project, which is in Java and XML. Last updated 1st Feb 1970.
- Project B's enlistment at http://example.com/git updated 24st June 2008 at 24:50 GMT. D, E and F are the biggest commiters to this project, which is in C and shell script. Last updated 1st Feb 1970.
- Project C's enlistment at http://example.com/git failed at or about revision 12345. Click here for instrustions on what to do about this. Last updated 1st Feb 1970.
- ...
This not only tells user the status of their projects, but that enlistments are being processed, the expected time between each processing of enlistments, that some processing fails and that there's a link to find out more information. Such a feed also focuses attention on the processing of enlistments---which is the heart of ohloh and the key differentiating factor that seperates ohloh from 15 billion other open source sites.
Idea Y: A mixed feed of upstream bugs that effect ohloh performance and functionality:
- Ticket "support for .xcu file format" updated in ohcount by user "batman"
- Post "jabber message length" updated in Help! forum by user "someone else"
- Ticket "svn branch support" updated in ohloh by user "robin"
- Ticket "bzr support in ohloh" created in ohloh by user "joker"
- Post "jabber message length" created in Help! forum by user "someone"
This lets people keep up with the status of ohloh progress on issues such as the implementation branch support for svn and support for hg.
Monday, 23 June 2008
New ohloh look and feel
Once you're logged in, almost nothing above the scroll cut on the front page is useful---we already know what ohloh is and don't need bandwidth-hogging ads to tell us. What we need are deep links into new stuff---projects, users and forum posts.
How about logged in users see content rather than ads on the homepage?
Sunday, 15 June 2008
Kernel Hell and what to do about it
I've been in kernel hell with my home system for the past couple of days. What I want to build is a custom kernel that'll do xen, vserver, vmware, selinux, support both my wireless chipsets and support my video chipset. Ideally it should be built the Debian/Ubuntu way, so it just works on my Ubuntu Hardy Heron system.
So far I've had various combinations of four or five out of six working at once.
I'm not a kernel hacker, but I have a PhD in computer science, so I should be able to at least make progress on this, and the fact that I can't is very frustrating. At work I grabbed a kernel off a co-worker, but it wasn't built the Debian/Ubuntu way.
Standing back and looking at the problem, there seem to be two separate contributing factors:
- There are a huge number of organically-grown structural layers. I count git, the kernel build scripts, make, Linus's release system, the Debian kernel building system and the ubuntu kernel building system. I won't deny that each of these service a purpose, but that's is different points a which each of the six different things I'm trying to make work can begin their explanation of how to make them work and six different places for things to go wrong.
- There are about many Linux distributions and each of the things I'm trying to get working caters to a different set of them.
Wouldn't it be great if someone (ideally under the auspices of the OSDL) stepped in and said "This is insane, we need a system to allow users to build their own kernels from a set of <git repository, tag> pairs and a set of flags (a la the current kernel config system). It would download the git repositories and sync to the tags and then compile to the set of flags. Each platform can build their own GUI and their own backend so it works with their widget set and their low level architecture, but here's a prototype."
The system would take the set of repositories and tags in those repositories and download the sources with git, merge the results, use the flags to configure the build and build the kernel. Of course, sometimes the build won't work (in which case the system sends a copy of the config and the last N lines of output to a central server) and sometimes it will (in which case the system sends a copy of the config and an md5 checksum of the kernel to a central server and optionally uploads the kernel to a local repository), but more than anything it'll make it easy and safe for regular users to compile their own kernels. The system would supplant "building kernels the Debian way" or "building kernels the RedHat way" and enable those projects working at the kernel level to provide meaningful support and help to their users on distributions other than slackware.
Potential benefits I can see are:
- increasing the number of crash-tolerant users willing to test the latest kernel features (better testing of new kernels and new features, which is something that's frequently asked for on lkml)
- easing the path of new device drivers (users get to use their shiny new hardware on linux faster)
- increasing the feedback from users to developers, in terms of which features people are using/interested in (better, more responsive, kernel development)
- reduce the reliance on linux packagers to release kernels in which an impossible-to-test number of features work flawlessly (less stressed debian/ubuntu/redhat kernel packages)
- ease the path to advanced kernel use such as virtualisation
You know the great thing about that list? Everyone who would need to cooperate gets some benefit, which means that it might just happen...
Macrons and URLs
A review of how lots of programs handle macrons is at http://research.elabs.govt.nz/macron-support-in-open-source-web-applications/.
Saturday, 14 June 2008
Exporting firefox 3.0 history to selenium
I wrote a quik hack to export the history as a series of selenium tests:
sqlite3 .mozilla/firefox/98we5tz3.default/places.sqlite 'select * from moz_places' | awk -F\| '{print "<tr><td>open</td><td>"$2"</td><td></td></tr>" }'
sqlite3 locks the file, so you'll need to close firefox (or take a copy of the file) first. Cut and paste the results into an empty selenium test.
Obviously, your profile will have a different name.
Sunday, 4 May 2008
OpenID - Everybody Wants To Go To Heaven, Nobody Wants To Die
My first free openid provider (http://stuartyeates.videntity.org/) went belly up for reasons I'm still not too sure about, but the life expectancy of internet startups and free services has never been that long. I have a new identity (http://stuartyeates.myopenid.com/) which does me just fine.
One thing I've been noticing is that while a host of the internet services that I use want to be my identity provider, very few of them want to let me login using an openid provided by another identity provider. From a business point of view I can completely understand this: they want to know everything about the user so they can (a) off better, more integrated services and (b) see more customised advertising. I have no problem with (a), but (b) is one of the reasons I'm eying up openid in the first place.
They don't understand that to get to openid heaven, they're going to have to die. By giving away the user-authentication-and-give-us-your-personal-information step, they can drive significantly more logins and significantly deeper interaction with their website and with their content. Sure, they can't necessarily get access to the users email address and whatever fake personal details they submitted at sign up, but I've yet to see this used particularly well anyway. The personal details certainly don't seem to be used to anywhere near the same effect as analysis of user behaviour.
What would be really good is an openid identity provider with (a) shared no information with any of the large advertising groups or dominant internet companies, (b) really clear information about privacy expectations (and I'm not talking here about a page of legalese titled "privacy policy," but discussion and disclosure of things which jurisdictions user data is stored in, steps taken to avoid collection of user data, etc) and (c) a clear sustainability model to prevent it being bought-out for the user data and to ensure it's continuity (I can imagine paying a subscription for it).
I can imagine that this is the kind of thing that google or yahoo might sponsor in their efforts to promote their next generation of web authentication standards. The existance of such an outfit would hugely boost the reputation of such a standard and lacking the huge advertising and existing lockin it would hardly challenge their own identity providers while answering a whole range of independence, privacy and monopoly questions.
Tinkering with ohloh
I've added and am actively curating a group of go/baduk projects. The overall goal is to encourage reuse and reduce the willingness of hackers to rewrite go/baduk systems from scratch.
My next step on the technical side is to write some GRDDL (Gleaning Resource Descriptions from Dialects of Languages) to transform the XML returned by the API into RDF, which I can them import into simal.
My next step on the social side is to mention what I'm doing in some of the go/baduk mailing lists, but I want to wait until I've got something concrete to provide that Sensei's Library (the current repository of information about go/baduk programs) hasn't already got.
Friday, 2 May 2008
Happiness is tests passing
I've just (re-)attained the happy state of the unit tests passing in the key package of jgogears. I've invested a surprising amount of time and energy in the unit tests, mainly as a form of requirements analysis, and I'm really pleased with the result.
Sadly, the core package that contains much of the code has some outstanding, longstanding failures which are going to be challenging to fix. They are represent failures in jgogears' ability to round-trip board states between GNU-Go ASCII and SGF files and will require a bug-for-bug reimplementation of the GNU-Go ASCII board printer.
jgogears has reached the stage where it now plays games that are obviously meant to be go, but is not yet a serious contender.
Friday, 18 April 2008
Resetting vmware networking
In an attempt to erase it's memory I removed /etc/vmware/locations but this caused vmware-config-network.pl not to run at all.
Eventually I worked out that the trick was to remove everything in /etc/vmware/locations other than the lines near the start telling it where to find directories and executables and rerun vmware-config-network.pl selecting all the defaults.
Suddenly everything worked.
Thursday, 20 March 2008
Quality explanations of technical issues
Imagine my pleasure at reading this analogy of a really rather complex compiler / interrupt issue.
For the record, I know nothing about the x86 interrupts, since we were taught interrupts using the much simpler RISC SPARC system.
Tuesday, 18 March 2008
Tinkering with suffix-trees and algorithms
It linearises board positions and then uses classic string processing techniques, principally a large suffix-tree. Suffix-trees are widely used in information processing, information theory and compression fields of computer science. I also used them extensively in my recent Ph.D.
Currently I'm training with about 200 go games (~40k moves), giving me about 950K nodes in my suffix tree.
I've just switched my linearisation method from a strict distance measure to one which capitalises on adjacency much better.
There are a number of tuning parameters for the rate at which I grow the tree. I'll be tinkering with them as I increase the number of boards I'm using for training.