Group items tagged

Internet learning promises to make intellectual life more sterile and abstract than it already is — and also, for teachers and for students alike, far more lonely

The Internet teacher, even one who responds to students via e-mail, can never have the immediacy of contact that the teacher on the scene can, with his sensitivity to unspoken moods and enthusiasms.

I think that the best of those lecturers are highly adept at reading their audiences. They use practical means to do this — tests and quizzes, papers and evaluations. But they also deploy something tantamount to artistry. They are superb at sensing the mood of a room. They have a sort of pedagogical sixth sense. They feel it when the class is engaged and when it slips off. And they do something about it.

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.

Although we find ourselves as travelers in the age of over sharing, it turns out we remain quite adept at avoiding the really tough topics.

Google’s Eric Schmidt recently stated that every two days we create as much information as we did from the beginning of civilization through 2003. Perhaps the sheer bulk of data makes it easier to suppress that information which we find overly unpleasant. Who’s got time for a victim in Afghanistan or end-of-life issues with all these Tweets coming in?

Between reality TV, 24-hour news, and the constant hammering of the stream, I am less likely to tackle seriously uncomfortable topics. I can bury myself in a mountain of incoming information. And if my stream is any indication, I’m not alone. For me, repression used to be a one man show. Now I am part of a broader movement — mass avoidance through social media.