I was moving a bunch of files from one location to another, and it ended up that a ton of those files had the wrong permissions. Now permissions of 755 will generally work for serving an HTML file, but it should probably be served as 644, and since it wasn’t it was bugging me. We’ve already discussed my neuroses, let’s just leave it at that.
I think, perhaps, that truer words have never been spoken by an email application. The Microsoft Outlook Test Message is apparently sent to the Junk E-mail folder. By Outlook itself. You would think that somewhere along the way this would not make it through the Quality Assurance process. Either the message isn’t junk, or someone might need the message. Or something.
Wow. That’s a mouthful. For those who aren’t aware, it stands for Remote Procedure Call (RPC) over Hypertext Transfer Protocol (HTTP) on (Windows) Small Business Server 2003. Essentially, making an Exchange RPC connection via standard HTTP protocols, over a secure (SSL) connection.
I had been royally frustrated with this, as every document I seemed to find talked about installing this proxy server or that back-end server and this front-end server. In this install, I have a single server. It’s the proxy, the front end and the back end. Though the pages I found said it could be done, I couldn’t get it to happen.
I noticed today that I had a bunch of markup in my comments. I had been wondering why I had all these <p>, </p> and <br /> tags in there. Turns out I had neglected to set the convert_breaks=”0″ attribute when I redid my page. So it stored all the break information within the comment. This really didn’t affect the presentation at all, as it just came right back out in that format. But it meant that my comments had all this markup in them for the last couple weeks.
The world is afire this morning with talk of the announcements by Six Apart and the three major search engines (Google, MSN and Yahoo) to support a new HTML attribute named nofollow (in full, rel=”nofollow”). By adding this attribute to your link anchors, the search engines will no longer consider the linking page as a component of the linked page’s rank.
Installing the Movable Type “nofollow” plugin from Six Apart will automatically update the built-in tags MTCommentBody, MTCommentAuthorLink and the container tag MTPings. The use of the MTPings container should serve to update any URLs contained within, such as those produced by the MTPingURL tag and surrounding template code.
We have been married for very nearly two years, and in that time we had never bothered to update my wife’s name on her Social Security card. I’m sure this is probably something that we could be fined for doing, but we just never got around to it. Everything else? Absolutely. But not that little blue card.
So we went to the web site of the Social Security Administration to find out what we needed to do. We found a very helpful page that gave us all the information we needed. What’s more, it sounded like a relatively painless process. That would be a nice change when dealing with the government. Alas, it was not to be.
I must admit that I haven’t really received much from my wish list lately, but that’s okay. Some of you have sent monetary donations or even just a note of thanks. I’m not trying to make you feel bad. Though it’s probably worth nothing that, if you do, I’ve got plenty of things on the list. Head over and check them out for yourself.
The first tip allows you to enable an extra tabbed browsing option. Firefox allows you to open new links requested from other applications in new tabs, but what about those on web pages? Not possible without installing this line in your user.js file:
// Reveal more tab/window options: user_pref("browser.tabs.showSingleWindowModePrefs", true);
Once in place, you can go to the Tools > Options > Advanced screen, where you will have the option to change the behavior of opening new links from a web page. If you do this, you might also be interested in this tip:
/* Force New Windows Restrictions 0: Default - Divert *all* new windows to current tab/window or new tab 1: Don't divert *any* windows spawned by JS 2: Don't divert JS windows that include size/placement/toolbar info */ user_pref("browser.link.open_newwindow.restriction", 2);
One other tip has to do with the rendering of the page. By default, Firefox will wait 250 milliseconds (a quarter of a second) prior to displaying anything. Change this value to the value you like and you should see some speed gains:
// Last value in milliseconds (default is 250) user_pref("nglayout.initialpaint.delay", 0);
Each of these changes goes into the user.js file, which you can find in your profile directory. If you can’t find it there, just create a new one. You will need to exit and restart prior to seeing the changes take effect.
In each case, the comment (the part inside the /* */ marks) isn’t really needed – it just helps to show you what values you can use and what the option does for you, for when you look back in a few months and have no idea why you added it.
I’ve been trying to clean things up today, and a part of that is trying to get rid of a few things about Firefox that annoy me. Maybe “annoy” is too strong of a word. Inconvenience might be a better one. Anyway, I figured I would play and see what I can find out.
First, extensions. I’ve installed fireFTP. I like it, in that it’s got an interface right there in my browser, but it is not quite right. I can’t put my finger on it. Part of it is that keyboard navigation doesn’t seem to quite work, and part of it is that there seems to be a delay that I can’t seem to time just right. Since there is no real notification when something completes (a sound perhaps), I find myself sitting and looking at the screen. I’ll use it some more, but I’m leaning towards dumping it.
I also installed FoxyTunes. This is a very sweet extension, though I’m not sure that I listen to music enough to use it. Still, the design and interface is awesome, and I’ll likely use it to enhance the interface to the Bloglines Toolkit when I get the chance. I really like FoxyTunes because it gives me quick access to volume and mute – something that was annoying me about the Windows volume control. I think it likely that I’ll keep it.
Finally, I decided to do some tweaking on the UI.
I use Google a dozen times a day. Probably much more than that. It’s always a pain for me to run a Google query while I’m in the middle of something on another page. I usually use CTRL-N to open a new tab, then click on the address bar and enter “google”, then the search string. Blech. I rarely use the “feeling lucky” search, so I have had to go to the site itself, not just type the search string in the address bar.
So I tried using the search bar in Firefox, but that wasn’t doing it for me either. Then I stumbled upon this tip that seemed as if it would work. Nope. Didn’t seem to do a thing. I had almost given up when I found another link (now dead), which tells you how to do it: Type about:config in the address bar, find browser.search.defaulturl and set it to the value you want. Bingo. Now I just CTRL-L to get to the address bar, type the query, and it takes me to Google. Sweet!
Update: After this last step stopped working, I had to go hunting again. This site held the answer. Instead of changing browser.search.defaulturl, change keyword.URL. This may be a change in Firefox 1.5 (though my earlier version worked okay without it) or it might be something else. Regardless, this should fix you up.