dmerrill: Not to worry. If some hoser snatches the linuxdoc.org domain, all that has to be done is to make it not worth his while to own it. One just has to make it more expensive than he/she/they can afford. ISP costs can become very high when a site is getting hammered with enough traffic to flood a few OC-3s.
Not too much to say about my end of things (whatever those things may be). Still job hunting. The game is scarce and the hunters are many.
Went to Barnes & Noble the other day. Noticed, for the first time in a long time, a copy of Fahrenheit 451 on the shelves that did not have to phrase "The temperature at which books burn" on the cover. Hallelujah! Almost bought it (I've been waiting a long time to get a new copy, just to avoid that bloody insult on the cover), but I don't have a whole lot of money and it came down to Fahrenheit 451 and a book of poetry by Seamus Heaney, Seeing Things. As I've read Fahrenheit 451 many times, but had never seen the Heaney book before, I'll have to wait a bit for Fahrenheit 451.
Right now, I'm reading Excession, by Iain M. Banks. As I've come to expect from Iain Banks, it's awesome (in many senses of the word). One of his many "Culture" novels.
Got distracted from xmms yesterday when I noticed the "Invisible IRC Project" listed on the CodeCon website. v1 is pretty much "encrypted, hopefully anonymized, IRC." v2 (in development), is what I'm interested in. Sounds like some ideas I tossed around (bad follow through) for a distributed, encrypted, chat system. One thing that I ran into was how to avoid dupe sends of the same message between systems that are acting as servers. Obviously, don't send it to the system you got it from, but I was also thinking about using a 32bit CRC or md5sum for the message along with a TTL. The sum could be used both for error detection and by transmitting the sum ahead of the message, the receiving server can say "already got that." Next question is: for the average size of chat/irc messages, is the computation+transmission overhead of an additional checksum worth it?
Still trying to figure out why I'm getting large amounts of "popping" on cd's that I rip using my new system. If I turn around and rip them on the old system, no pops. It's either the cable running to the cd and dvd drives or the drives themselves. Don't think it's the drives, as I can rip from either drive and get the same result. Guess I'll have to buy a different SCSI-2 cable and see if that makes any difference.
Went to an engagement party for a friend tonight. Not entirely sure as to the wisdom of the the whole deal (think both of them are too young, emotionally), but it's their lives. Thing is, where we all come from, once the vows are taken, you can't just walk away if things don't turn out so well. Forever is a long time when you're not happy.
Haven't done much in the way of coding lately. Life is a really odd thing. I have a personal theory that the universe can be described as a fractal, with various places in the fractal corresponding to specific places and times. Choose a point and start zooming in. No matter how closely you look, there's always something more that can be seen by looking even more closely. Infinite detail in infinite combination. Huh, that last bit sound suspiciously like some philosophy espoused by the Vulcans from Star Trek. Time for the padded cell.
Noticed Alan Cox's comments about the mess that was I2O. I can truly sympathise. I spent far too much time sludging through the 400+ sheets of double-sided 8.5"x11" printout that made up the I2O specification. Fortunately, the company I worked for decided to ditch I2O (too much hassle, and the customers started developing nervous twitches when our sales people said "I2O"). Instead, we rolled our own company-wide wrapper for storage and network controllers. From the comments of several former co-workers who had been on the various I2O committees, I2O started out as something cool and then got bogged down in the committees. Design by committee rarely produces anything good, something that is all too easily forgotten.
Considering that one of the main points of free software is that it is "open to many eyes," it seems to be a little off that so many of the prime examples of free software make little if any effort into making the code more understandable.
I, myself, had more than one occasion to grumble about the crypticness of the network stack while at my previous job.
Tomorrow: more resume work.
So, for anyone who knows someone who could use a network server developer, Perl/CGI/DB person, Linux driver/network stack munger or just about anything else that involves C/C++, Perl or Korn work on a Unix/Linux OS, I can be reached at klevin@eskimo.com. Heck, I've got nothing against other languages (had briefer flings w/ Common LISP, Java, and CORBA via C bindings).
Anywho, time to hit the proverbial sidwalk and do some "networking."
21 Jan 2002 (updated 21 Jan 2002 at 20:13 UTC) »
--
I've figured out what the "person" and "proj" tags do here on advogato, but still not sure on the "wiki" tag, so here's and experiment, wiki'ized "klevin": klevin.
Hmmm. Amusing, but I'm not sure of the utility. Perhaps that's because there's no entry for "klevin". I may have to remedy that.
FOAF updates: Trust rankings are now exported, making the data available to other users and websites. An external FOAF URI has been added, allowing users to link to an additional FOAF file.
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!