“The body of missing CNET editor James Kim has been located, authorities announced Wednesday. Arrangements are being made to transport Kim to an undisclosed location, according to police. Kim had been missing in the remote southwestern Oregon wilderness for 11 days and was found at approximately noon Wednesday about half a mile from the Rogue River, authorities said. Kim, 35, left his family’s stranded car Saturday morning searching for help and never returned. “He was very motivated…he traveled a long way,” Josephine County Undersheriff Brian Anderson said at a press conference Wednesday afternoon. The Kim family has asked not to be contacted at this time.”

A very sad story - most of it transpired while I was away in Hawaii. I feel like I knew James, having linked to his reviews, news stories and videos over the years. It’s shocking when something like this happens, even more so when it happens to someone I consider to be a peer of mine in this industry. There are many lessons to be learned here (such as staying put when people are looking for you), but James tried to save his family and I have nothing but respect for that.

In grinding through the 1614 email messages I had when I opened Outlook this morning, one email in particular stood out to me: it was an email with an attachment that was 31 megabytes in size. THIRTY-ONE FREAKING MEGABYTES. That’s beyond ludicrous, that’s well into the “will crash some email clients even if it happens to make it through and doesn’t kill your entire Inbox and cause all your other email to bounce” category. Now, the person sending it likely didn’t realize it was so big (I sure hope they didn’t), but here’s where smart software should come into play: an email client simply shouldn’t allow a user to send an email attachment that big without a polite warning, stating something such as “The attachment you’re trying to send is very large - it may not be received properly”. The threshold would be set fairly high - likely around 10 MB before it would trigger the warning - and there should be an option for users to ignore the warning if it’s something they do often and know that the person on the other end can accept large files. No one wants a return to irritating Clippy-like helpers, but there’s just no way that intelligent software should let users do something as foolish as send a 31 MB email attachment.

On all of my PCs, I have the middle mouse button configured to act as a browser back button, allowing me to quickly go back to the previous page I visited rather than having to click the back button or use the ALT+left arrow key. I spend so much of my life online, saving a few seconds or (more importantly) wear and tear on my mousing arm is important to me. So I was a bit frustrated that I couldn’t seem to configure Firefox 2.0 to allow me to use the middle mouse button on my Microsoft mouse to open links in a new tab when I used the middle mouse button to click on a link. At first I thought I needed a Firefox add-on, but after some research it turns out that by default the middle-click button opens links in new tabs - but I never saw it working because my Microsoft mouse software always overrode it. By going into the Control Panel > Mouse > Buttons settings, and selecting the check-box for “Enable Program-Specific Settings”, I was able to select the Firefox executable and set the Wheel Button to Middle Click. Now in Firefox the middle click on the mouse button will open up links in new tabs, while in other programs it will go back.

I thought it might have been easier to streamline everything to work the same, so I tried making the left zoom button on my Microsoft mouse function as a middle-click button, thus keeping the real middle mouse click button for the Back function, but ergonomically the zoom button is slightly out of position for easy use - which is why I very rarely use it. So it’s back to the previous configuration: Firefox-specific middle mouse click to open a link in a new tab.