Regular Kamusi visitors have probably noticed that the site has suffered from chronic problems with page loads. Last week the problem got so bad that we had to restart our server several times. We scoured our usage logs and analyzed our system, and we think we've solved the problem.

Two emails arrived within two days of each other. First, from "kibo," who gave the email address "nothing@nothing.no":

Regular Kamusi visitors may have noticed some funny things going on with the site recently - service outages, malformed pages, broken links, font changes, changed page locations, and more. It's been a long and busy week...

The Kamusi Project is seeking a student intern with an interest in business AND African languages to help develop and implement a financial sustainability plan.

The intern will work online from his/her own computer (no travel involved), in constant internet communication with other members of the Kamusi Project team in Africa, Europe, and the US.

The position is unpaid, and hours are negotiable. Rewards will include letters of reference, solid experience for the résumé, some cool Kamusi swag, and exciting and satisfying work on the cutting edge of African language technology development. (The position might transition to a
paid part-time job during the next academic year.)

On the old Kamusi site we had a fun little slideshow feature. For the original slideshow, we uploaded a bunch of pictures in a folder on our server. When someone visited the homepage, one of the pictures would load randomly, and then another random image would load 15 seconds later. The feature did not work well on all browsers, so we eventually replaced it with a script that loaded a random image from the folder, and then enabled the user to scroll through the remaining images.

When we moved to our new server, we decided that we wanted a customized slideshow that could show the pictures that Kamusi community members have uploaded to illustrate dictionary entries. Each photo would link to the entry with which it was associated, so the feature would be a good way to introduce people to new words. We also want to encourage people to use the photo uploader feature, and we're hopeful that people will be motivated to contribute images by seeing their pictures in the slideshow.

Dictionary image submitted by a Kamusi community member (click photo to see the word it illustrates):
<?php require_once("/var/www/slides/slideshow.php");

?>

A couple of provocative posts (Post 1 and Post 2) by Don Osborn have revived some thoughts I've been having about African languages and information technology. Don's posts have arrived at a good moment - the power here in Accra just went out for the eighth time today, but I've got about enough battery life to type some preliminary notes.

Don writes about the "long tail" and the economics of language. In sum (and without network, I can't scroll back through his posts), he is thinking about the question of "smaller" languages and how people who are born speaking them relate to their mother tongues from an economic perspective. Do people who speak these "long tail" languages feel the need to learn languages higher up the tail for economic purposes? Will such people abandon their mother tongues over time, in preference for a language that allows them to communicate with more people and therefore have expanded economic and social potential?

These are questions that I have long pondered in the context of Swahili in East Africa. Swahili is very high up the tail. With somewhere in the neighborhood of 100 million speakers throughout East and Central Africa, it is spoken by about as many people worldwide as German, roughly one out of 60 people on Planet Earth. Many of the languages of East Africa are endangered, and others are diminishing, with Swahili being the language of choice of many of those people who are drifting away from their mother tongues. I have witnessed rural households where the children are discouraged from speaking their ethnic languages in favor of Swahili, and thus cannot speak with their own grandparents in a common language (though they communicate fine, each speaking their preferred language but understanding what is said in the other).

Abdel-Karim writes from Egypt, "Regarding the content, is this [PALDO] planned to be a wikipedia-style dictionary (i.e. Entries are generated by users and some sort of community ranking/approval mechanism is in place with an optional discussion page for each entry?)."

The answer: Not exactly. There will be an editor for each language, or a team, who will be responsible for approving each entry. Remote users will be able to submit entries or edit existing entries, but all of their work must go through the official editor for that language before going live.

Before implementing the editorial tools for each language in PALDO, we need to build the data models for each component language. Languages differ in more than words, so the database that contains information about multiple languages will have to account for those differences.

We have a long task list ahead of us as we transition to our multilingual model. We've prepared a master list of what we need to accomplish, and divided the tasks into some logical categories. It's a lot to get done in a short time - the core programming needs to be done by July 1 - so if you are able to volunteer for a coding task, we'll be happy for the help.

The document listing our coding priorities is really meant for internal use, but if you are interested in seeing what we're up to, click here to look at the working draft. (This is a Google Spreadsheet, so you'll need a free Google account to view it.)

Comments, of course, are welcome on this blog.

Last night we removed the "Transition Status" section from the Kamusi Project homepage. When we moved the site from the university where the project started out, we had to re-wire a great many features. Now we're declaring that job complete.