Difference between revisions of "social computing/federated"

from HTYP, the free directory anyone can edit if they can prove to me that they're not a spambot
Jump to navigation Jump to search
(→‎Links: related blog post on Friendika)
(→‎Links: Salmon Protocol)
Line 27: Line 27:
 
* {{wikipedia|Distributed social network}}
 
* {{wikipedia|Distributed social network}}
 
* [http://www.w3.org/2005/Incubator/federatedsocialweb/ W3C Federated Social Web Incubator Group]
 
* [http://www.w3.org/2005/Incubator/federatedsocialweb/ W3C Federated Social Web Incubator Group]
 +
* [http://www.salmon-protocol.org/ Salmon Protocol]: a standard protocol for comments and annotations to swim upstream to original update sources...  open, decentralized, abuse resistant, and user centric.
 
===to file===
 
===to file===
 
* '''2011-07-09''' [[URL/to file::http://project.friendika.com/node/123|We need a decentralised social web more than ever before]]
 
* '''2011-07-09''' [[URL/to file::http://project.friendika.com/node/123|We need a decentralised social web more than ever before]]

Revision as of 02:07, 26 October 2011

About

Distributed social computing is social computing which is does not depend on a single server or operator; it can continue to operate even if some of the servers on which it is hosted are taken off the internet for any reason.

Terminology

Synonyms for "distributed" in this context include "decentralized", "peer-to-peer", and "federated". "Social computing" may also be referred to as "social networking", and a social computing application may be called a "social network", although those terms have slightly different meanings; see social computing.

Goals

The primary goals of distributed social computing are:

  • to prevent concentrations of arbitrary power, which is prone to abuse (see issuepedia:Google+/policy/naming)
  • to ensure that the social network can survive various events:
    • server failure
    • company failure
    • domain name seizure
    • internet connectivity disruption

Given that each node in a distributed network helps satisfy these goals, we will want to maximize the number of different implementations of the network. Any design for distributed social computing software should therefore be platform-agnostic.

In Testing

These both provide a server running the software (partly as a demonstration, partly for testing, and partly as a fallback for those who don't want to install the software themselves) and also provide the software. So far, all known distributed social network services and software are provided for free, as it would be very difficult to impose a fee without driving users away.

  • Appleseed (site): this purports to be distributed, but after installing it and playing around with it for a few minutes, I can't see how to connect it to other nodes. This may be a feature to be added later. Other features did not seem to be working correctly. --Woozle 21:31, 18 August 2011 (EDT)
  • Diaspora (site): this software appears to be somewhat more difficult to install, so I have not yet installed it. One criticism is that it was written by inexperienced student programmers who have not built in adequate security; another is that it seems to have burned through its startup funding (obtained through startup.com) and lost momentum, so it may be on its way out -- although interest in distributed social networking has revived considerably in the wake of the Google+ "Real Names" fiasco. --Woozle 21:31, 18 August 2011 (EDT)
  • Friendika appears to be fairly far along, and successfully connects to Facebook, Diaspora, and supposedly Twitter.
  • Safebook (site) is especially privacy/security conscious
  • StatusNet (site) appears to be designed for federation, and also supports OAuth/OStatus

Under Development

FeedFerret is still in the concept stage.

Links

to file