As nymia pointed out, we've apparently been down or something... but it's all better now.
On the software front, I've been trying to piece together a coherent conduit for mail to my Visor, so I can stop spending over an hour daily going through misc@openbsd.org, ports@openbsd.org, tech@openbsd.org, etc. and do some of it on my lunch break at work. (If only we had a decent 'net connection there, sigh.) For as much flack as it catches, IMAP-UW's c-client library is really quite good (with the Perl Mail::Client lib), and I can add it to Coldsync's Palm Perl libs to complete the picture.
I would really like to use Coldsync, but /usr/local is taken up by OpenBSD ports right now, and I don't want to throw extra stuff in there. One of these days I'm going to have to seriously sit down and figure out enough about the infrastructure to permit my old trick under FreeBSD (/usr/contrib) to work. /usr/contrib is a better place to put this sort of software anyway, it's written by someone else, maintained by us specifically for our OS, but not supported by us. That, historically, is the role of /usr/contrib. /usr/local, OTOH, should be for truly local stuff that can be blown away with no ill effects on the rest of the system. At least that's how I've always felt about it. Unfortunately, /usr/local is ingrained into a lot of places in our tree right now, so massive changes would need to take place, and I don't think a lot of others see the value in it. Maybe I'll go on a crusade sometime. There's no real reason why the system can't discover what your preference is for everything. I've got a few ideas on that front...
deekayen: that's no way to live. I wish you had smarter parents. Alcohol abuse really sucks. Get them help if you can.