When you have signed up you can invite three more friends to like/diss. Currently, you also get five more invitations for your friends for each bug you find and report.

Each invitation code below can only be used once, first come, first served. To signup, go to:

http://www.likediss.com/users/register/

Invitations codes (if one is already used, try another one):

bwhaxxbdqzu
nfehbxjqnk
dajlddhbzrw
zjoeieusbmdkk
isglumjtvtgyd
yrqadfuxbtu
leyyeozoqm
icfoqpqijoz
xelwdilaocdr
yfbdviytcbj
gjlxipmii
fzjjvrerz
xvncibndzega
pxalazwqucw
zmxgskisuas
vrjxolpacih
wzspfktfw
nwwguctqa
rgzpqeovkjlu
vyhfaazqnm

The upside is that you can get fancy things like desktop application like widgets like sortable and re-sizable tables, expanding trees, and tabs with Ajax XHR data bindings up in a short time without writing much JS code. The downside is that you get a lot of code to send over the network. Although the library has whitespace compressed production files and fragments you can use if you only use some of the widgets, you get pretty soon up to 500kb or 1mb of client side scripts and style sheets. On the other hand, if you compare it to the other major high level web UI framework Dojo Toolkit you get a much more stable and standards bases solution that don’t crash and ordinary browser like Dojo does.

It is obvious that the YUI framework takes the web one step further down the road to replace the rich user interface desktop application without losing the interaction and user experience. That being said, we will not use it on our social network site because of the files size overhead, but continue to use PrototypeJS and to some extent Scriptaculous. But if I were about to build a web based application for an organizations internal use or for a stock broker firm, I would definitely give YUI a chance.

What was the problem? When the Scriptaculous autocompleter only get one item to display it is already selected and it just to (1) hit the tab (2) hit enter or (3) click on it with the mouse to have it populated in the form field. But Bob was really eager and said that he wanted to select the suggested tag with the arrow keys (although it was already selected and marked visually as such) and that he had committed usability testing using his wife and that she couldn’t manage the suggestion menu when there was a single match.

The Script.aculo.us behavior has already been a standard when it comes to the autocompleter and it works the same on other suggestion lists like the one in Google Bookmarks.

Another thing about the autocompletion, it get’s kind of confusing when there is a short delay in the network. When you have typed a few characters, up comes a suggestion based on the very first chars you typed.

I wonder what the average user can tell a server based auto suggestion list from the one populated by the browser that suggests strings based on what she typed before in a field like that.

Speaking of autocompletion, what does you guys think of the autocomplete attribute and how do you handle it when trying to be XHTML Strict valid?

I guess you’re fast to reply that a site needs an identity and a clear owner. You’re probably right, but who doesn’t get tired of those page headers containing a logo, a search field, some log in/log out stuff and a top navigation bar? UI standards are always good because the users knows them and knows where to look for things like navigation. But it feels like the Web 2.0, community and social network sites hasn’t come up with much news for mastheads. Look at digg, del.icio.us, facebook, twitter, and flickr. Maybe it is time for a ribbon paradigm shift for the web too?