Typepad Connect

| Share On Facebook | Embed

Just testing out Typepad Connect. Typepad Connect is Six Apart's version of Intense Debate or Disqus or any of the commenting services that serve to enable the "horizontal contributions" that Cole has written about.

Just like I have done previously with Intense Debate, I have disabled the built in comments for this entry and added comments powered by typepad connect. You can also check out my typepad connect profile page.

I'm just curious to get some sense of what this service has to offer. Please post a comment below and let me know what you think.

Intense Debate

| Share On Facebook | Embed

We had the first meetings this summer with TLT Faculty Fellow, Carla Zembal-Saul. Part of Carla's interest is related to the social and interactive elements of learning portfolios. We talked a lot about the "horizontal contributions" hashed out in Cole's post and vaguely eluded to in my previous post. We spent some time looking at other comment engines.

As an experiment, I have turned off the built-in comments for this post, and turned on comments powered by intensedebate.com.

Some features of intense debate:

  • post video comments (try it out, it's very easy)
  • view your or another's intense debate profile to see comments you have left across the web
  • comment voting
  • easily embed youtube video
  • easily embed polls
  • threaded comments
  • commenter profiles that include info such as last tweet, and links to other social sites.
  • login with openid
  • login with facebook connect

So, go ahead and comment below. Post some video comments. Vote some comments up and down. It's fun and easy!

It is raining. I am writing this from inside my car, to be posted on the web later. Here is something I am thinking about now.

Blog comments: Do we need a standard for some sort of blog entry object, where comments, and comment submission form can travel and be included in the recontextualization that happens with blog entries via RSS. For example, if I am running some sort of social hub for a class, and students' blog posts are flowing in to this space, wouldn't it be nice if the comments left on an entry at the aggregated space are in sync with the comments on the source blog. What if a blog provided a comment engine that acted in the more flexible manner of comment engines like disqus or facebook connect . The comments functionality could be embedded with the same post in any context. What if the the entry body that is included in the syndication feed also included the comments and the form? is that all we need to do?

My notes from James Boyle's keynote at UMW's Faculty Academy, "Cultural Agoraphobia: What Universities Need to Know about our bias against openness"

Pick between two networks:

Network 1: Users can perform a set of white listed functions. Only certain respectable entities can distribute information: a few universities, some newspapers, governments. Dumb terminals. functioning happens in the network center.

Network 2: Distributed, dumb network. Intelligence at the ends. We don't know what stuff is traveling on the network (text, sounds, video, maps).

network 2 will lead to porn, spam, idiots, ranting, stupid rumors, piracy. Anyone can connect to this. Whose gonna do commerce on this thing?

No one would have voted for network 2 in 1992.

Two models for encyclopedia to have information on anything and become an authoritative source:

Encyclopedia 1: Need best experts. going to have to be paid a lot. need peer reviewers. edit for style and consistency. enormous investment. strong copyrights to protect this investment. trademarks for logo to say this is the authoritative source.

encyclopedia 2: we'll create a site and people can put stuff up.

The difference between these two models relates to property rights, corporate organization.

Two software models:

Software model 1: machine code, drm, sold through license. Software model 2: open source.

Both worked. IBM makes twice from open source, than from paid portfolio.

West point:if you want a secure system you need an open system. Anyone is smart enough to come up with an algorithm that they can't break.

No one would think this 17 years ago. We are always wrong in one direction. In each time, the open version appeared that it was not going to work.

not claiming that open is always better. Sometimes we need closed systems for privacy or property rights.

There are reasons to believe that cognitively we skew to see more dangers and few benefits of open systems, and skew to see more benefits and less dangers of closed systems. This is the cultural agoraphobia.

behavioral economics: people don't think the way economists think that we think. We buy warranties even though they are not a good deal.

We are not risk neutral, we are strong risk adverse, the risk makes us feel disproportionate regret.

As a teacher you took methods, tricks, exam formats of other teachers and made them your own.

open materials aren't just free to copy, but are free to adapt, version, customize, just as with open source software.

We have flourishing open software, open encyclopedia, open network, but education is behind.

Academic presses: Tons of stuff. You can't buy book anymore. So clearly they are all available online? The daily show puts their stuff online for free. .

Empirical evidence that having books online for free drives sells up

In academia we have a blindness towards openness.

openness can cure openness: google pagerank. follow whre animals go to the water to find waterhole.

we (the audience) make decisions: Your instinct will be to clamp down on the side of control.

Other people will think of better stuff to do with our materials than we can. There are billion people wired out there.

Higher Education is being more timid than viacom. yes, there are risks. But there are concerns about losing audiences. With every type of literacy, there is point where there are conerns about opening up the franchise. Letting women vote, large scale reading of the bible in your native language, scribal conventioans that made it very hard to write, deliberately difficult - not a bug but a feature. lawyers: we have our own language. you need to pay us to speak it for you. "Law French"

design principles: default should be open. if not, burden of proof is on person seeking closed solution. Some items, like students social security numbers, will be easy to meet. Others like ed resources, will not be as easy.

Tech systems: make them open so users can modify with their behavior. Huge repositories with tons of meta data, costs millions of dollars. No one uses them. Not designed where user behavior modifies the system. (like google).

In pilot training you are trained not to trust your perceptions. We need to learn to distrust our cultral agoraphobia.

For a reason I am not entirely sure of, I decided to start playing with twitterfeed today. twitterfeed is a service that will periodically check rss feeds of your choosing and then post new items to your twitter stream.

I started by thinking how cool it would be if any time anyone posted anything at blogs@psu with the psuets tag, it could show up on the ETS twitter account. Same thing for posts tagged with tltsym09 and the TLT symposium twitter stream.

So, I figured I might as well try out this little tool before I get too far ahead of myself thinking of the opportunities. I hooked up this blog's feed to my twitter account.

It worked. Okay, so let's hook up my link blog, too.

Now I was hooked. I just posted content over at the blogs@psu news. Why not hook that up to my twitter account also?

Then the bell really went off. Ding! Why not hook up the comments feed of my blog up to my twitter account? I configured twitterfeed to only send the most recent new comment, checking every 30 minutes. So at most, one comment tweet will be sent every thirty minutes. This blog doesn't get that many comments, so in reality there will be far fewer tweets going out. Although with new comments being fed to twitter, that may very well change.

I have known for a while that one of the most important new features needed on blogs@psu is "email me followup comments" feature when leaving a comment on someone else's blog. Without this, conversations on a particular blog post can easily whither. Well, in the meantime this twitterfeed can help remedy that. maybe. We'll see.

One cavet to twitterfeed: you have to let it know your twitter password. It's really the only way something like this can work. I threw caution to the wind. You may not be as free-spirited. Update: As I was writing this, twitter launched it's oauth support, a more secure way to authorize api access.

After a few days out of circulation, I come back to find some posts on the PSU Voices I mentioned in my previous whiteboard post. The Reverend's and Cole's posts pretty much layout the potential and thinking behind this tool, so I don't feel a need to repeat it. Read their posts.

Along the lines of Jamie Oberdick's comment, what surprised me about this search page is that I have found myself using it for searching all these social sites at once. Getting the local (PSU) content mashed in with that is such an added bonus. I'm simultaneously getting the local and global results. I am curious to see where this path will lead us.

Erin Long and I visited Penn State DuBois this past wednesday to talk about blogs@psu and how it can be used for teaching and learning. I started out talking about blogging in general, and swung into personal content management and learning portfolios. Erin went through specific examples with Comm 180 and English 202 and how they used blogs in those courses. Lastly, we helped everyone get started with creating their own website with blogs@psu. There were around 14 people in attendance, a mix of faculty and staff. I had a great time meeting everyone. It was a lively group.

You can find our slides below. I am happy that these slides just served as a jumping off point for a conversation with everyone in the room.

Last Tuesday, Cole walked into my office and sketched out a picture of a page that would not only aggregate content from blogs@psu, but also pull in related content and media from around the social web.

whiteboard_psu_voices_1024.jpg

On Wednesday, I modified the blog search template to include these ideas

On Friday, it went into production. Check out the page on "democracy".

It was really easy to make this change. The point of this post is not to toot my horn in how quickly this idea was realized. The point is to highlight another example of the benefits of a platform we can easily build on to realize our ideas. All the details on this new page, and my ideas on where this is all might be going will have to wait for another time.

I have mentioned here and there my vision of blogs@psu as not just a rigid web publishing system limited to the templates and structures that those running the thing (like me) will bless, but more of a general platform for enabling all kinds of interactions on the web.

This is why I met Chris Millet's blog post today with such joy. He used MT's custom field feature to add a location field for the entries and modified the templates to generate a GeoRSS feed and embed a maps widget from yahoo. Check out his post. It is really cool.

What MT/blogs@psu needs to provide is a way for developers to easily package and share these features. I know they could become template sets, but I am thinking something more flexible: 1) Something that I don't need to install on the server and could continued to be maintained by the author (kind of like the way styles can be shared via stylecatcher) and 2) something that could be mix-and-matched. For example, I might want to add maps support to either a "classic blog" or a "professional website".

The future is now, my friends.

You may play these in any order you like, or all at the same time.

Oh no! embedding is disabled on the last video I wanted to embed. you'll have to click below to watch the last video:

http://www.youtube.com/watch?v=D6iEe_1kWqA

birdflu_screen.jpg

Brad manages the programming group in Education Technology Services.

Subscribe

Embed

Embed the headlines from this blog in another web page. Just copy and paste the embed code below.

www.flickr.com

Recent Comments

  • Brad Kozlek: Jim: I am thinking that the comment form itself be read more
  • Cole W. Camplese: I'm thinking hard about this one myself. I posted about read more
  • Jim: I think it would be that easy, just syndicate both read more
  • ELIZABETH J PYATT: Good notes. I think it shows that profit from openness read more
  • TK Lee: Thanks for sharing the notes. I found it helpful. The read more
  • ALLAN SHAWN GYORKE: It makes me glad that we set up the open read more
  • Brad Kozlek: Jim, that is a nice feature of jaiku. Twitter seems read more
  • Jim Leous: Brad -- this is interesting. How would you say that read more
  • Alan Levine: You will have 1,000,000 followers in no time at all. read more
  • laura: brad i just realized the title and subtitle of your read more