Group items matching

in title, tags, annotations or url

readers by making it possible to hop around a book, to hand out individual chapters as assignments, and to take notes in highlighter yellow right on the text. The notes are sharable among a social network of students and instructor.

A caption, simultaneously spoken by a voiceover (They call this karaoke mode. It turns out to help memory better than either text or speech by itself) instructs me to tap the cells nucleus three times to simulate its breakdown.

learning modules built with Inkling will be priced individually on iTunes,

Russian Hacker Selling 1.5 Million Facebook Accounts

It’s generally a good idea to change your password periodically. It’s also advisable to ensure that your social networking passwords are all different and to generate difficult passwords that include numbers, capital letters and special characters, if at all possible. Roboform, PassPack and KeePass are a few free or affordable resources to help you manage your online passwords in a secure fashion.

Intimacy 2.0: Privacy Rights and Privacy Responsibilities on the World Wide Web

This paper examines the idea of privacy in the world of ‘intimacy 2.0’, the use of Web 2.0 social networking technologies and multimedia for the routine posting of intimate details of users’ lives. It will argue that, although privacy is often conceived as a right with benefits that accrue to the individual, it is better seen as a public good, whose benefits accrue to the community in general. In that case, the costs of allowing invasions of one’s privacy do not solely fall on the individual who is unwise enough to do so, but also on wider society.

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.