Social Software - Debates or Design Choices

Debates or Design Choices

Social software may be better understood as a set of debates or design choices, rather than any particular list of tools. Broadly conceived, there are many older media such as mailing lists and Usenet fora that qualify as "social". However, most users of this term restrict its meaning to more recent software genres such as blogs and wikis. Others suggest that the term social software is best used not to refer to a single type of software, but rather to the use of two or more modes of computer-mediated communication that result in "community formation." In this view, people form online communities by combining one-to-one (e.g. email and instant messaging), one-to-many (Web pages and blogs) and many-to-many (wikis) communication modes. Some groups schedule real life meetings and so become "real" communities of people that share physical lives.

Most definers of social software agree that they seem to facilitate "bottom-up" community development. The system is classless and promotes those with abilities. Membership is voluntary, reputations are earned by winning the trust of other members and the community’s missions and governance are defined by the members themselves.

Communities formed by "bottom-up" processes are often contrasted to the less vibrant collectivities formed by "top-down" software, in which users' roles are determined by an external authority and circumscribed by rigidly conceived software mechanisms (such as access rights). Given small differences in policies, the same type of software can produce radically different social outcomes. For instance, Tiki Wiki CMS Groupware has a fine-grained permission system of detailed access control so the site administrator can, on a page-by-page basis, determine which groups can view, edit or view the history. By contrast, mediawiki avoids per-user controls, to keep most pages editable by most users and puts more information about users currently editing in its recent changes pages. The result is that Tiki can be used both by community groups who embrace the social paradigm of mediawiki and by groups who prefer to have more content control.

By design, social software reflects the traits of social networks and is designed very consciously to let social network analysis work with a very compatible database. All social software systems create links between users, as persistent as the identity those users choose. Through these persistent links, a permanent community can be formed out of a formerly epistemic community. The ownership and control of these links - who is linked and who isn't - is in the hands of the user. Thus, these links are asymmetrical - you might link to me, but I might not link to you. Also, these links are functional, not decorative - you can choose not to receive any content from people you are not connected to, for example. Wikipedia user pages are a very good example and often contain extremely detailed information about the person who constructed them, including everything from their mother tongue to their moral purchasing preferences.

In late 2008, independent analyst firm CMS Watch argued that a scenario-based (use-case) approach to examining social software would provide a useful way to evaluate tools and align business and technology needs.

Methods and tools for the development of social software are sometimes summarized under the term Social Software Engineering. However, this term is also used to describe lightweight and community-oriented development practices.