Also, it wasn’t until the end of the course that I realize now nicely the Flick browser could have complimented the weekly assignments. If a student were to open all their accounts on week #1, *and* configure Flock for them, they might find subtle ways to experience them earlier in the course. On the other hand, Flock can be a bit confusing when you’ve got it configured for a lot of social sites.

Do you recall anyone in class mentioning using the Flock browser? I had thought about bringing it up one or twice. I don’t have much use for it, but it sure is interesting. Like the delicious and diigo toolbars, Flock doesnt’ do what I need, but it does something similar.

Diigo’s annotation system would be an incredible tool for helping workgroups discuss their own online presence. For example, imagine that your workgroup maintains a series of subject guides your library website. As the subject guides grow, it becomes harder to organize them and the group has many ideas and opinions for how to make the more useful but it’s hard to make a decision.

Using the Diigo Toolbar, each member of the group can review the subject guides, and highlight those sections they would change. They can add “sticky” notes to comment on the page as a whole.

Of course, since Diigo is also open to the public, if your audience also uses Diigo, you can solicit or get unsolicited feedback through the annotations of others.

And that’s just ONE idea.

Diigo annotations do beg a big open question about privacy though. When you have the toolbar on, by default, every URL you visit is sent back to Diigo. They say they don’t record that info; they just use it to look up the annotations to show you. Fair enough. The open question is do the risks outweight the rewards. In this case, the rewards look very good (social bookmarking with a more human communication angle… nice).