Society (by alaric)

It's easy to sit and complain that Society Is Going To The Dogs, and hardly any harder to come up with somebody to blame (these days, immigrants and politicians are popular), and still well within the mental capacity of the average Daily Mail reader to come up with some satisfying-sounding radical proposals for what to do about it.

However, a society is a very complex system, and every change you make has complex consequences; nothing is quite as simple as it seems. Further complicating the situation is that any attempt to make your system of laws or government institutions more complex further complicates the analysis of subsequent changes; and, perhaps most pertinently, a society is not some beaker full of bubbling chemicals - the components of a society are sentient, some of them are even intelligent, and they are highly incentivised to make the best of their situation. In other words, people will figure out how to exploit systems, rather than working happily within the spirit of them.

People who are familiar with my approach to engineering solutions to problems will not be surprised to find that I suggest:

1. Forgetting all the cruft and historical baggage, and sitting down and carefully enumerating what you actually want from the system

2. Making the system as simple as possible (but no simpler), to reduce the scope for unexpected consequences

3. Using self-reinforcing negative feedback loops to maintain stability, while injecting noise to prevent stagnation in local maximae

   Read more »

A large rabbit run (by alaric)

Today, I made a run for Jean's rabbit, Blacky. He has a hutch, but rabbit hutches are far too small for rabbits to spend all day in; we'd been letting him run around the house (which requires constant watching, so can only happen for an hour or so), or letting him enjoy the slightly larger possibilities of a large cage with the bottom removed pegged down on the lawn, but we knew it wasn't nearly enough for him; he was always wanting to get out, and when he's in the house, he enthusiastically runs the entire length of downstairs.

So, I built him a run, with some help from Jean (he's her rabbit, after all, but there's only so much use a four-year-old is in this kind of project). Two metres and ten centimetres long, a metre and five centimetres wide, and fifty centimetres high; made out of a wooden frame with rabbit mesh, and a liftable solid door at one end, which also provides some fixed shade.

I relish the chance to do something with my hands, as I usually don't get time to, and end up spending all of my time at a computer. And Blacky certainly seemed happy; he was running around it at high speed, occasionally bounding into the air and spinning round, which is what rabbits do when they're happy. Note the motion blur:

That's not all, though; we've also bought him a lead, so we'll be able to safely take him for walks along the drive.

User Interfaces for Event Streams (by alaric)

Reading Phil Gyford's post about the reasoning behind his Todays Guardian app reminded me of an old interest of mine - the design of user interfaces that show people streams of events.

I hate the fact that I have several systems that have reason to throw notifications at me:

1. Incoming email (with multiple accounts)
2. Twitter (with multiple accounts)
3. RSS feeds I follow
4. Voicemails/SMSes
5. Notification of server failures and other such technical problems
6. Incomng phonecalls, Skype calls, etc
7. IMs and DMs in IRC, and people mentioning my name in IRC channels
8. People talking in channels I'm following in IRC
9. Scheduled alarms (time to stop working and eat!)
10. Batch processes have finished (I often start a long compilation/test sequence going then browse the Web for five minutes while it runs - then get distracted and come back twenty minutes later)

Many of these event sources are capable of producing events of different levels of urgency, too. It's really quite complex. Some things shout in my face (incoming skype messages cause a huge window to pop up over what I'm doing, for example) while some need to be manually checked (such as email; I get too much spam for the "you've got mail!" noise to mean much to me), and this has little correlation with the relative importance of them.

Obviously, the first thing to do is to have some standard mechanism in the user interface system for notifying me of events. Growl is a start, but it's focussed on immediate notifications, rather than handling a large backlog of events. What I want is something like my email inbox, that has a searchable, scrollable, history, and notifies me when new events come up. But I also want richer metadata than Growl has; I want all IMs, emails, and whatnot from the same person to be tied to that 'source' of events, so I can filter them into groups. I want to have Personal, Work, and Systems events, and to have Personal deprioritised during working and Work deprioritised during personal time. And so on.

The BlackBerry OS goes someway towards this with its integrated Messages system. Any app can register to put messages into the message stream, so when I get emails, BlackBerry IMs, notifications of new versions of software being available, etc. they all appear in the same time-stream and I get a 'new message' notification. I want something similar on my desktop, but with much more advanced filtering and display capabilities. My design for 'user agent' entities in ARGON involves using a standard "send an object to an entity protocol" for all email/IM/notification activities - the same protocol that is used to send print jobs to a printer, files to a backup system or removal storage device, orders to an automated process, and so on; it's roughly the equivalent of "drag and drop" in a desktop GUI. Incoming objects from 'elsewhere' are then combined inside the UA with internal events such as calendar alarms and situations the user agent might poll for, such as things appearing in RSS feeds, into a centralised event stream, by the simple process of translating all internal events into incoming objects like any other; but actually designing a user interface for displaying that is something I look forward to doing...

Phil's analysis of the newspapers interests me, because it's a very similar challenge. You have a stream of events, and the user may want to skim over them to see what's relevant then zoom into particular ones. How do you present that, and how do you help the user deal with an inundation of events, by applying heuristics to guess the priority of them and suitably de-emphasising or hiding irrelevant events, or making important events intrude on their concentration with an alarm? Priority is mode-dependent, too; if you're in an idle moment, then activity in your interest/fun RSS feeds should push out work stuff entirely - apart from important interruptions. And some events will demand my attention to respond to them, in which case they should offer me links to the tools I need to do that - a notification of a problem on a server, ideally, should carry a nice button that will open me up a terminal window with an ssh connection to that server. But some things might require my attention, but I can't give it yet - so I need to defer the task, so it doesn't then clutter my inbox, yet in such a way that it reappears when all higher-priority tasks are done. There are elements of workflow, where events need an initial "triage" to be categorised into "read-and-understood, do now, do later today, do whenever" and maybe prioritised, then later, deferred tasks need to be revisited.

Also, some event streams are shared. Perhaps an event should be handled by the first member of a team to be free, such as a shared office phone ringing, or a bug to be fixed or feature added to a software product. There needs to be some system for shared event pools, with support for events to be "claimed" from the pool by a person, or put back. Perhaps personal event systems should be able to contain proxy objects that wrap events stored in a shared pool somewhere, so they can be managed centrally as well as appearing in personal event streams along with events from other sources. Standard protocols would be required to manage this.

Looking at the relatively crude support for this kind of thing in even the supposedly integrated and smart combined email/calendar apps, I think there's a lot of fun research to be done!

A stroll in the countryside (by alaric)

On Sunday, I was looking after Jean as Sarah was in Cheltenham to run a writing workshop thing.

So I suggested that we might go for a walk, and Jean liked the idea - however, she decided she wanted a LONG walk! So after some discussion, we set off for the furthest of the three pubs in the Parish, which is about three miles away, with a packed lunch and lots of water, and Jean's teddy bear, who she decided should come with us.

To my delight, Jean didn't tire and demand to come home; we made frequent stops to drink water, and sat down in some shade in the woods to eat our cheese and biscuits, but we pressed on cheerily, past some lambs:

Eventually we reached the Fostons Ash for some lemonade and crisps.

Then Sarah rang as she was on the bus home, which stopped off by the Royal William, the pub nearest our home - so we decided to walk straight there to meet Sarah, taking a different route, where we got a little closer to some of the lambs:

At the Royal William we ate a filling dinner of chips (not so unhealthy if you've been walking all day!), and came home.

Jean was still enthusiastic at the end, despite having now walked about six miles from 2pm to 8pm!

The best thing was, I recorded about two hours of it on my concealed camera. It's mainly shaky footage of bushes and sky, but it offers the context for the audio track, which records all the awesome conversations Jean and I had.

Ugarit Roadmap (by alaric)

I've not had much time to hack on Ugarit lately, which is a shame - but just to keep you enthusiastic, here's my current roadmap.

Read more »