I "have" a Facebook account, same with Twitter, Flickr, the various IM services, Wave, and Meetup accounts, I leave various IRC servers open, heck I recently signed up for Linked In. And of course I have this blog.

But I have a strong disuse of most of them.

• Twitter: My Twitter is sparsely used. Posting wise I consider it a technical outlet, or a connection to the public internet, I generally avoid posting personal things to it. I use it more like a business might use it than the random breakfast posting tweeter. In the end I don't post much.
• Facebook: I vehemently guard my Facebook friends list. My Facebook friends list is only for people I have a real personal connection of some sort to. I reject friends of family members I don't have something close to a personal dialogue with. I reject random people who make friend requests. I reject people who "might" be distant relatives but I don't remember ever actively talking to. Generally I try to avoid accepting anyone who might end up as a 'vanity' friend — someone who I'll probably never really talk to and just exist as a entry in a list of supposed "Friends". I consider Facebook a "private" social medium, I only connect to people I personally know, not people I connect with over the internet focused around topics. Only having around 20 people on my friends list is on purpose, the idea of having that list grow to 100+ disgusts me. In the end as well, I don't have much reason to open it up, and just wait for any e-mail notification about messages to pop in.
• Flickr: I signed up to twitter because I thought that some of my photo galleries like my work gallery and projects didn't fit as Facebook galleries. I don't really like Facebook, And like I just mentioned I consider it "private", so it didn't make sense to keep them on Facebook. However after some use of Flickr I've been looking into setting up a private app just for posting image galleries of my own.
• LinkedIn: I'm not exactly looking for a job, but after some thought I decided I should probably start paying attention to the world of networking with people that open up potential job opportunities. So I ended up signing up on LinkedIn. Hasn't been that long so I haven't done much with it of course.

Despite scarcely using my social media accounts I "do" have a draw to being social, but none of the social media mediums seam to fit.

The state of most uses of css3's border-radius around the web has been bothering me for awhile now. Though now I've found something else to be annoyed at.

The earliest common use of border-radius was -moz-border-radius in Gecko based browsers. Later on the WebKit implementation came into common play. When and where things were actually implemented isn't really important, that's just the order that people started to know about them as common knowledge.

As a result there are plenty of websites around which are still using out of date css that only support Gecko and WebKit based browsers, or in some cases support nothing but Gecko based browsers. This is somewhat irritating considering nearly every browser — at least in their most recent versions — support border-radius, and by using incorrect css they omit support for browsers that actually "DO" have a border-radius implementation. Like Konqueror, Opera, and IE9.

I've made some some small updates to my site, namely I updated the personal and portfolio icons and added a link to my new Flickr account into the personal section of my website.

The new personal icon is the same Umbrellow sprite featured in the personal area of my site.

The new portfolio icon is a drawing of a lizard at a computer. The computer part of course makes perfect sense, but why a lizard? That comes from how I "envy lizards and their heat lamps" when I'm in the office at work. The office isn't exactly ever warm, and I almost feel like a warm-cold-blooded creature, I don't like the cold, and I enjoy bathing in the heat.

Back on HTML5, section 4.10.7.1.13 defines a number state for inputs. The traditional input for numbers you see inside of OS is a spinbox, a text box containing a number with a set of up and down arrows beside it which allow you to use your mouse to change the input (iirc some OS even let you use the up and down arrow keys).

So far there are two implementations of the number input, in Opera in and WebKit.

Opera gives you a spinner input and lets you use the arrow keys, and in the iPhone OS WebKit optimises the keyboard by placing the numbers at the default top row (why they don't give you one of those nice fancy slot machine style number inputs they worked so hard on is beyond me).

While I was working on version 3 of Kommonwealth I got back to a part of our interface which makes use of live input events (ie: Events that fire as you type into the input) to offer a preview before the onchange event is used to actually change the data by sending an ajax post to the server.

For those who haven't heard of the oninput event, it's part of the html5 spec. You know those older ui parts such as autocomplete features and whatnot. The normal way of making these work is to manually subscribe to keydown and keyup events, and sometimes even use a timer for long inputs. Why? Because onchange only fires after you blur the input (that is what it is speced for and meant to do) and there was no event that would fire while typing was being done, so the only easy way to do it was to subscribe to keyboard events. Of course this method only applied to text inputs. The oninput event is basically an event in html5 which takes care of it. It works similarly to onchange, but instead of firing on blur it fires while you're typing into the input. This has an extra benefit in compliant browsers that like onchange it is only supposed to fire when the data has actually changed (ie: typing asdf then pasting asdf to replace it shouldn't fire).

Well of course this would be like all other html5 features incomplete browser support, the html5 spec doesn't list browser support in any browser. But that's where user code comes into play. We create code to support it manually in browsers that don't support it, and allow browsers that do support it to take over and handle it natively.