Yep, I joined Twitter. I held out for a while, not sure I wanted to join in all the 140 character fun. But after just observing others’ posts for a few weeks, I found I understood why tweeters are tweeting everywhere everyday. Number one, it’s a great digest for information. Following some of my favorite magazines and news sources, you get links to the latest and greatest without having to search. The information just comes to you. And it’s fun! Following your family and friends lets you connect without the clutter and distraction.

I am surprised, however, that there hasn’t been more hullabaloo about this categorization aspect of Circles. I thought for sure we’d be hearing people complaining that this “putting people into circles” business (insert whiny voice here) is unfair and will hurt people’s feelings because everyone should be equal. I’m glad there hasn’t been such comments, or at least I haven’t seen any, because I think this feature is needed. When it comes to social groups, we all have people we’re closer to and not so close to. People we want to share more personal things with and those that we just want to say “hey!” to every now and then. I think Google+’s Circles reflects more realistically our offline social lives.

If you agree, ask around and demand an invite from a pal. It’ll be interesting to see how Google+ progresses and grows over the next few months and if any Facebookers will jump ship for the new web hotness or just double up their social worlds. I doubt the Madelaine Zammits of the web will be coming aboard, but I’ve definitely tested the waters and am feeling much more relaxed. Heck, even the Zuck-man himself took a dip. +1 Google, +1.

The kses file basically tells WordPress which HTML elements are safe for blog post entries. Anything other than what’s defined here will be torn asunder. (See Otto’s post for a more detailed description.) Many queries to the all powerful Google resulted in this post by Rhys Burnie for a solution to my quandary. Rhys’ code basically creates an addendum to the allowed HTML elements defined in the kses file. The additional elements and their attributes are then plopped into the filter used for the WordPress editor, called tinyMCE, before it’s initialized. The additional PHP code can then be added to your theme’s functions.php file, a quick FTP upload, and you’re off! Pretty slick, eh?

I found, however, that Rhys’ element list wasn’t quite up to date, most likely because the HTML5 spec has changed since the post was made last year. I added some additional element attributes, particularly for the video tag. You can see the attributes for each element noted by [#|attribute|attribute|etc....] on the various lines. Here’s the code:

//extending valid elements
function extend_valid_html5($init) {
	//Standard attributes
	$atts = 'role|accesskey|class|contenteditable|contextmenu|dir|draggable|hidden|id|item|itemprop|lang|spellcheck|style|subject|tabindex|title';
	$html5Elements = array(
		'article[#|cite|pubdate]',
		'aside[#]',
		'audio[#]',
		'canvas[#]',
		'command[#]',
		'datalist[#]',
		'details[#]',
		'figure[#]',
		'figcaption[#]',
		'footer[#]',
		'header[#]',
		'hgroup[#]',
		'mark[#]',
		'meter[#]',
		'nav[#]',
		'output[#]',
		'progress[#]',
		'section[#]',
		'summary[#]',
		'time[#|datetime]',
		'video[#|src|poster|autoplay|loop|controls|width|height|type|style|id|preload]',
		'param[#|name|value]',
		'source[#|src|type]'
	);
	if(!isset($init['extended_valid_elements'])) {
		$init['extended_valid_elements'] = '';
	}
	$init['extended_valid_elements'] .= str_replace('#',$atts,implode(',',$html5Elements));
	return $init;
}
add_filter('tiny_mce_before_init', 'extend_valid_html5');

Rhys also gives mention to Nick Gallagher’s approach to solve the HTML5 element issue, which I also tried, but found the kses modification technique to work more successfully. An additional note, if you plan on giving the whole thing a whirl: I found that even by adding all of the attributes for the video tag above, the editor was still stripping out the controls and preload attributes. By HTML5 definition, so far, these attributes can be used by declaration only, as follows: <video controls width=”640″ height=”360″ preload>. But the gosh darn editor stripped out these anyway. Trial and error found that if you add these declarations with values set: <video controls=”true” width=”640″ height=”360″ preload=”auto”>, everything stays put :) An additional additional note, don’t forget to update your doctype to HTML5 :P

For more info on the video tag, check out Dive into HTML5 and Camen Design.

Sooo, I finally beat the system. And I feel great. And now I can post with HTML5 video galore and be accessible all around and everyone can enjoy my multimedia-tastic posts with the browser of his or her choice. Without silly Flash. You can use Chrome. Or Safari. Or Firefox. Or even Opera. I guess you can use IE too. I’m falling back to a Flash player if you’re still using that silly browser. Enjoy.

(At least until WordPress releases an update that fixes the problem in core and makes this fix obsolete  :P, which according to their bug tracker, will be the case. ;)