Group items tagged

Demand for Web 2.0 suicides increasing Posted on Friday 18 December 2009 I went to the suidicemachine and got this message

Tired of your Social Network? Liberate your newbie friends with a Web2.0 suicide! This machine lets you delete all your energy sucking social-networking profiles, kill your fake virtual friends, and completely do away with your Web2.0 alterego. The machine is just a metaphor for the website which moddr_ is hosting; the belly of the beast where the web2.0 suicide scripts are maintained. Our services currently runs with facebook.com, myspace.com and LinkedIn.com! Commit NOW!

ok the FAQ’s get eve better…..

What do you think are the most important features a social network should have? How would you prioritize them? Do you plan to Build Less or go big? If building less, what is the minimal set of features you can get away with? We plan to “build less.” These are the features which we aim to complete first: 1. A good secure protocol, encrypted at every leg, including a specification for a lightweight, probably HTTPS, RESTful set of routes. We see all of this communication happening between two Diaspora servers, rather than strictly between peers. We realize there is the problem with polling with this model, but we think there are several tricks worth trying which all have their relative pros and cons: PubSub (fast and easy, requires some level of centralization), querying friends servers from the browser side and posting responses back (requires browser side decryption) to name a couple. Alternatively, we are considering going with XMPP altogether due to the ability to be able to push content between nodes, but we need to research it further to see if it is something we would want to implement. 2. A datastore and corresponding interface that can store all of your stuff in one place. MongoDB is what we are looking at for V1, but the redundancy of TahoeFS is intriguing(as well as serving a slightly different purpose). 3. A clear extension framework. Diaspora will be service-agnostic and we will need to make it easy to import from and export to any format/web service. It is also our goal to make Diaspora as content-agnostic as possible, by providing abstract data types and an easily extended UI so that whatever new content people want to store and share can be integrated without re-rewriting parts of the whole application stack. 4. Be your own OpenID provider. Having a single identity across lots of services is great, but why trust a web service to hold it? Once we are the keepers of our own data, we can also selectively allow services access to it through Oauth.

I had my students this fall engage in social bookmarking, earning credit toward their class participation grade for doing so. I made sure to spend at least 10 minutes a week having students share their finds during class time, which means that the students’ finds were integrated with other class discussions and not just some out-of-class “busy work.”

I’ve set up a Diigo group for the course. I’ll invite my students to create Diigo accounts and join the group. In deference to FERPA, I’ll let students choose pseudonyms if they wish, as long as they let me know.

Diigo groups allow group members to comment on and “like” bookmarks shared with the group. These are features that Delicious doesn’t provide, and I’m eager to test them out with students. We live in a participatory culture, and our students expect to be able to interact with content they consume. “Liking” and commenting are interaction tools that my students should be comfortable using given their experiences on Facebook, and these tools should tap into students’ desires for community and sharing quite nicely.

One final comment, a funny one.  On Monday, in my "Twenty-First Century Literacies" class where laptops are required for a whole range of experiments and inclass collaborative work, I caught one of my students with his laptop open and with a book propped secretly inside it, reading away in his book when he should have been paying attention.   So maybe that's the next class, "Should Professors Allow Students to Use BOOKS in the Classroom Devised for Computer Learning?"   I'm being facetious but that's the point.  A book is a technology too.   How and when we use any technology and for what purpose are the questions we all need to ask.

Do you see the difference?   "Computer learning" doesn't exist.   In 2011, it exists less than it did a decade ago and, in a few years, that phrase won't exist at all.   Students learn.  Computers are tools for all kinds of things, from checking the Facebook page, to making notetaking easier, to being fact checking or calculating devices that can take a class to a more sophisticated level to interactive social networking devices that can either distract a class or allow for new forms of group collaboration.   There are many other uses as well.   The point is that most profs have (a) simply "adapted" (as a colleague told me recently) to computers without understanding the intellectual and pedagogical changes they can enable; or (b) resigned themselves to their present, gleefully or resentflly; or (c) made them into a pedagogical tool; or (d) all of the above.