A week ago I noticed that Eric Raymond had updated his version of the jargon file; in doing so, badly and without redirects, he did, of course, break all the links from my jargon file lexicon interface. Again.
The easiest way to minimise web maintenance is to never link to content that you don't control. (I should have borne that in mind before I set up my blog.) I was so busy fixing the breakages that I didn't notice the changes in the jargon file entries themselves.
NTK's blipticle on jargon file changes prompted me to look at Wiki. Could a community-maintained Wiki replace the jargon file? Would Twiki, with its changelogs and some editorial control, suffice? Could its backend be modified to autogenerate a printable dictionary on demand? I see much of /. had much the same idea.
One of the areas Wikis fall down in lies in naming. The 80sJoinedCapsWikiNamingConvention may be cute, but it is not search-engine friendly. A clearly-separate-words-wiki-naming-convention works much better for clear indexing of individual keywords, and if the keyword is mentioned in the url it is significant. (I prefer - to underline because the dash is visible and is not confused with spaces in underlined links, because the dash does not require the shift key, and because dash is permitted in dns naming, allowing consistent use throughout the url.) Recognising that significance, incidentally, is why I have google's recommendation for 'ungood'. It's not luck.
It's been almost a year since I last did a SaVi release. I really should do another release, but until Geomview builds with gcc 3.2, there's likely little point. All that's happened recently is the successful relocation of the original Geometry Center web content.