PUBLIC MARKS with search thought

A while back I wrote a little RDF vocab that extended the 2006 vCard vocab. It introduces a few extra terms which I thought were useful, mostly taken from the vCard 4.0 drafts at the time. e.g. a "lang" property to indicate languages spoken by the person represented. One other thing it has though is a more vCard-like way of representing telephone numbers, e-mail addresses, etc.

We thought it appropriate to allow Twitter to be more than just an on monitor phenomena. To accomplish this we have combined an Arduino, Ethernet Shield and typewriter. We added a little bit of solder (we’re spoofing keystrokes) and some coding (available here) and what we have is a twitter monitoring machine.

We collected some things from the internet we thought would work well on paper and we made it into a newspaper with a limited edition run of 1,000.

You can read more about it over here and you can follow the developing adventures of Newspaper Club over here.

I’m just a spectator, albeit a very interested one, but I have long thought that Hickson possesses just the right mix of pragmatism and idealism for this job.

Sauf que le pragmatisme 2.0 ressemble bigrement à de l'infantilisme.

a Web of Data version of a simple authorization scheme and protocol called WebAccessControl (WAC). It includes a draft of a vocabulary and a protocol (see also open issues with it). I thought it might be nice to have a visual representation of the schema

I’ve always been curious about which drummers use a click track and which don’t, so I thought it might be fun to try to build a click track detector

Adding persistence is something that we will typically all have to do at sometime in most real world web applications and will definitely slow things down a little; so I thought I’d approach the problem using my latest favourite storage engine, CouchDB

a Restish example using CouchDB

I have a no asshole rule which is really simple: I really don’t want to work with assholes. So if you’re an asshole and you work on my team, I’m going to fire you. Now, if the whole team says gosh, that’s awful. We want to work with as many assholes as we can! then we have a simple solution. I’ll fire me!

from the build a community section.

A better way to think of a manager is as a servant, like an editor or a personal assistant. Everyone wants to be effective; a manager’s job is to do everything they can to make that happen.

what concerns me is the question if this is going to keep working or not? For some time I thought spotlight-comments-based Tags would be a solution – and later have run into growing difficulties, Quicksilver not 100% working any more with Tags, TagBot occasionally overwriting Tags, the TagBot people simply going away etc. etc.

There was SpotMeta (which, if I recall right did use a similar "Xattr"-solution ) but with Leopard that was not compatible and not developed anymore. I intend to go with Apples further development of OSX (as long as my machine is going to support this) but I want to be at least assured that the people who implement this new scheme will make everything possible to make it likely that it wil continue to work in the reasonably future. Michael didn't start fear in my heart, he just gave me a starting point to ask these questions. (By the way I have asked a similar question the Tags-people, a question based on my past experiences with tagging solutions)

On my Apache mod_wsgi setup, I got 235.65 requests per second. That was really good, I thought! However, with the Spawning setup, I got 347.20 requests per second.

another way of deploying WSGI apps with graceful code reloading.

A set of RDF triples may be considered as a directed graph where the resources and literals form its nodes, and the predicates its edges. This graph in turn can be thought of as a resource in its own right, and dealt with in another graph. This document explores an extension for expressing named graphs in RDFa.

OK, thought we’d better blog these (and YES, they all exist.)

Nearly all of my experimental works (and some of the mainstream ones) composed since 1995 were developed by incorporating (to varying degrees) two main principles/thought processes:

1. Non-linearity: or fractal, controls the surprise, the unexpected, and is achieved by the Fractal Würfelspiel;
2. Linearity: maintains the flow and carries a listener through a work. This is delivered by recursive (fractal, self-affine) applications of the Golden Section

using SGMLParser and having seen nothing similar (and imagining its many uses!) I thought I'd give it a whirl in IronPython.