path: root/README


             
Friendica RED
=============

Red is essentially a "personal CMS" linked to a decentralised permissions and communication platform. This creates a grid of small servers which link together to form a much larger system (much like the internet itself).  This allows one to create services with social contexts and extensible permission controls which are all integrated together as if they were offered by a single large data provider - but without the inherent privacy problems and costs associated with centralisation. Privacy and access controls are instead maintained at the local level where they can be enforced by those who own the data being shared. Additionally, identities in Red are not tied to DNS endpoints and have some degree of mobility between providers.

For example, let's say "Iggy Normak" is a colleague of mine. I can create a web service called "Mike Macgirvin" which acts as a blog or social networking hub, and share files and data with Iggy. These are stored on my website, which is served by a small hosting provider. Iggy can access my private photos from anywhere on the web, while logged into any Red website (for instance, from Iggy's own business website) - without encountering any additional authentication dialogues. Nobody else is able to access these files and photos without my permission, even if they "guess the URL". This kind of decentralised access control is somewhat unique and opens up new possibilities for creating very large scale web services from smaller operators, providers, and website designers.  
 
Red has somewhat limited functionality at the present time, and is being provided as a "developer preview". The communication layers, authentication and permission systems are all basically functional. Much development work remains. Red is free and open source distributed under the MIT license.
Friendica RED
=============

Red is essentially a "personal CMS" linked to a decentralised permissions and communication platform. This creates a grid of small servers which link together to form a much larger system (much like the internet itself).  This allows one to create services with social contexts and extensible permission controls which are all integrated together as if they were offered by a single large data provider - but without the inherent privacy problems and costs associated with centralisation. Privacy and access controls are instead maintained at the local level where they can be enforced by those who own the data being shared. Additionally, identities in Red are not tied to DNS endpoints and have some degree of mobility between providers.

For example, let's say "Iggy Normak" is a colleague of mine. I can create a web service called "Mike Macgirvin" which acts as a blog or social networking hub, and share files and data with Iggy. These are stored on my website, which is served by a small hosting provider. Iggy can access my private photos from anywhere on the web, while logged into any Red website (for instance, from Iggy's own business website) - without encountering any additional authentication dialogues. Nobody else is able to access these files and photos without my permission, even if they "guess the URL". This kind of decentralised access control is somewhat unique and opens up new possibilities for creating very large scale web services from smaller operators, providers, and website designers.  
 
Red has somewhat limited functionality at the present time, and is being provided as a "developer preview". The communication layers, authentication and permission systems are all basically functional. Much development work remains. Red is free and open source distributed under the MIT license.