June 9th, 2002


RFC 2617

Earlier today I read through RFC 2617 (HTTP Digest Access Authentication) and was pretty impressed by a number of parts about it, particularly how the server can reply that the nonce value is stale and the client will reply without prompting the user for the password again. That was one of the things that'd always bothered me about HTTP-based challenge-response in the past, but I just hadn't taken the time to more than skim the RFC before.

But .... I wonder if this spec is implemented properly in enough common browsers. Does anybody know?

I could do some really cool shit with this, but I don't want to waste my time if it's going to only 80% work in 95% of browsers. Or, I could just go all 1995 and put up "This site best view with Netscape 12.0!" all over my sites.

Update: *sigh*... not perfectly with Mozilla.

Reliable internet

I just love it when my my parents' cable modem service dies in the middle of critical remote server maintenance.

At least I can rest a bit comfortably, knowing screen is keeping my processes going for the 15 minutes until I get back online, but still ....

I think I'll ask the company to get me both DSL and cable at my house for reliability.

Tonight I....

- went to the gym
- got a bunch done on new project; sent design docs off to partners
- bunch of LJ maintenance
- played myself some pool

Now it's 3:45 and I get to sleep in tomorrow.

I unplugged my alarm clock the other day because I don't need an alarm and I don't really ever care what time it is.

Two phonelines ... fun!

Remember how I was saying the other day that all phone calls around here are for my 13-year-old brother?

What's worse is that we have two phone lines. We got the second way back in modem days and just never got rid of it, so that's "his" number.

So I hear the second line ring a dozen times until his answering machine picks up, then his friends hang up and call the main line, thinking maybe he's in some remote part of the house that can't hear only half the number of phones ringing as the main line.

Which means I can answer the main line immediately with "Cole's in Seattle this weekend watching some baseball... can I take a message?"

Kinda throws them for a loop.

And shit... now I forgot that kid's name.


Nick mailed me, saying he has a project for me.

His parents have tasked him with building a stone walkway around one side of their house, saying that "You're an engineer, we've spent $80,000 on your education.... build us a stone walkway."

And it's sunny and I love projects, so I'm going over to help him.

The easy part.

For the past week I've been in research & design mode, making schemas, protocol docs, reading up on different protocols, learning new APIs, and just taxing my design in general for every possible scenario I could imagine, no matter how bizarre and unrealistic.

All that gets pretty stressful.... the amount of forward thinking required gets you second- and triple-guessing every little detail, and in a given day I was only completely sure of one or two new things by the time I went to bed. And once in bed, I couldn't sleep, continuing trying to break my design.

But I'm pretty damn happy with it now, and I started implementing it yesterday. Got a bunch done then, and today even more so.

Seeing it come together so quickly now is really exciting, both writing the internal APIs, seeing those work, and then seeing the entire thing in action. At one point today I typed for about two hours, ran it, and it just worked. So. Rad. I love programming.

Anyway, now I'm all hyped up after reaching a good milestone and want to go do something, but it's Sunday night and everybody has jobs and stuff tomorrow so they go to bed early. Pssssh. Lame. So I might just go to bed here myself.

I'm waiting for Evan and Sherm's finals to be over, so I can work with them more.