Another use for feed licenses: Splogicide

Doc Searls just changed his blog license to Attribution-NonCommercial-ShareAlike 2.5... in order to clearly deny splogs reblogging rights to his content.  Interesting, though I think there may be some unintended fallout.  But there are some cool applications for this.  What if someone built a tool to make it easy to find such copy right violators (academics use these tools to find plagarism)? With an accompanying service to aggregate complaints and, when they reach a sufficiently remunerative level, send attack lawyers after sploggers.

Update: The collective intelligence of the blogosphere is a mighty thing.  In a comment below, Doc points at an open source plagarism detector from UCSB (my alma mater) that already does Internet searches.  Hmmm.... 

AOL's Open Source Contributions to Dojo

It's nice to see something your team has worked on being put to good use.  In addition to other things, we open sourced the JavaScript Compiler tool my group has used internally for several years.  (It's actually more of a linker and compressor than a compiler since of course the output is still JavaScript.)  We're also contributing new code to Dojo, including a pretty cool cross domain XML request mechanism.

Sam Ruby presents "Teenage Mutant CyberSurfers"

This afternoon, Sam Ruby was nice enough to reprise a version of his recent talk at AOL Silicon Valley.  There's a real independent convergence between Sam's observations and predictions and the fictional world described in Vernor Vinge's Rainbows End.  Which as I understand Sam is just now reading :).

Update:  The audio is up on our podcast feed already!

AOL Pictures Beta and woohoo

In conjunction with the new Pictures Beta, there's a cool tool called woohoo which displays a an AIMPages picture gallery in a widget, embeddable anywhere.  Fun stuff...  for example:

Feeds Best Practices

The slides from my RSS/Atom Feeds Best Practices talk from lunch today are up now.  There was a good discussion afterwards and hopefully we'll put up a podcast. I'm more convinced than ever that the key to a successful presentation is: free food.

URL format change for Journals

One of the recent changes this week in Journals is an update to the format of our entry URLs.  We're essentially adding the entry date and title to the URL, for example:

.../entries/2006/07/13/rest-and-the-authorization-header/1354

So anyone who may be parsing our URLs -- be aware that the format has changed :).  We will, however, do a permanent redirect from the old URLs to the new ones.

REST and the Authorization: Header

Talking to lots of people about identity, mashups, web services, and sustainability of the mashup ecology today at Mashup Camp.  I'm wondering why LID apparently is using a new X- header for passing pointers to authentication information rather than re-using the existing extensible Authorization: header.  Both GData and Amazon Web Services  allow Authorization: as at least one option in their REST interfaces:

Authorization: GoogleLogin auth ...
Authorization: AWS ...

I know that GData uses 401 Unauthorized and WWW-Authenticate: challenge headers and I'm going to assume that AWS does too:

WWW-Authenticate: AuthSub realm="https://www.google.com/accounts/AuthSubRequest" 

So, existing services are using the RFC 2617 framework; it's working for them; why not build on top of that instead of inventing new headers?