I think effectively banning users by blocking IP ranges is going to become very difficult once IPv6 is rolled out.

Just saw this interesting snippet:

During a trip to Microsoft’s Redmond campus this week, I had the opportunity to meet with Mark Lucovsky, one of the original architects of Windows NT. We had a long discussion about NT’s development and evolution; one of the more fascinating tidbits he revealed was that NT doesn’t, in fact, stand for New Technology, as documented in books such as “Showstoppers” and “Inside Windows NT” (Microsoft Press, 1992). Instead, the name comes from the earliest days of the product’s development, when Microsoft designed NT to use the Intel i860, a RISC processor. In those days, Intel’s chip was behind schedule, so Microsoft had to use an i860 emulator called the N10. NT was so named because it worked on the “N-Ten.”

My effort to integrate Amazon-like features into this website: If you enjoyed the excellent dialogue between Mike and I, then you may be interested in this excellent set of best practices concerning HTTP implementation, as many of the same issues are brought up. It’s really a great read if you’re into that sort of thing. Hat tip: Zeldman.

Interesting day, woke up early (for me) to head to Fry’s and pick up some computer parts, then headed straight to HPUG. Once I got to HAL-PC by luck Cheryl (leader of the Web-Tech SIG) was giving away a 1.4GHz Athlon box and I nabbed that; there’s something wrong but I suspect it’s just the power supply. It has a really nice motherboard with RAID too so this will be perfect for my Linux file-server box.

Later tonight I took Joe his new Athlon XP box I built for him, and it’s running really great. When the sound card comes in he’s going to have a very nice setup. It’s surprisingly fast and it reminded me that I really need to upgrade my processor on my desktop, more so now that I’m doing .NET development stuff on it. (More on that later.)

Tonight after some testing I finally upgraded the server to PHP 4.3 and MySQL 4.0.10, and things are running beautifully.

What I’ve been avoiding writing about (and thinking about) is the part of today that wasn’t technology related. Helsa had to be taken to the Vet Hospital because she started throwing up several times and also apparently sometime between last night and this morning her skin got this yellow tint. The doctor said that she isn’t in any pain, but because she lost weight so fast her liver is probably overloaded with fat. They don’t know why she stopped eating in the first place, and we have no clue. They did blood tests, an ultrasound, and x-rays, and hopefully we’ll have some better data to know what’s going on. The doctor was very optimistic, so I’m feeling better about things, but it was still painful to se Helsa like that. They’re going to get some fluids and food in her through IV so that should help as far as the liver is concerned. It sounds like if they can get her body some nutrients so it stops trying to process the fat, that will help the liver. The only problem is that “fatty liver” is generally symptomatic of something else, and we haven’t determined the deeper cause.

All around blogspace, blogrolls are down as it seems rpc.blogrolling.com isn’t responding to requests, even though the main site is still working. All I had to do was increase the $cacheminutes variable in my script to a high number and now it’s returning the cache from the last time it was up. I need to make it so it does that automatically, but that’s a task for when I have more juice left in my laptop.

Well before I was delivering application/xhtml+xml to all Gecko-based browsers, but there seems to be a bizarre problem with Mozilla on this page. I had been doing my Gecko testing in Phoenix, which has no problems at all, and is now the only browser receiving the proper content-type for XHTML 1.1. Mozilla 1.0.1, 1.2, and 1.3a all seriously mess things up. First it shows the hostile XML error when it loads the page, which I brought on myself by putting it into super-strict mode, but the problem is there are no errors. I’ve triple-checked the page, and everything validates. It reports the error at a different place every reload, and it points to a random line from inside the blogroll, which is just basic XHTML. Then completely randomly it will show the page, but then stop displaying the content div after the “M” in the third paragraph from the last post, but then it shows the menu, which is after that in the code. When I change the content-type to be sent as text/html it displays every time, but still stops at the same place. Wait, as I’ve been writing this it looks like it’s working again in Mozilla, but only with the old content-type. Sigh. Hat tip: Mike Little.

In tweaking the structure of things here in my quest for perhaps the perfect(ly structured) weblog I came to the problem of the blogroll, which is obviously a list but there is no obvious way to format it in list format (I know that’s the XHTML2 module documentation but it’s well-written and applicable). What follows is an explanation of how to create a semantically correct blogroll. I am a paid subscriber to the service, so there may be options available to me that aren’t available to everyone, or you may just need to do things a little differently to get the same result.

1. First you can’t have anything in the first prepended or appended to updated links, because as we will see in a moment these are actually put outside the link "goodies" we’re going to play with later. So leave that blank. You can order your links however you’d like, I used to have them alphabetical but now that I’ve lost the visual indication of recently updated ones I’ve ordered them using the "Recent" option. (Should I be using an ordered list because of this? I haven’t decided yet)
2. Set there to be no container, we’re going to have to make our own container in a minute.
3. Originally I had thought that the opening and closing list item tags (<li>) could be put in the link "goodies" section, but it doesn’t work like expected, so for right now use the contributer only "Optional Linebreaks" option and put </li> in the field.
4. For global targets I set it to "NOTARGET" but you may or may not need/want to depending on your personal philosophy on this issue.
5. In the "Link Goodies" section prepend <li> to the link.
6. You’re done! Almost. Check out what we have so far.

We’re not quite done yet, because we don’t actually have a list yet, all we have is a set of list items with no enclosure. This will work with lazy UAs, but it’s not correct. To enclose it I’m going use a modified version of the PHP method given on the site for including the blogroll, but if you don’t feel like you need the extra feature I’m going to lay out, you can just wrap the output from the stock script above in a ordered or unordered list tag.

Mike Little just dropped his blogroll in favor of his own link manager. He may be biased, but the issue he brought up of the blogrolling server provoked some thought. In terms of features, there’s no reason why I shouldn’t be using Mike’s script, but what really keeps me coming back to blogrolling is the community features, which aren’t easily duplicated without (you guessed it) a large community. So with that in mind, I began to think of ways I could cache things on my end, thereby making things easier on the blogrolling server and faster on my end. Two benefits that come to mind immediately is that it will eliminate an unnecessary request on the client-side (I’m using the javascript version currently.) and that the blogroll can be gzipped with the rest of my page for clients that support it. Here is the code I’m currently using. The code can either be embedded directly or included from another file. It caches using the unique blogroll id, so multiple blogrolls should not be a problem.

Also please don’t think that formatting your blogroll as a proper list entails having it look boring, the power of CSS allows you to customize the look of your list like never before, and though my blogroll isn’t styled (yet) the button-looking menus on your right are actually unordered lists. In fact, you will have more control over the appearance now that your blogroll is formatted as a list than if it was just a paragraph seperated by line breaks. If you have any questions about this leave a comment and I’ll be happy to help out. Of course Jason could add a list option tomorrow and make everything but the cache redundant. C’est la vie!