You're always free to send email to me, though.
(image created at http://services.nexodyne.com/email/)
Monday, November 14, 2005
Minor blog changes
How Tom manages his email
Most importantly – the scroll bar is gone from my inbox! I have 14 emails in my inbox. 12 of them are to-do items – so maybe I’m not all caught up, but I’m not that far behind anymore.The post discusses in more details how he manages his email. I currently have 2188 messages in my Inbox -- that's only going back to the beginning of August, I have many more archived. I think if/when I decide to try something along the lines of what Tom does, I'll probably archive more regularly rather than delete or file by subject or recipient. With a good desktop search tool, searching the archive is quick and easy.
On a related note, I tried Google Desktop and found it weak when compared to X1.
Thursday, November 10, 2005
Custom Yahoo Maps
Wednesday, November 09, 2005
Sniffing Passwords is Easy
Wednesday, October 05, 2005
Searching the Deep Web
Friday, September 30, 2005
Geeky Friday: Little known vim "feature"
Odder still, the HTTP status code returned was 199. Normal returns from a web server have status 200, errors are 500, redirects are in the 300 range, 404 is for missing pages. I've never heard of 199. I searched Google and a couple forums for the various software tools that could be involved and found nothing.
So, I went to the source code. Using "find . -mtime -2 -print" to identify all files which had changed in the past two days, I focused on a file I had been testing with the night before.
The extent of my test was adding something along the lines of:
if (some condition) {
print some debug information to the log file
}
I considered this to be safe testing code. It didn't modify any variables, make any database calls, or call other procedures (other than the command to write to the log file). I got the debug information I needed and then edited the file again back to the was it was before. Or so I thought.It's worth mentioning at this point that I was using vim instead of emacs, my usual text editor.
When I looked at the source code today, I looked at the line immediately following where I had inserted and removed the debug code. It was a line to return (programatically) a web page to the user's browser. One of the arguments to the command is the status code. Instead of the usual "200" I saw "199".
I was bewildered. Clearly this was my fault because the mistake was right where I had been editing this file, but there was no reason for me to have changed this return code. How did this happen?
I fixed the code right away, but I had to know what went wrong. My first guess was that vim had some keystroke shortcut to decrement a number -- it seemed reasonable since the new value was exactly one less than the correct value. So, I googled for "vim decrement" and I was right.
I laughed heartily, especially because the key combination for this is Control-x (C-x) which is used as the beginning for many emacs commands. Most notable, "C-x C-s" is used to save the current file. Clearly what had happened was that my well-trained fingers knew it was time to save the file after I had removed the debugging code and hit "C-x C-s". Unfortunately, the cursor was placed on the number "200" when I did this and vim did what it was programmed to do when fed C-x. My brain kicked in and saved the file in a vim-approved way but I didn't notice the error.
As for the discrepancy between Firefox and Internet Explorer, I wouldn't say that IE did the Wrong Thing, it just did things differently. Firefox looked at the content of the information returned, which looked like valid HTML data, ignored this odd status code and displayed the page. IE, on the other hand, decided that if the status code wasn't 200, it would display an error page. Ok, maybe that is Wrong, it's certainly less elegant and less helpful.
Lessons learned (or rehashed):
- There's no such thing as safe testing code on production servers.
- Always test changes in more than one browser.
- Be extra careful when using an alternate editor or simply stick to one editor
Tuesday, September 20, 2005
Geeky Friday: Complaints about gaim (and sourceforge)
Gaim works well most of the time, but once every 2-3 months, one of the major IM services will tweak something and non-official clients (such as gaim) will not work. If such a tweak is persistent, the gaim team will usually push out a fix within a few days.
Just some thoughts. My complaints all revolve around communication about what's going on. I'm ranting today because I've not been able to log in to AIM for the past couple days -- with an exception late last night. Maybe AIM changed something, maybe the server I connect to is overloaded (and gaim doesn't know how to switch), maybe it's something else. I'd like to know more.
The gaim team could post something on the blog-style front page of their site. But, perhaps I'm in a small minority of gaim users who are experiencing this problem. It would be nice to communicate with other members of this small minority to discuss. There's a gaim forum on the sourceforge project page but it's slow and the user interface is severely dated. I could file a bug report, but similarly, the user interface is lousy and I have a difficult time getting a sourceforge login cookie to stick around from the time I log in to the time I get to the page to file a ticket. (I would try to tell sourceforge about this problem, but that would involve filing a bug report using the same system).
It would be relatively easy for the gaim team to address these sort of problems with freely available services. There are many options for improved forum software any one of which would be easy for the gaim team to install. But forumer offers "100% free hosting" for IPB and phpBB -- I'm not familiar with IPB, but I know that phpBB would be a significant improvement over the sourceforge forum.
For bug tracking, I've been pleased with Atlassian's JIRA. Atlassian has a nice progressive view towards open source projects -- providing their software at no cost and, in some cases, hosting or maintaining the software for the project.
Thursday, September 08, 2005
Hilarious Domain Name Mispronouncings
Tuesday, August 30, 2005
A man who doesn't like his phone
Monday, August 08, 2005
Would you trust his directions?
Friday, August 05, 2005
Geeky Friday: Extended bash completion
It does seemingly obvious things, such as offering known host names when using ssh or sftp (taken from config and known_hosts files in ~/.ssh) or offering the valid command options that follow the cvs command (e.g. commit, update, log, etc.). Here's a big list of what commands it will expand arguments for.
I think people who do more systems administration than I do will probably benefit more than I will, but at least I can now reduce how many times cvs complains about the invalid command "cvs udpate".
According to its page at freshmeat.net this has been around since 2001. As distributed for cygwin, the file is now nearly 9000 lines long plus another 1700 lines in an associated subdirectory (bash_completion.d). This seems a tad monolithic. I think it'd make sense for these completion functions to be split up and packaged along with the executable itself. This is an extension of what is currently done. Regardless of the installation packaging system (rpm or apt on linux, fink on mac, cygwin for cygwin), the package already contains not just the executable, but also configuration files, manual pages, other documentation, and often custom shell settings to be placed in /etc/profile.d -- perhaps these completions should just be added into the files placed in profile.d since the contents are just bash commands which add information to the current session.
Tuesday, August 02, 2005
Did Hell Freeze Over?
This mouse looks cool. It all makes sense now. Apple didn't want to release just another two-button mouse with a scroll wheel. They've done quite a bit more. Update: Russell Beattie has a hands-on review of the Mighty Mouse.