Seems Network Solutions runs a year early:
Domain Name: ALISTAPART.COM
Registrar: NETWORK SOLUTIONS, LLC.
Updated Date: 13-may-2008
Creation Date: 07-may-1998
Expiration Date: 06-may-2009

I wonder how anyone can still trust this company. Time to move to a different registrar i'd say.

Once again, Twitter.com is in maintenance-mode. Hopefully -- as usually -- for the win.

There's one thing i realized which really puzzles me. It is the way, they serve their temporary maintenance page (pictured in parts in the screenshot to the left).

This time (i haven't checked this during any of their downtimes before), they publish their temporary page in an extremely stupid way:
Twitter is serving a 404 status for every URL on twitter.com. The page you see during maintenance is a customized 404 "Not Found" error page. The 404 HTTP status means, that the url you tried to access doesn't exist and you should never use this url again, as it is bogus. This is not very clever. Now you can argue how important a proper google-index for twitter.com is, but even if you'd not care about google (and any other search engine) throwing every twitter-page out of it's index due to the 404 the crawler gets with every request, it still is wrong. HTTP statuses are there for a reason and serving a 404 during maintenance is not what the 404 status was meant to be used for.

The proper way to handle this would be to do a temporary redirect by serving a 307 or, even better, simply serve the maintenance page with a 503 status, which is the perfect fit for a maintenance. HTTP Status 503 stands for "Service Unavailable" which is exactly what is happening during a maintenance break.

Serving a 503 would deal with search engines nicely and clients like Twitterrific could also nicely parse it and inform the user correctly. For instance hahlo.com is momentarily just serving black frames, making their users believe something is wrong with hahlo. Pockettweets on my iPhone also confuses the user as Mobile Safari is simply alerting the user about too many redirects.

Hopefully someone from twitter will read this and not make the same mistake again in the future.

Since i use twitter, i modified his script to post alerts and extended the functionality a bit. The script cureently only checks webservers via HEAD requests. If a host does not respond, it posts an alert to a given Twitter account, remembers the host and will post a host-up notification to twitter, should the host come up again.

The benefit of this is, that you can get Tweets via SMS providing you a nice 24/7 monitoring solution. In order to receive SMS alerts, you basically need 2 twitter accounts. One where you send the alerts to and a second one which you use to follow the first one in order to receive notifications vis SMS (as you can't receive notifications from your own account, this is not possible using just one account).

The script is usually run by cron. To run it, you need Perl and the Perl LWP module as well as a configuratio-file which is described in the header of the perl-script.

Download checkandtwitter.pl V 0.2 here and enjoy.

Here's my little christmas gift to all of you having either Saft or any SIMBL PlugIns installed and want to work with the WebKit nightly bulilds without crashing or having to manually disable the above mentioned PlugIns:

OpenWebKit

is a simple AppleScript App, that just does the following:

• Rename /Library/InputManagers to /Library/xInputManagers
• Start /Applications/WebKit (the nightly build you have installed)
• Rename /Library/xInputManagers back to /Library/InputManagers

Installation notes:
Download, unpack and doubleclick.

Note: as this script needs to rename a folder in /Library, it will only work when you have Admin rights for your Mac!

Tada! No more hassle.

Enjoy!

PS: i wonder why the nightlies do not just already disable all input managers so we don't have to.

Jacob Cord wrote a very nice little converter which takes a tab-text file, exported out of your Google Analytics Geo Map Report and converts it to a KML file which you can import into Google Earth.

The output of the original script didn't look all that exciting, so i modified it a little to produce some awesome visualisation of website traffic.

Just read an interesting Article over at ALA which also mentions new techology like AJAX and the like being too much hyped and immediately being used without thinking about the user and his needs first.

Let's make a test. I recently developed something at work, where many would see AJAX written all over it. Look at the movie below:

Is this using AJAX? Let me know in the comments (sorry, TypeKey login required now due to crazy comment spam)!

BTW: the above is a live recording right out of my browser window. No editing involved other than scaling the movie down to 60%.

Dear Webmaster,

surely you are having a contact form somewhere on your site where i can contact you by providing my Address, Phone and such. It'll probably look something like this:

Please be aware that many countries do not need any States in a postal address. In fact, in many countries it is totally uncommon to have a state included in a postal address - some don't even have any states at all.

So please, please, please do not make the STATE fields on your contact forms mandatory. If you're clever, you can decide on making them mandatory depending on the Country chosen. But please, once i selected Germany or such (you'd have to research that country-list on your own - i was to lazy to research it and only make states mandatory IF USA was selected as country) do not make the State Field mandatory!

Oh, and while we're at it: Our phone numbers are also formatted differently and might have a different total length, so don't force us to format them like 123-123-1234 (German area codes might have 4 to 5 digits for example).

Thanks so much for not being ignorant about foreign countries!

This is driving me mad for almost a decade now.

I hope someone has a suggestion to get around one of the nasty "features" coming from Redmond:

Internet Explorer on Windows has some funny logic implemented to add some PADDING to SUBMIT-Buttons (<input type=Submit>) of forms. The Longer the content/text of the VALUE tag is, the more PADDING it adds automagically. Thus we have real ugly looking form buttons on our pages which take up valuable space.
This padding can not (to my knowledge) be set using CSS.

I'd appreciate if anyone knowing of a workaround to get rid of the padding IE is adding could let me know.

Look at the grey buttons in the screenshot below (click on the image for larger display) to get a picture of what i am talking about: