Stay tuned folks! I’m beginning to get the blogging bug again and I’m going to start posting very useful information about our industry, our beloved web development.
I’ll display proper techniques I’ve learned over the years for most things concerning front end development. This ranges from semantic mark up to css to my favorite JavaScript :)
So for the last two days I haven’t been able to sign onto AIM from home. I’m a Pidgin chat client user so this only applies to those that are as well. If you’ve been receiving the following message while trying to connect “Received unexpected response from http://api.oscar.aol.com/aim/startOSCARSession“ it means your connection issues are caused by an invalid SSL certificate and you’ll have to disabled SSL for the time being. Read more about it here on Pidgin’s support site: Pidgin connection problem Here’s a screenshot of what to look for: 
Google broke my (and many other’s) #1 rule …fade in menus…really??? html onmousemove=“google&&google.fade&&google.fade()” This isn’t going to be anything you can really learn from but I’m pretty surprised at Google for implementing something that goes against web standards. I expected more from them…it’s friggin’ GOOGLE!! lol I personally don’t like the fade in functionality of their home page and I’m sure some people think it’s very cool but what’s the real point of it? I actually hate it because I do have to wait for the menu to load and sometimes it doesn’t kick in for a second or two. So if you want to take anything away from this I suppose it would be what web enthusiasts have been saying for nearly half a decade…less is more.