This is the last blog entry here on WordPress. The archives have been moved back to my main site and my new blog entries will be moving there, too.
I’m going to leave a copy of the archives here because they’re well-indexed by search engines, but if you want to keep up on the latest, go here.
WebGUI looked good, but I couldn’t seem to get it working correctly. I tried a couple of other things, but none of those panned out, either. So I’ve decided to convert my main site back to Moin.
I used Moin on my main site back in the early 1.5-ish days and it worked rather well. I can’t remember why I changed, though it could well have been one of the many service provider moves I made. At any rate, Moin gives me the flexibility that I want, and I’m not terribly scared of Python if I want to get into some of the code that runs it.
I’ll eventually get my blog moved back there. While WordPress does blogs well I would rather keep everything together on one site. For some reason it gives me warm fuzzies.
On a whim I decided to have a peek about for a content management system that suits my needs. After a little poking about Freshmeat I came across WebGUI, which looks pretty interesting.
A couple of the obvious features I like are that it’s written in Perl and has a good security policy. Of course, TWiki is written in Perl and has a security alerts page, so that doesn’t guarantee much. WebGUI is shipped ready-to-go in binary form, and is ostensibly pre-configured, which I figure should save me from making too many foolish mistakes. Time will tell.
I’m going to give it a go on my main site soon. Photos don’t put themselves on-line!
I’ve started reading two new books today. The first is Free Culture, by Lawrence Lessig. The second is The New School of Information Security by Adam Shostack and Andrew Stewart.
I’m not much past the first chapter in either, but both seem pretty good so far. I’ll post my take on each when I have one.
Got a few good search terms to respond to again, so here goes:
twiki install centos 5.1: Don’t do it unless you know what you’re getting into. I had a bad security experience likely caused by Twiki, and I’ve seen a lot of people reporting similar experiences that they are convinced was Twiki’s fault. At the very least, google “twiki security” before you do it. The codebase is much too large for a single person to audit it in a reasonable amount of time. If you need a good Wiki in general, give Moin a try. Consider using a Wiki hosting service, where someone else has to worry about the security of the underlying machine. Or just don’t use a Wiki at all — unless you truly want what a Wiki in specific has to offer.
iphone unofficial toolchain easiest way: There is no easy way. There is drudge’s way that I point to in another entry, but aside from that I didn’t find any way that was at all easy. binutils can be convinced to generate (possibly-working) tools for arm-apple-darwin fairly easily, but I think GCC is a bit trickier. Don’t try to do it on your own unless you want to spend a lot of time making the tools work rather than using them.
do peanuts have gluten?: Nope, peanuts don’t have gluten in them. They may have gluten on them, though — it depends on how they’ve been processed or flavoured. When in doubt, read the label and assume that “spices” includes something gluten-based. I’ve seen some with and some without gluten, so have a look around.
Blogs written by programs suck. I’ve had a (relative) flood of incoming links from “blogs” that are nothing more than bottom-feeders wrapping excerpts from my blog with a machine-generated sentence or two around them. One was even a nonsensical machine-generated article (probably with a Markov chain, but with a lower-quality corpus of text than I’m used to seeing). They didn’t even choose any interesting entries to quote from (not that there are many of those here, anyway).
Maybe I’m just grumpy, but I’m thinking that FOAF needs an evil twin, maybe called DIAF, which would allow one to express their contempt for such a scheme.
According to the iPhone SDK ReadMe, the beta version of the SDK isn’t exactly ready to go on 64-bit systems. Given that I’m using a 64-bit system this may explain Error 34 and some of the other strangeness I encountered.
I’m also running into walls left, right, and centre in my plan to get GCC running on the iPod Touch. I had also forgotten about Perl‘s perverse configuration process, which doesn’t lend itself easily to cross-compiling.
At this point I think I’m going to punt on building Perl for the iPod until the official SDK is released and I can get on the developer program. The fact that this will almost certainly take several months (until Apple is ready to accept non-Americans) is annoying to me, but there’s naught that can be done about it — I simply don’t have the knowledge to port GCC to the iPod, and that seems to be the most sane way to get these things going.