Crypto-Gram recently recommended a study by Utica College's Centre for Identity Management & Information Protection. They do not limit their interest in personal information to the abstract: indeed they require your name, job title, company and email address if you would like to read the study.
I just released Loudmouth 1.3.2. This has been some time in the making: the goal has been to provide new features and keep compatibility with the stable 1.2 branch while Loudmouth 2.0 matures. We managed to add support for STARTTLS encryption, SASL authentication and DNS SRV lookups with minimal additions to the API. Together, these changes mean that Loudmouth will Just Work with your Jabber account in more cases, and that Loudmouth complies better with the XMPP 1.0 standard.
Users of Gossip and Telepathy will benefit from these improvements, and they should land in Maemo in the Diablo timeframe. We anticipate some stabilisation work on the 1.3 branch followed by a stable 1.4 release.
Senko deserves much of the credit for this release; he worked hard to make this happen. Thanks to Micke for supporting me in getting my first Loudmouth release out. Thanks also to Nokia, who supported Collabora's work.
- Eat This Book: A Year of Gorging and Glory on the Competitive Eating Circuit
- Eat This Book: A Conversation in the Art of Spiritual Reading
- Eat This Book: The Holy Community at Table with Holy Scripture
- Eat This Book: Cooking with Global Fresh Flavors
- Eat This Book: The Last Diet Book
- If the Cops Come, Eat This Book
- Eat This Book
- Eat This Book!
Of these books, only the last is edible.
- Don't Eat This Book: Foundations for Marvelous Meals
- Don't Eat This Book: Fast Food and the Supersizing of America
Neither of these is edible.
The Telepathy API has until recently only been available as a single large HTML document. The HTML is generated from D-Bus introspection XML with extensions for stuff like enums. I hacked up a conversion to DevHelp's index format, meaning you can use DevHelp to browse the documentation.
To set it up:
- check out the telepathy-spec repository
- run make
- copy doc/spec.html and doc/telepathy-spec.devhelp2 to a directory /usr/share/doc/gtk-doc/html/telepathy-sp
This might also work for other D-Bus APIs; I haven't tried.
(If you're developing using Gtk/GLib/Cairo/Pango/GStreamer/etc. and not tried DevHelp, I heartily recommend it. It's really handy, especially with the Ctrl-S shortcut.)
Recently I got involved with a local group, the Magnificent Revolutionary Cycling Cinema. The idea is to use bikes to generate electricity, and to use that as an instrument for education, in particular about sustainability. We just had our first outing at The Big Chill, a three-day music festival.
Eight of us cycled from Cambridge to the Big Chill site in Herefordshire, a journey of roughly 130 miles. Many others arrived by other means to take part. Once we got there, we set up a tent with a platform for the bikes, a central console for managing the power generation, a projector and a pair of speakers. This took the best part of a week.
By some amazing coincidences, many people with ties to the project happened to be at the festival:
- David Butcher, the godfather of pedal power; who was doing his own bike-powered project at the festival
- members of the Chicago and local Ross-on-Wye chapters of the Rat Patrol, who brought along some brilliant mutant bikes and home brew cider
- Fredric King, producer of B.I.K.E., a film we were showing about the Black Label Bicycle Club
- Run Wrake, creator of amazing short film Rabbit that we were also showing; though Run was VJing at the Big Chill, we sadly didn't get to meet him
As for the cinema: in general, reception was very positive. Many festivalgoers made the trek up the hill from the festival to visit us, and people were generally keen to get on a bike for a bit and feed our machine. We were very happy that it all actually worked; as it turns out the power we generated was pretty close to what we needed to keep running. (Odd, and somewhat disquieting, to think that the tent housing our roughly 330 Watt show was shone upon by a number of 1000 Watt lights.)
By the end, we were all exhausted from the 10pm-3am shifts, and somewhat sad at having to take it all apart. Nevertheless, I had a wonderful time. We learned a lot from our first excursion, and got lots of ideas for future improvements. Everyone involved seems eager to take the project forward to further success.
When people criticise Wikipedia, they often cite specific errors in articles as evidence that its overall quality is poor. The irony in this is that it encourages Wikipedians to fix those exact errors.
While the day and month of Hamilton's birth are known, there is some uncertainty as to the year, whether it be 1755 or 1757. Hamilton himself used, and most contemporary biographers prefer, the latter year; a reference work ought at least to note the issue. The Wikipedia article on Hamilton (as of November 4, 2004) uses the 1755 date without comment. Unfortunately, a couple of references within the body of the article that mention his age in certain years are clearly derived from a source that used the 1757 date, creating an internal inconsistency that the reader has no means to resolve.
I think McHenry underestimates Wikipedia's readers, and I suspect that when people notice inconsistencies they are smart enough to refer to other sources. At any rate, the article now devotes an entire paragraph to the question, including two citations. McHenry acknowledges this problem in a later essay (while criticising a different article):
By the time you read this, the entry will likely have been corrected, and some Wikipedians will proclaim this as another proof of concept. It does not occur to them to wonder how many people may have come upon that entry in the more than three years it has existed and relied in some way on the misinformation in it. They nearly got me.
He was right about one thing: the error in the article was fixed that same day. But I think this says something positive about Wikipedia: that it is willing to acknowledge mistakes and try to fix them as soon as they are discovered. For as long as McHenry continues to points out errors, there will be Wikipedians on hand happy to fix them.