OpenID & AOL

Christian Decker wrote this in the early evening:
As I posted earlier I’m really excited to see that OpenID is started getting ever more popular. It comes to no surprise after Microsoft announcing their support for OpenID that other big players jump on the train. This is AOL’s turn:
It’s not really a secret that AOL has been experimenting with OpenID.  As I’ve said, I think that user-centric, interoperable identity is hugely important to enable the social experiences we’re trying to provide.  This is a work in progress, but things are coming along thanks to our authentication team’s diligent effort.  Here’s where we are today:
  • Every AOL/AIM user now has at least one OpenID URI, http://openid.aol.com/<sn>.
  • This experimental OpenID 1.1 Provider service is available now and we are conducting compatibility tests.
  • We’re working with OpenID relying parties to resolve compatibility issues.
  • Our blogging platform has enabled basic OpenID 1.1 in beta, so every beta blog URI is also a basic OpenID identifier.  (No Yadis yet.)
  • We don’t yet accept OpenID identities within our products as a relying party, but we’re actively working on it.  That roll-out is likely to be gradual.
  • We are tracking the OpenID 2.0 standardization effort and plan to support it after it becomes final.
I hope that they accept OpenIDs for their products soon, as it obviously increases the reachability.

Web 2.0, a (not so) serious comparison

Christian Decker wrote this around lunchtime:
Web 2.0 is the thing going on right now on the web and everytbody is asking, “what the heck is it?”, so Jeff Zeldman has put together a nice comparison between Web 1.0 and Web 2.0: Clearly “Web 2.0″ means different things to different journalists on different days. Mostly it means nothing—except a bigger paycheck. But let’s simplify what The Economist is saying: Web 1.0: AOL buys Time Warner. Web 2.0: Google buys YouTube. Put another way: Web 1.0: New media company buys old media company. Web 2.0: New media company buys new media company. If we’re stuck with this meaningless Web 2.0 label, let’s at least have some fun with it. Here’s my new game. I’ll start, you finish: Web 1.0: Joshua Davis on the cover of Art News. Web 2.0: 37signals on the cover of Forbes. Web 1.0: Users create the content (Slashdot). Web 2.0: Users create the content (Flickr). Web 1.0: Crap sites on Geocities. Web 2.0: Crap sites on MySpace. Web 1.0: Writing. Web 2.0: Rating. Web 1.0: Karma Points. Web 2.0: Diggs. Web 1.0: Cool Site of the Day. Web 2.0: Technorati.com. Web 1.0: Tags. Web 2.0: “Tags.” Web 1.0: Bookmarking. Web 2.0: Bookmark sharing. Web 1.0: Pointless Flash widgets. Web 2.0: Pointless “Ajax” widgets. And the commenters go on: Web 1.0: 12px h2 Web 2.0: 51px h2 Web 1.0: Animated gif Web 2.0: Badges Web 1.0: Arial Web 2.0: Arial Rounded/Georgia Web 1.0: Bloated Table Code Web 2.0: Divitis Web 1.0 : Deserted blogs on Blogger Web 2.0 : Deserted blogs on Wordpress Web 1.0 : The past Web 2.0 : The present Web 3.0 : The future Web 1.0: “Under Construction” Web 2.0: “Beta” So are you Web 2.0 or still Web 1.0? :D

JS Linker in Dojo Toolkit

Christian Decker wrote this mid-morning:

AOL has been very generous by donating code for the JS Linker for Dojo:

The JavaScript source code can be represented in different levels of granularity. The JavaScript Linker uses the Abstract Syntax Trees (ASTs) representation, which represents the lowest level of detail, to model the source code. One of the main task for this project was to write a JavaCC compatible grammar that strictly follows the ECMA Specification. JavaCC uses this grammar to build a custom parser than can read and analyze the JavaScript source, which in turn, is used to build the JavaScript Linker.

What this means to Alex Russell:

This is the holy grail of JavaScript optimization: removing “dead” code. Dojo already provides a package system to help prevent including too much and a build-time compressor to help reduce the size on the wire of what you do need, but the linker does all of this one better by analyzing the application and figuring out what functions are entirely unused.

JavaScript has some unique issues with packaging, and this will help Dojo coders out a lot.



Technorati Tags: , ,