...more recent posts
I though this article was pretty good. I hadn't heard anything from or about Jaron Lanier in a long time. I see he's still thinking about the future. In this article he explains why Bill Joy's worst fears probably won't materialize - due to the lack of improvement in software. But then he's got some other fears of his own. Almost sounds like he's not quite serious, but his ideas might well be closer to the mark then B.J.'s. Who knows?
I just got a copy of the email that promises you a cash payoff through some sort of Microsoft marketing program if you forward the message to enough people. I get this email periodically. Always very similar. Still, it's not true. Probably it will go around forever.
I'm always trying to clarify just what it is I'm thinking about with these posts. So here goes another try. The problem is about building smarter information storage and retrieval systems. This calls for automated agents (software programs) that can do, at least, preliminary sorting of data for us. Search engines are examples of what we have built so far. Not very sophisticated. The main problem with search engines is that they have to rely on some variation of matching words (or strings of words, or letter patterns within words.) Not meanings, but words. 'Cat' and 'Kitten' are only the same to a search engine if it contains a dictionary that explicitly links 'cat' and 'kitten' as synonyms. Humans don't think in such a literal manner (I think.) We can infer meaning beyond mere identity. Software programs are not so good at metaphore, or god help us, poetry. With so much information available, we need our software filters (whether they be search engines or something else) to do more than find matching occurances of words. For them to be really helpful, we need software to understand meaning. That's the problem. There are two directions towards progress, and both, I think, are being pursued. I guess we'll meet somewhere in the middle. The first direction involves including some machine readable codes inside information documents that explain the meaning of the document. This is called metadata, and XML is the format being pushed to encode this metadata into documents. (Although how you form the syntax of the metadata is not dictated by XML, so it doesn't address the hard problem, it just provides a non-proprietary form to encode that solution into. We still must all agree to use the same metadata syntax, or we'll be back where we started.) The other direction to take involves changes to our languages themselves. These changes revolve around making less ambiguous symbol systems. Or, in other words, making human languages more machine like. (It's not that machines are becoming smarter and will eventually be intelligent in a human way; it's that we are becoming more like machines as they become more like us, and we will meet somewhere in the middle.) One example of this sort of language shift is how technical people tend to talk in strings of initials. HTML, XML, PPP, POP3, IMAP, NMAP, RAM, GPL, SQL, ect... This isn't just a time saving device. It is more machine readable. Searching for 'toast' may not turn up that great reference to 'lightly browned bread', but searching for 'XML' will always turn up articles on 'XML' because that is what we call it. Always. From the start. Probably this sort of shift in the language is troublesome to some people. Perhaps our humanity (or at least our culture) is located exactly in that ambiguous space between symbol and meaning. This gap allows us to be flexible, and maybe even beautiful. But it makes it really hard to communicate well with our machines.
Another example of this change in language, and what got me started on this today, is the idea of constructed languages. Everybody has heard of esperanto, the most popular constructed language. But how many know about lojban? It bills itself as "the logical language." Personally, I feel my time is better spent learning Java if I'm going to pick up a new language, but the description of lojban is really interesting. It's a sort of extreme case that highlights some of the more subtle shifts in language that are definitely happening alread. And man, would it be easier to write smart information systems if we all spoke more logically. Of course, we might not like that world very much. I guess we'll see. AFAIK; FWIW.
Here's a really good article by Mark Pesce (Mr. VRML, and maybe he was with Survival Research Labs?) A history of hacker culture organized around the major works of "hard" science fiction. I'm not familiar with the most recent book he ends with (Greg Egan's Diaspora (1998)) but everything else seems right on. Great paper. I'll have to take a look at Diaspora.
Independence day quote, internet style:
"We reject kings, presidents, and voting. We believe in rough consensus and running code." (Dave Clark, IETF 1992)
Good discussion at advogato about online communities and the various ways they interact (usenet, web bulletin boards, mailing lists.) Lots of "I remember back in the good old days..." but that can be instructive if coming from the people who really were around "back in the day." The much ridiculued Jon Katz has a 4th of July type article about Jose Bove, the man on trial for trashing the McDonalds in France. And slashdot also recommends space.com for some streaming rocket fireworks action, featuring clips from both categories ("when rockets go right" and the ever popular "when rockets go wrong".) But really, you should probably get out of the house. Turn that computer off. Happy 4th.
HavenCo is the company doing that "secure" co-location facility on the abondon military sea platform turned wacky independent nation off the coast of England. (The one on the last cover of Wired.) Slashdot did the first half of their HavenCo interview a few weeks ago (in the first half they solicit the questions that will be asked from the readers.) The long awaited article has been posted. Pretty interesting. The questioners don't pull any punches, basically suggesting that this is just a P.R. stunt. They do better with their responses then I would have thought.
Here's more about the next generation "two-way" web. Sick of these stories yet? This one's a good intro to all the various players (not just Mozilla) who hope to enable the client side.
On line privacy: the good and the bad.