Evan sees hosting fees paid by bloggers are the first revenue stream and selling audio as the second revenue stream-look out Audible! He talked about how much money Audible makes and his eyes were most opened when discussed that. Clearly that is the business here.

He also talked about letting advertisers come to the site and record commercials then pay to place them on shows. Neat idea, but that's not going to happen-advertisers are discerning and don't want sloppy ads. He also mentioned podcast hosts reading commercials on behalf of sponsors based on copy... that's possible. Getting advertisers for highly-branded content is hard enough but getting them to sponsors a large swath of random podcasts.

Seems the business is build this to a certain point and sell it to Google, Yahoo, etc. The hosting model is not great, that's a commodity business. The premium content is really the best play, but if you succeed at making it easy for folks to create content there might be less of a market for premium content (why pay).

He mentioned having a library of songs that you could legally pay for and play on your podcast some day.

He said an GMAIL invite style rollout shortly.

He talked about making walking tour MP3 files, or "the sound of the day." Comedy he sees as big. He like the odd stuff, the stuff that doesn't exist already. 

He starts telling the story of H.G. Wells' book " The Country of the Blind" passed on a village where everyone is blind and Nunez a non-blind visitor goes to a doctor that wants to remove his eyes.

Stop! Remix is nothing new. That's how cultures were created. Apple remixed, Bill Clinton remixed, we all do it. When we watch Michael Moore's film-for example-and thell our friends whether we loved it or hated it. That's remixing.

In world history remixing was never regulated. Remixing needs to be free; the ordinary ways of remixing. Ordinary ways are "word" and remixing text, writing is free.

What when the technology of remix changes? Do the freedoms change as well? He plays an audio snippet of the Grey Album. He mentions Tarnation, a film made with a budget of $218 that wowed Cannes. Follows some videos remixing Fox News and President Bush (liberal), John Kerry (conservative). The audience goes crazy with the video remix of Bush and Blair singing "My Endless Love". Always funny to watch it. "That's video creativity".

Not broadcast or NYT democracy but popular democracy. The question come back on screen: What when the technology of remix changes? Existing laws conflict with technology, laws need to be reformed (remixed?). Reform the law or reform the technology. Just like H.G. Wells story the powers to be want to reform technology, remove its  eyes.

1. Let's call "piracy" "piracy". Let's call "piracy" wrong. (Notice the quotes.)

2. Teach how powerful the technology is.

3. Demand changes in the law. Not a call for the end of intelectual property.

4. Punish. Defend and oppose the law because it will destroy our technology.

is Yahoo's resident MySQL Geek and he explains that the developer community requested Yahoo! to expose their search services. They saw it as a way to encourage 3rd party innovation. The initial goals were to keep it simple, collect feedback and create a low barrier to entry.

The Developer Community contains the SDK, a wiki, a blog, and general documentation of the API-which offers search on Web, News, Image, Video, Local plus a new feature of contextual search.

The architecture is based on backend clusters (for web, image, video, etc.) that are accessed by the application via a XML proxy developed in PHP. The proxy cleans up the XML results coming from the backend already existing internally to Yahoo! PHP is the de facto language of choice at Yahoo!

There's a restriction of 5,000 queries/day/service/IP - there's no developer token. So if you distribute your app each install wiill have its own limit.

The usual debate to decide for REST or SOAP also happened at Yahoo! "REST is 80% of the usage and SOAP is 80% of the support burden"-so REST was the choice. If there's community demand for SOAP they might consider implement it too.

Some cool apps were already created by 3rd parties and can be found here.

One distinction: del.icio.us vs wikipedia = indiv space vs shared space

Del.icio.us tags= a document description & associated behaviors or additional context around it

del.icio.us- why tag, what to tag, how to tag? Key idea- people tag for different reasons, some to help themselves find stuff again, sometimes to help other people find their stuff, sometimes to help organize groups, behaviours, or context around a given concept. 

tags on flickr to create groups of photos

Audience question: can we create meta- meta tags to share tag info acros across different services?  Response: the purpose of the tags is not always the same and therefore it is difficult to normalize tags across different services. 

how to give users feedback on how to effectively tag?  what feedback loops can be provided to boost learning?  Flickr- no such thing as a bad tag, Wikipedia- community polices innappropriate tags, Del- shows your tags, top/popular tags, intersection of tags w/others. Del.icio.us- don't interfere too much by imposing restrictions as users won't be able to find the stuff they tag.

Shirky- user/time are new axes for classification and this creates a need for tags and taggers to understand context. 

Del- expert-generated taxonomies don't pay attention to what people are trying to do.  Del tags are for people to help them find stuff, not to necessarily describe things in the abstracts

• Quality control

• Author fatigue

Solution to these problems: wikicities.com.  Solves author fatigue problem by creating a community that is topic-focused buyt not dependent on any one author.  Solves quality control thru the wiki peer-review process.

Organization by the Community: free form wiki software lets the community decide how to enforce community mores. 

Conclusion- wikis are a major "social innovation" according to Wales

Justin Chapweske of Onion Networks starts by talking about the HTTP protocol how it has been used since the days of Netscape 1.0  and proposes a remix.  That protocol problems today are more evident as larger data files are being transmited over the Internet (e.g contents of a DVD).  The idea is to use a swarming technique, instead of just throwing more resources (read $$$) to solve the problem. Swarmstreaming is a concept is similar to BitTorrent that breaks up a file and transmits is to various clients that transmit their pieces to each other.

Today's first presentation was from Neil Gershenfeld, from the Center for Bits and Atoms, MIT which is a group of 20 scientists incuding biologists, chemists, physicists, mathematicians, various kinds of engineers.

The state-of-the-art fabrication is not at 10 billion chip plant but at the ribosome. That's the insight. The ribosome is the living proof for the digitization of fabrication. Computers not controlling tools but computers as tools.

He shows some of the students that first applied to attend the class on the subject of personal fabrication (How to Make Almost Anything). Their projects are fun stuff stuff like the Screambody, Interpet Explorer, Defensive Dressing and an alarm clock that you have to wrestle with to prove you're awake. Some practical examples are the personal fabrication labs created in places like Ghana, India.

His new book on the subject is  FAB The Coming Revolution on Your Desktop.

Here's a recent article about Neil's work: How to make (almost) anything

• The customer is the only thing that counts

• Question your assumptions

• Learn from Chaos

• Let go of control

• Turn scale into advantage

• The switch to document/literal

• Stateless design

• The developer reference guide

• Developer tokens

• Thorough interop testing

• Private beta period

• Excellent tech support group

• Bulk methods

Things that went wrong:

• The switch to document/literal

• Lack of common data model

• Dates and time zones

• No gzip encoding wroking right now

• Quota confusion and anxiety

• No developer sandbox

• SSL (hard to debug, slow)

He is recounting the problems that Dr. Kurt Goedel faced trying to emigrate back into the USA during the early 1940's.  Goedel was one of the greatest mathematicians of the 20th century but he was also a very paranoid fellow, apparently. 

In any event, Goedel's work led to Turing which led to Von Neumann's work on computing.  Von Neuman is credited as one of the creators of modern computing. 

George has clearly spent a lot of time digging thru various archives to piece together this fascinating bit of historical brain candy.  One amusing little tidbit is the fact that the Institute's kitchen staff complained that the engineers building the first computers at IAS consumed too much tea and sugar.  Early example of the alpha-geek diet of caffeine and sucrose!

To read a really insightful article about Google's future and the presumed importance of creating user lock-in, see Charles Ferguson's excellent piece in Technology Review