Older blog entries for raph (starting at number 237)


The mailing list and Wiki for Fitz are now instantiated, thanks to rillian. If you're interested, you might want to check the archives; they contain some relevant discussion.

The next step is to populate the Wiki. I'll try to write a little something every day, just like I do here.


There's something fishy going on with the Anthrax investigation. All the evidence points to the culprit being someone hooked into the US defense establishment. At the same time, the FBI's investigation has been laughably incompetent.

Then, most remarkably, the New York Times published an editorial (reg required) talking about an individual who many believe is the culprit, but who has barely been investigated. The editorial itself doesn't name the name, but a few minutes searching on Google reveals it to be amost certainly one Steven J. Hatfill.

If this is true, it's a pretty big story. For one, it drives home the need for transparency and accountability in our government. The defense establishement has been largely exempt, because we have generally trusted that they need their secrecy to protect us from the bad guys. But if they are the bad guys, everything changes.

This story has been extremely differentially reported in the US and overseas media. Aside from this one editorial in the NYTimes, I've been able to find almost no coverage in the US mainstream press. If this is "objective journalism", fuck it, I'd much rather have Pravda. Fortunately, we have a vital independent press on the Web. I've been tracking this story through rotten.com.

I don't know that Hatfill did it, but it seems like by far the best lead the FBI has. For them not to be pursuing him vigorously, and for the US mainstream media not to be reporting the story, verges on the criminal.

Well Tempered Screening

I got my first color output today. Wanna see a sample? (note: 1.4M)

Also see these fun bug images: 1 2


Between Antony and tor, the discussion is really heating up. I should set up a real mailing list, so it gets properly archived and searchable and so on.


AaronSw pointed out that searching on "advogato" in google yields a "Google is hiring" adword. Considering the otherwise absolute radio silence from them, it's a very cool bit of feedback.


Woohoo! I got my first Well Tempered Screening output this morning. If you like, you can take a look at before and after. If you want to print them, try: pngtops golfer.png | pnmtops -equalpixel -dpi 300 | lpr

WTS solves three problems. It replaces the (possibly objectionable) patterning artifacts with a finely dispersed noise. It renders angles extremely precisely, where Ghostscript's existing halftones, even in "AccurateScreens" mode, are much less accurate than Adobe's. Finally, Ghostscript uses a "tile cache". As the cell grows in size, it can overflow the tile cache. In that case, performance can degrade horribly. By contrast, WTS thresholds on the fly.

There's more work to do, but I'm quite pleased.

Trustworthy names

Name services are an important battleground for trust. The question, "who deserves the right to name X?" is a deep one, and the answer is far more social than technical.

The way DNS is being run now sucks sucks sucks. One symptom is that there are no less than four services offering non-global DNS root service.

Much of the original motivation for my thesis work was a desire to build a better name system. It's a hard problem, though. More research is needed, or so I'm fond of saying.

What if you used the eigenvector metadata engine? Assertions would be of the form "name X belongs to public key 0x12345". When more than one such assertion exists for any given name, the one with the higher confidence value wins.

Obviously, this has the risk of "balkanizing" the namespace. Certain "controversial" names would resolve differently from community to community. While this isn't a serious problem for RealNames-like keyword searching, it is a problem if you're trying to publish stable URLs.

But here's the big question: even though the system is capable of balkanization, would it be a problem in reality? It's not clear to me. People can make local decisions to reduce the ambiguity in resolving names. For one, "registrants" can choose names less likely to be challenged. For two, when choosing the trust links for your community, you can emphasize people who take the game seriously and try to bind names to the rightful owner.

If the controversy can't be resolved, then the name is simply not useful as a global resource. Is this so bad? There are certainly a ton of names owned by squatters now, and can't be used, so it's not sure that the proposal would be any worse.

I'm not convinced that this is the best naming scheme. I personally favor first-come, first-served naming policies, and my PhD research goes into some detail about how to implement those. But I do think it's worth thinking about alternatives. What we have now isn't very good, and it isn't going to get any better by itself.

MuPdf and Fitz

I took a look at tor's MuPdf. It's very unfinished, but it's still very impressive. The unhinted, antialiased text is very pretty, and performance seems to be excellent. In many ways, it's a model for what I want Fitz to be. In many other ways, Ghostscript is the model, because it's already solved the problem of rendering the full PDF imaging model.

Antony Courtney has posted an architectural goals document for Fitz, with edits from me. There's a lot more I want to write, but I don't have big gobs of time right now. Also, it's obviously getting near time to set up the public infrastructure for the project: CVS and mailing lists as bare minimum, but I also want a Wiki.

Two degrees of separation

Gene Kan died last week, probably a suicide. Sad.


Developer release 7.21 is out. We're going to merge in the DeviceN code next, so this is probably an "island of stability".

Deep thinking vs not

Bram has been thinking deeply about how to efficiently move around large quantities of data in a robust p2p way. The result is BitTorrent, which is now in a good beta release.

By contrast, here we see "oopster", which is a specialization of Jxta to move around the OpenOffice binaries (which needs this kind of thing because of bloat, but that's another story). They're just beginning to think about the problems that Bram has already solved.

In the thinking world, one of the great applications of BitTorrent will probably be ISO's of free software distributions.

tromey: Cool.

sej: What you are proposing (adding transparency to PostScript) is adding nonstandard extensions to PostScript. It's possible, but I'm not sure what the real advantage is over PDF.

Jeff Darcy has written an interesting piece on protocols that contain reimplementations of TCP. Looking through the archives, Jeff has a lot of good stuff on protocols. Designing good protocols is an esoteric art, and should probably get more attention. It's nice to see writing in the open, even though Jeff works for a proprietary company.

Roughly, Jeff is to protocols as David McCusker is to trees. I think we should do a Vulcan mind-meld of the two, because I think an efficient protocol for remote access to trees is interesting. It's a central component of the Athshe vaporware project, but I freely admit that there many aspects I don't how to do right. Maybe in the absence of mind-meld technology, we can just bounce ideas off each other.

Dirt and noise followup

I wrote a few days ago about "dirt and noise". One of the things I was thinking about is the demonstration in Wolfram's book that the simple "rule 110" automaton can run a universal Turing machine. The straightforward implication is that, even for such ridiculously simple automata, if you know the initial state, you cannot predict whether a certain pattern (corresponding to the halting of the Turing machine) will ever occur. Simple universal machines are not new, but Matthew Cook's proof that rule 110 qualifies certainly pushes the simplicity envelope.

But here's a question. What if your cellular automaton didn't proceed purely mathematically, but had occasional bit errors? Does this make the halting problem go away? If so, does predicting the presence or absence of patterns become tractable?

Incidentally, the best review I've seen so far is this one, posted on the MAA website.

The book may be more interesting as art or literature rather than science. Certainly, the argument for deep equivalence in all fields of human intellectual endeavor is at the heart of Magister Ludi (Das Glasperlenspiele), by Herman Hesse.

Outrageous rudeness

tromey wrote more about his feelings upon receiving emails saying "automake sucks".

Think about the analogue in the real world. Let's say you spent years refining an artwork, and many copies were distributed. Then somebody comes up to you with a copy in hand, says, "you know this artwork? it sucks," and rips it in half. I am a peaceful person, but I would be quite understanding if you just hit him.

The principle of it is the same on the net, but of course there are a lot more assholes within easy reach of you here. Scale matters. In a smaller community, it would be a lot harder to get away with behavior like that, at least without being called on it.

I get some "thanks" emails, a number of impolite emails asking for favors, and a sprinkling of hostile ones. I really appreciate the former, and know I should send out more myself. The hostile ones I happily ignore. As for the ones in the middle, I somehow never seem to have time to respond. Ah well.

Last time I got a "you suck" message (it was here, three weeks ago), it was very easy to ignore, because the person who wrote it had already firmly established his credentials as someone whose opinion I cared nought about.

Thanks, Tom, for your work on automake. I use it, and it really does make life easier. The fact that it's actively maintained is quite a luxury. You're one of a handful of people actually doing a usable automated build tool, and I appreciate that.

Build tools

That said, now I'll talk about how automake sucks :) No, actually I'll respond to tromey's thoughtful comments on what a systematically designed build tool should look like.

I agree with the four bulleted points (integrate configuration with build, single invocation, tools as objects, caching), although I maybe I don't quite understand the implications of treating tools as objects. Does this simply mean that when you upgrade the C compiler, you rebuild everything?

Derived object caching is particularly interesting, not just because it makes builds faster, but because (if done right) it should make switching between variant builds much more pleasant. I want to be able to build with a -pg option and then have a binary I can profile. Even better, --with-checker (and other tools requiring compile-time support).

I've also been refining my thoughts since my rebar entry to the Software Carpentry competition. At the time, I proposed an XML syntax, but don't believe in that any more. I see makefiles as an integral part of the program. They are just as worthy of human readibility as the program code. But that's just a syntactic difference.

More fundamentally, I believe that the build tool should be a library combined with a simple lazy functional programming language. This is a somewhat quirky choice for a programming language, but I think well justified for this application. Laziness lets the implementation find and exploit parallelism without explicit direction from the programmer.

Other approaches, such as cons, provide a library over some available scripting language. That's also a reasonable approach, and keeps you from having to invent a new language. But I still favor the new language. For one, scripting languages tend to be pretty big, because they're trying to support general purpose computing. In this context, the language could be tiny. Second, I think the lazy approach has distinct technical advantages.

One such I'll try to illustrate here. A build script in the current rebar prototype looks something like this:

hello_o = compile/C ('hello.c');
foo_o = compile/C ('foo.c');
hello = link/C ([hello_o, foo_o]);

You could implement this sequentially, but because compile is functional (side effects are not permitted), the implementation is free to run the first two lines in parallel. In fact, the current prototype does so. But of course all serious build systems have some way to -j2.

More exciting, if an error happens (let's say foo.c doesn't exist), you can easily trace that to the exact line in the build file. I consider providing very high quality error messages to be vitally important. This is certainly an area where auto* falls down. With auto*, by the time you trip over the error, the build script has been macro-substituted and otherwise mangled beyond recognition.

In fact, I'd go so far as to say that a build system should be a tool for diagnosing build problems, with the happy side effect of actually building the target if there aren't any.

On deployment

A fundamental question: should building a project require a separately downloaded build tool, or should a distribution ship with enough of the build tool included to successfully run on target systems?

I lean toward the former. You can't ship a distribution without making some assumptions about available tools. autoconf assumes working sh and make. This is a reasonable assumption on Unix systems, but not on others.

Even so, I think it makes sense for code distributions to ship with a copy of the build tool (a good reason to keep it small and simple!) so that it will run on some subset of legacy systems. One of the advantages of doing it as a functional language is that you can have an implementation optimized for size and portability, rather than performance and features. In particular, the "tiny" flavor might eschew sophisticated dependency analysis.

Drawing the lines

I think it's very difficult to figure out where to draw the lines between a build tool and the rest of the system. In particular, the overlap between the build tool and the package system is considerable.

You can think of /usr/local/ as a very ad-hoc package database. The "make install" and "make uninstall" targets of makefiles do the basic package install and uninstall. /usr/local/lib/pkgconfig/ is one effort to collect metadata about installed packages. Distributions aren't very good at the basic function of finding libraries, and they also aren't very good at maintaining a separate development sandbox, especially one that can be manipulated without root privs. That's a good reason for /usr/local to continue.

The other way works too. Your build tool could build a .deb or .rpm, and you could rely on the package system to do it right. In fact, this approach is already common on Debian for kernel installs (make-kpkg). For one, it makes hardly any sense to install a kernel as non-root.

In the long term, to do things really well will probably require parallel evolution of the package system and the build tools. That's a bit daunting; it's likely to take a lot of time.

I care deeply enough about a good build system that I've put a lot of thought into it and have built a prototype. Tom, if I get the sense that your new approach is good, I will help you with it. I'll start just by dumping some of my thoughts (this can happen in my diary).

By the way, building Ghostscript is the acid test of a build tool. If a build tool can handle Ghostscript, it can handle anything.


gary just merged the various mod_virgule trees, and the site is now running the new code. One visible consequence is the (n new) notation for article comments. Less visibly, we can now proceed with courage, knowing that adding new features isn't going to cause pain for a future merge.

There are some performance issues that crept back in. Please be patient.


rillian has been hacking jbig2dec with help from me, and the progress is encouraging. It now decodes 042_10.jb2, with symbol dictionary and text region. My guess is that it will be decoding CVision streams very soon, as that's basically all the functionality they use. Before too long, we'll be inviting people to bring test images to throw at the code.

tromey: I'm sure automake gets more "sucks" emails than a lot of other packages. While I consider myself quite critical of the auto* tool hierarchy, I also very much appreciate the work you've put into automake, and believe that it's very high quality given the constraints it operates in.

The main challenge it faces, I think, is that there isn't a single well-designed tool, but a hodgepodge of different tools with overlapping functionality. Further, the boundaries between these tools are more or less set in stone for historical reasons.

Thus, I feel that it's possible to do a lot better than auto*. On the other hand, people aren't doing it, so from a practical point of view the question is moot.

I'm also very glad that you're thinking about how to move forward. Obviously, you have lots of practical experience that the "redo it from scratch" crowd lacks.

Another factor in your email volume is that automake has a lot of users. This speaks well to it being a useful tool, I think.

Bottom line: keep up the good work, and ignore the whiners.

Yesterday I blogged a feeling of frustration about the propagation of my trust ideas into the world. I got a great response back from Paul Crowley, indicating that he is reading and understanding what I'm doing. Thanks, that's what I wanted. Tonight, I'll wrote a bit more about my feelings. Feel free to skip such self-indulgent drivel, and/or to downgrade my rating.


Jeff Darcy called me on my obnoxious tone in a posting of mine from about a month ago. He's absolutely right. It's unreasonable of me to demand or expect that other people are listening to what I say. Not only that, but doing so I'd be setting myself up for disappointment big time.

Even so, I do have some feelings which I think are valid. Given the choice, I prefer two-way interactions. This blog offers many rich opportunities for such interactions, so much so that I can afford to ignore people who ignore me.

But Slashdot and SourceForge are not just blissfully ignoring me. The /. crew said disparaging and wrong things about the Advogato trust metric at a panel. SourceForge misrepresents their stupid popularity poll as being in some way an "expanded" version of the concepts from Advogato. Both of these things hurt my feelings, and also hurt the diffusion of my ideas. Now that I think about it, it's likely that the latter is the reason why I'm finding it difficult to get over the former.


I've gotten no ping replies from Googlers. They're probably all too busy computing their post-IPO net worths. Not that it matters anyway; there's no possibility of real communication, because they're all bricked up behind massive NDA walls.

Prompted by AaronSw, I found that there's a fair amount of literature on PageRank. Most of it is from "search engine optimizers", and much of it is of very low intellectual quality. The page I linked yesterday is the best of the lot; in particular, it has good references. I sent email to the author, Markus Sobek, and got a very nice reply. See, I'm not just whining about lack of exposure, I'm actually trying to do something about it :)

Anyway, I thought some today about a particular problem: what to do if you have a known attacker (someone who's trying to acquire a high PageRank for a site which doesn't deserve it). Pre-Google, you had lots of people doing this with huge keyword lists. Now it's harder, but of course it can be done. These days, when it is done, it's usually over highly-connected nets of interlinked pages, rather than individual nodes.

So let's assume you have a list of cheater nodes. How can you tweak PR to counteract the deliberate manipulation? One particular goal is to reduce the rank of all the interlinked pages, without having to carefully enumerate all the nodes. So the simplest technique, of assigning a PageRank of zero to all cheaters after running the algorithm, doesn't work well.

On the other hand, removing the cheater nodes before running PageRank is likely to work well. I'd guess this is what Google actually does.

Even so, I think there is a better solution, which is to run PageRank over the whole graph (including cheaters), but to zero out the rank of all cheaters after each iteration. Why is this better? Because adding more successors dilutes the flow of rank. Keeping the cheater node in the graph, but zeroing the rank, gives you the most dilution. This is particularly effective, I think, against these interlinked page attacks. You can express this nicely in linear algebra, and I'd expect you'd be able analyze the improvement quantitatively, using the attack-resistance tools I'm doing in my thesis.

You might even be able to take this a step further, flowing some kind of negative rank backwards through the graph. The assumption is that, if a node links to a cheater node, its other links are also suspect, and should therefore count for less in the rank computation. Let me propose a more concrete algorithm. Flip all edges in the graph, and do a PageRank with your cheater set as the seed (E(u) in the terminology of the PageRank paper). This gives you a R(u) rank for each node in the graph. Normalize so that the cheater nodes all have unity rank.

Now, in your second pass, do the usual PageRank, but after each iteration, multiply all ranks by 1-R(u) as obtained in the first pass. This will zero out the cheater nodes, and also reduce the juice for the nodes that link them.

Should I patent this idea? I'm not sure.


tor asked how Fitz was coming along. Well, right now the Ghostscript 8.0 release stuff is taking priority. But I do expect to be able to devote huge chunks of time to Fitz after the 8.0 release. Right now, the ideas are simmering in my head.

tor wrote:

raph: I did take a long hard look at ghostscript, and initially I wanted to use it as the graphics engine for my toolkit. However, I felt like I was stuck in a maze of twisty little passages, all different. Also, performance was a bit of an issue. I want analytical (as opposed to supersampled) anti-aliasing of text and graphics. I need unhinted font rendering, since I plan on using my toolkit as part of a typesetting system, where hinting, snapping to integer pixels and suchlike is a big no-no.

Yes, these are all very good things to be concerned about. Ghostscript's code complexity is a real problem, and I think it affects our commercial sales as well as free users. Analytical supersampling is cool, but 4x supersampling is not that bad. Ghostscript's implementation is quite a bit faster than I expected; I thought Libart would blow it away, but it holds its own.

Unhinted font rendering is very dear to my heart, and I agree very desirable when doing typesetting. It turns out that integer-fitting is just a decision taken by Ghostscript, not a deep architectural principle. I have a draft of a patch to make GS do unhinted (and subpixel positioned) text rendering, but haven't had the time yet to polish it for release. It's on my list for the 8.0 release though (and is therefore slowing down Fitz :), because I think it will be such a nice improvement for users.

Another issue which I didn't see you mention is images. Ghostscript currently breaks them down into lots of tiny rectangles (or parallelograms, in the case of general affine transforms). This isn't all that bad a choice when printing to high resolution, but definitely limits interactive screen update performance. Performance also becomes a problem with interpolated images.

The PDF viewer was really more a test program for my drawing layer, but it grew out of proportion and all the other PDF viewers seemed lacking in one respect or another so I decided to keep going.

I agree; the Ghostscript graphics renderer is poorly tuned for interactive editing. Also, PDF viewers do suck, even though I think Ghostscript handles the rendering parts pretty well.

Fitz will address a lot of the issues you raise, but it still pretty much vaporware. I'm looking forward to ramping the project up soon, at which point it might make sense to join forces. We should probably talk about our respective goals.

Obfuscated code

I'm continuing to struggle with integrating Well Tempered Screening into Ghostscript, although my recent progress is encouraging. A large part of the problem is the difficulty of the Ghostscript runtime. Believe me, trying to do objects-in-C in the Gtk+ framework is positively straightforward compared to Ghostscript.

Take "device colors", for example. The typedef and struct are in gxdht.h, the allocation is done in gsstate.c (for persistent allocation; temporary, stack allocation is done in gshtscr.c), the constructor is split into two parts, one in gsht1.c, one in gsht.c, and you have functions all over the place (gxht.c, gxcht.c, gxhtbit.c, gxdevndi.c) accessing the fields directly, rather than going through virtual methods. Then, of course, you have the marshal and unmarshal methods in gxclrast.c.

Part of the reason for this complexity is that the code is trying to optimize the amount of allocation that gets done. Since the halftone is allocated as part of the graphics state rather than separately, you can install a new halftone without actually allocating anything. Of course, it's more complicated than that because of gsave and grestore; when you restore the graphics state, you get the old halftone back, so the first time you set a halftone after a gsave, you do have to allocate.

I personally consider this a massive instance of premature optimization. A malloc()/free() roundtrip is about 250 cycles. Saving an allocation every pixel is worthwhile, but installing a new halftone is relatively rare (likely on the order of once per job), so the actual time saving is immeasurable.

Even if you did want to optimize the allocation away, the pattern of separating allocation and construction is not the best way to do it. Far better is to have a free pool, so that in the common case an allocation is a handful of cycles, but you still get a clean "new" API for creating the object, rather than having the client responsible for allocation.

At some point after 8.0, I'm going to write up a set of new guidelines for better runtime design, with a focus on code clarity. I am now convinced that it's possible to improve code clarity massively without sacrificing performance at all. One important tool will be patterns with roughly similar performance but with a cleaner interface. Free pool vs. exquisitely hand-tuned allocation is a perfect example. Also, there are good tools such as inline functions that weren't available when Ghostscript was started.

A move to C++ is also on the table, but I think it's possible to get most of the benefits by careful design of the runtime in C. C++ would open lots of questions, including whether or not to use the STL, whether reference counting is to be done with smart pointers, and so on.

In any case, I think the opacity of Ghostscript's code is a big part of the reason why you see new PDF renderers popping up. Ghostscript actually solves the problem rather completely (including funky color spaces and all that). But it's always fun to start a new project.

Async thoughts

The online discussion of asynchronous programming continues, with new posts by David McCusker and Jeff Darcy.

Let's take a big giant step back. Asynchronous programming adds a lot of complexity. Thus, there better be damn good reasons for it, or we wouldn't bother. What are those reasons?

It depends on the application. In many cases, the answer is purely quantitative. You want to usefully use time that would have otherwise been spent waiting for synchronous requests to complete. If you bail and do it the synchronous way, the system will have same basic functionality, but performance will start to suck.

In other cases, the problem demands asynchrony. Many of these problems have a simulation flavor. You can't just process all the state changes for one object and them go on to the next. The objects interact, so you need to interleave them somehow. A good example is video games.

Somewhere in between, you have problems that in theory don't need asynchrony, but in practice the performance difference is so large as to be qualitative. For example, these days it is a basic requirement of web servers to be able to serve multiple connections concurrently. (Note that some very early web servers only did one at a time).

I think you see different styles of providing asynchrony because of the different needs. One style is focussed on performance. In particular, you really need threads to take advantage of SMP machines (which, in turn, are quite rare in contexts where performance is not essential). Here, you're willing to take the hit of more complex code if performance increases enough. In particular, you may be willing to give up simplicitly in the mapping between the problem and the code to solve it. Squid is probably one of the best known exemplars of this style.

Other times, though, programming with asynchrony is the clearest way to encode the solution to the problem. To me, a clear example of this approach is CSP and the languages inspired by it. Of these, Limbo is the most fully developed. It's worth noting that the Limbo implementation is essentially single-threaded (multiple threads can individually block on I/O, but only one interpreter loop runs at a time), and is a slowish interpreter, so you can't really make the case that performance is the driving goal.

A more pedestrian example is the ubiquitous event loop found in video games and many GUI's. It evolved because it was the simplest, most direct way to express asynchronous behavior.

Composition of async modules

Jeff Darcy's overview of the tradeoffs between event-based and multithreaded approaches to asynchrony touches on one point which I feel is key: the ability to compose a larger system from smaller modules. Composition techniques we take for granted in synchronous systems, such good old-fashioned function calls, run aground in asynchronous systems.

In a pure event-based system, you can't call a procedure which might block. This limitation can be crippling. Often, you relax a bit and allow some operations to be done as blocking procedures. In classic Unix, the open() call is only available in blocking flavor, so when you need to open a file, you just call it and wait. Similarly, the classic gethostbyname() function has been a terrible source of blocking in Web browsers.

If what you're doing is mostly procedure calls, then threads can be a win. Go ahead and call a function which might block. If some other thread can make progress, it will. However, there are still a lot of gotchas. For one, you have to get your locking discipline right. It's easy to introduce subtle race conditions, which are a total pain to debug. Even more fundamentally, you have to write code in a thread-safe style. The classic Unix API's again fall flat, because of such things as errno being a global variable. These days, most people try to write thread-safe code, though.

Another thread gotcha is scaling. If your architecture forces you to have an operating system thread per connection, or a thread per simulated object, or whatever, you lose. Why did you choose the asynchronous route in the first place? If it's solely performance, then running up against scaling limits is not what you wanted.

Thus, a lot of the interesting work on asynchronous programming is about hybrids of the pure event and thread models. Matt Welsh's SEDA is one such, with a refreshingly clean quantitative focus. But it's interesting for another reason. The "stages" are relatively loosely coupled, which means that you might compose stages from different modules into one big app. In fact, the Haboob web server already has a mechanism for mixing in Jython scripts.

My feeling is that you could do something very similar with CPython. For performance, you'd want to write the core async runtime in C (to avoid Python's global interpreter lock), but then you could more or less freely intermix stages written in C and Python. The C ones could take care of your low-level, performance intensive stuff like the network wire protocols, crypto, and caches, and the Python ones could take care of your higher level application logic. I find this the most compelling architecture for performant P2P applications. Most importantly, you could start by writing everything in Python, then migrate to C as needed.

It might even be possible to provide a uniform Python API for both the Java-based and C-based SEDA implementations. Such a thing would be a fairly dramatic demonstration of cross-runtime programming.

more: Dirt and Noise, Trust, Jokes

Dirt and noise

Thanks to everyone who sent references to Shannon's 1948 paper.

Earlier, in discussing the software food chain, I asserted that lower-level nodes limit the performance and robustness of higher-level nodes that depend on them, but gave fault-tolerance as a counterexample. But, looking at communications channels, Shannon's theory tells us of a quantity, capacity, which subsumes both bandwidth and noise, and for which higher levels cannot exceed the capacity provided by lower levels. Looking at, say, reliablity alone, you don't see such a clear relationship. FEC is a way to get a high-reliability channel at a high level when only a noisy one is available at a low level.

The real world has lots of dirt and noise. Shannon was one of the first to really tackle that problem quantitatively, and the brilliance of his work still stands. Any new kind of science that pretends to model the real world must model dirt well, otherwise I am not convinced.


Ok, I am officially frustrated by the (lack of) response to my work on trust. I've gotten very nice encouragement from my friends on #p2p-hackers, and also mail from Mamading Ceesay, but even so, there still aren't very many (any?) people who are taking the time and effort to understand my work. I've done this work as a public gift, in the form of writing, free software, deployment, and placing the ideas in the public domain (everyone else is patenting their stuff like crazy 1 2 3 4 5 ).

Kevin Burton speculated that the reason I'm getting so little feedback is that all of the smart people are working for proprietary companies such as Google. Sometimes I get the feeling that I'm struggling with the basics of analyzing PageRank, while the 50 PhD's at Google have it all figured out and are laughing at my incompetence. Are any of you guys listening? I would appreciate a simple ping.

It is encouraging to see other people beginning to understand PageRank, even if they are "search engine optimizers." I just sent Markus email, and look forward to his response.

<AaronSw> the intersection of SEOs and linear algebraicists is small

Perhaps attack-resistant trustworthy metadata is just not an important goal. But then I see stories like this.


If Bush is serious about his goal of having Palestine democratically choosing a replacement for Arafat, he's sending the wrong people. He shouldn't send Colin Powell. The one he should send is Katherine Harris.

The execs at Enron, WorldCom, etc., didn't sell their souls to the devil. We're talking more along the lines of leveraged equity swap deals.

neoblogism: (n) a made-up word whose only reason for existence is to signal a blog context.

228 older entries...

New Advogato Features

New HTML Parser: The long-awaited libxml2 based HTML parser code is live. It needs further work but already handles most markup better than the original parser.

Keep up with the latest Advogato features by reading the Advogato status blog.

If you're a C programmer with some spare time, take a look at the mod_virgule project page and help us with one of the tasks on the ToDo list!