Wordpress

LiveBlog of Matt Mullenweg's Keynote --

Streamed at http://ustream.tv/channel/nv08 (at least some of it)

Note: This liveblog is rough -- just notes, no editing

Beginning blog platforms --
Open Diary -- 1998
LiveJournal -- 1999

5 years ago -- based on B2

Over 7 million downloads

MM on what Bloggers want -- "Bloggers hierarchy of needs"

1. Expression
The most important tab on the WP blog is the Presentation tab -- allows people to change the theme

A lot of successful web 2.0 companies are successful because they protect users from spam communication

Introductory Notes

These are some thoughts in progress -- I've been thinking these things through for probably the last few years, but things have been getting more interesting of late.

Some of the blog posts that have helped shape my thinking here include:
http://bavatuesdays.com/proud-spammer-of-open-university-courses/
http://weblogs.elearning.ubc.ca/brian/archives/044998.php

A mildly edited version of my response to Jim Groom's post over on the bava --

D'Arcy mentioned the need for this to scale, and he's right. With that said, I don't think we need to have scalability to 100K students as a first goal. The beauty of the small pieces loosely joined is that it's easier, and that it's a step away from the monolithic LMS's so beloved by so many --

Toward that end, it's good to consider what we'd need to carry from the blog to the aggregator in order to connect a student work with an institutional SIS/LMS. To start, I see two factors as essential: first, mapping a feed to a student, and second, mapping individual posts from within a feed to a course.

Over the last two nights, I put some time into building out a rough proof of concept showing some of what can be accomplished via a good aggregator and Drupal's taxonomy structure.

We've been thinking about/using aggregation in a variety of ways for the last couple years, but the development of the FeedAPI has created some pretty amazing possibilities faster than we could have hoped. I've been meaning to build out a site like this for the last few months, but a couple of recent conversations stirred me into actually doing it.

What has been fun about building out this proof of concept was how quickly the site came together. It's rough, and has no graphic design component at all, but the core functionality came into place quickly.

The results are here, and I'll include the brief description from the homepage of the site.

First, the useful details:

• All content on the site can be searched via the site's search.
• Full text of all imported posts available here.
• A Directory of all keywords available here.
• The obligatory tagcloud here.
• And the feed list here.
• Posts can also be listed and filtered by keyword and author.

This site is designed to show the utility of a single location as a collection point of content from disparate sources, and how that content can then be re-organized by use of keywords to categorize the content that has been imported.

On this site, all imported content retains all keywords added to the post by the author. Additionally, new keywords are added to posts on import to allow for the content to be searched and organized in other ways.

A brief technical overview:

If you are not a geek, you can stop reading here. If you are a geek, read on!

• This site uses Drupal as the main framework.
• As this site is a proof of concept, we kept things light. The only core modules in use are Menu, Search, and Taxonomy. This site uses no path aliases, and the theme is the lightly modified Zen theme that ships with DrupalEd.
• Aggregation is handled by the FeedAPI, and extended by the Feed Element Mapper.
• The Similar By Terms module handles the content recommendations that can be seen alongside posts (see here for an example).
• The Views module generates several of the screens for displaying and navigating the imported content, and the Views Bonus module extends these views.
• Finally, CCK is installed and enabled (although, for this implementation it could probably be eliminated if necessary); and HTML Corrector is installed to clean up any unclosed tags that on imported feeds that could break the layout.

For those keeping track of such things, this site has taken a grand total of six hours to build, including this writeup. The functionality of this site is all achieved using modules and code currently available within the Drupal community.

One group of folks deserve a special mention: the team of people behind the FeedAPI module. For those interested, you can see a lot of the discussion at the RSS and Aggregation group. They planned and executed a great project, and without their work this site would not be possible.

I'll admit it at the outset: I'm in a bad mood today.

But when I see things like this, and this, and this, all talking about running courses in Facebook, I can't help myself

(Okay, really I can. But in this case, I don't want to).

Read Facebook's terms of service.

The "User Content Posted on the Site" section is particularly relevant here:

When you post User Content to the Site, you authorize and direct us to make such copies thereof as we deem necessary in order to facilitate the posting and storage of the User Content on the Site. By posting User Content to any part of the Site, you automatically grant, and you represent and warrant that you have the right to grant, to the Company an irrevocable, perpetual, non-exclusive, transferable, fully paid, worldwide license (with the right to sublicense) to use, copy, publicly perform, publicly display, reformat, translate, excerpt (in whole or in part) and distribute such User Content for any purpose on or in connection with the Site or the promotion thereof, to prepare derivative works of, or incorporate into other works, such User Content, and to grant and authorize sublicenses of the foregoing.