I am in utter disbelief at the audacious lies of Sen. Lindsay Graham, who dared the other day to claim President Obama has been “AWOL” on the matter of the economic stimulus plan. He’s been all over trying to make this thing happen, and now he’s using the Internet (finally, a president who gets it) to help make his case:
Yes, our new president is using YouTube to get his message out. Power to the people!
Not a Creed fan here. Apparently this is one of the latest web memes that I’m about six months late to discovering. But it doesn’t matter. It’s still freakin’ hilarious. And for what it’s worth, I have Cake to thank for tipping me off to it.
YouTube is worlds apart from the likes of MySpace (*shudder*) when it comes to good code, but like most massively influential sites, they don’t really seem to care that much if their code validates, and even less if the code they provide webmasters for embedding content in their own sites does.
Frankly, I usually don’t care that much about validation either. I worked in this field for too many years when no validators even existed, and I’ve always taken the pragmatic approach: make it look and work the same, more or less, in all reasonably recent versions of Internet Explorer and Netscape (with Firefox and Safari having replaced Netscape over the past few years), and be done with it.
But I still have to admit that it’s a bit embarrassing that the “Valid XHTML” link (which appears in the Meta sidebar by default in WordPress) proves just how not valid my XHTML really is. I checked it today and was shocked to find 76 errors. I was relieved, however, when I dug in and discovered that only three of those errors had been my own. I had nested a <ul> inside a <span> (which I honestly didn’t even realize was a mistake, although I understand why it’s wrong, and it was easy enough to change from <span> to the valid <div> without any visible difference), and I had omitted alt attributes from a pair of images that don’t need to be identified by page readers anyway (and would probably be better off being worked into the CSS somehow).
These were pretty minor errors, if I do say so myself. 67 of the remaining 73 errors originated in cut-and-paste code blocks I got from PayPal and LinkShare (the latter of which I deal with only very reluctantly because they provide the mechanism for Apple’s iTunes affiliate program). What a surprise that the code from these sources looks like it was written by a tech support grunt in 1996 (in other words, by me in 1996)!
These were easy enough to fix, as well. I’ll just need to remember to fix them again if I ever change the code in those ad blocks, which I’m sure I will. The final 6 errors were the result of a YouTube video embedded in one of my blog posts. Ah yes, the age-old <object> vs. <embed> conundrum. I’ve always hated <object> because it seems unnecessarily complicated, with a slew of nested <param> tags that could just as easily have been attributes of the tag itself (although I suppose the point was to allow new parameters to be added without having to add support for new attributes in the DTD); plus it reeks of Microsoft’s platform-dependent ActiveX crapfest. I especially loathe the presence of, and need to hunt down, a ridiculously long, completely arbitrary clsid string representing the file format of the embedded file. (What’s wrong with a freakin’ MIME type?)
Unfortunately, the cleaner and more straightforward <embed> has never been part of any HTML specification, so it doesn’t validate.
Now it appears that there’s a solution to embedding YouTube videos in an XHTML-compliant way. Huzzah! But that means I’ll have to go back through all of my posts that have YouTube videos in them (which is a surprisingly large number) and fix them. It should be easy enough to hit them all at once with a well-constructed SQL query; I just need to study the pattern and do it. In fact, if I’d spent the last 15 minutes studying the problem instead of just complaining about it, I’d probably be done already.
The other night I revealed to my mom, for the first time (and 30 years after the fact), the true, bizarre nature of the things I was exposed to multiple times per day on Sesame Street; in particular the Yellow Submarine-inspired cartoon about the lost kid and the yo-yo master. Along the way through the treasure trove of old clips YouTube has to offer, I found this other long-forgotten favorite. I think this can probably be viewed as a sequel to the more famous “Mahna Mahna,” but as a kid I liked it even more. Enjoy!
While I’m at it, there are, of course, many more amusing and/or disturbing vintage Sesame Street clips on YouTube, such as…
And this (disturbing):
And finally, while certainly not as iconic as the Pinball Number Count series, there was this other counting series that I also remember quite well. (I suppose the wizard opening his robes to reveal another smaller self within does fall somewhat into the “disturbing” category… to say nothing of the trenchcoated flashers at the end!):