As it is apparently hard to create a new page on wikipedia, here is the draft version of hubzilla page. A draft could be deleted and as this page is not bad and could be copy just in case.
Hubzilla (formerly known as Redmatrix) is a community management platform that is designed to mesh with other instances running the same software. It is considered a platform for federated networking, and is compatible with both Diaspora and Friendica. Hubzilla is notable for combining aspects of social networking, blogging, forums, cloud storage and content management all into one application.
In 2012, Mike Macgirvin of the Friendica project stepped down, and formed an experimental communication platform named Friendica Red. This system existed for exploratory purposes, and was designed based on lessons learned from developing Friendica.
Much of the design concepts for the new platform would be based on ideas about user identity management and privacy permissions. It leverages a unique federation protocol named Zot, which acts as the design successor to Friendica’s DFRN protocol.
As time went on, Friendica Red was rebranded RedMatrix, before the name Hubzilla was decided on. On December 24th, 2015, Hubzilla 1.0 was officially launched.
Hubzilla can be defined as a decentralized communication and publishing platform. Any server running Hubzilla is defined as a hub, which can function independently of any other hub in the network.
Channels are a core concept for the platform – in short, each channel is an activity stream of objects that can represent a specific action, such as a posting a status or uploading a photo. This stream can show both public and private activities, and an ACL permissions system determines which users can access a given entry. Each channel also contains a unique Webfinger address, for example https://example.com/channel/bob would be represented as email@example.com
A Channel can be created for the following use-cases:
- A Social Stream
- Branded Product Streams
- Group Forums
A user is assigned their first channel upon registration, but they can create as many different channels as their hub allows. Each channel in turn can connect to another channel as a contact. This mechanism will allow a user to interact with posts, as well as post on the wall of other channels as themselves. Private messages and statuses can also be passed back-and-forth from one connected channel to another.
MagicAuth is a type of in-browser encryption that grants access permissions on remote hubs. In a sense, it is a workaround to a long-standing problem in federated social networks: ordinarily, users couldn’t visit each other’s profiles and directly interact with them if both people are connected through different servers. MagicAuth exists as a means of granting access permissions to visiting users. The use-case works like so:
- Bob’s channel is on https://example.com/channel/bob, with the channel address of firstname.lastname@example.org
- Bob visits Alice’s channel at https://othersite.com/channel/alice, ie, email@example.com
- When Bob visits, his browser session performs a cryptographic handshake with Alice’s channel
- Bob is allowed to comment and like posts on Alice’s channel while he is visiting.
- Bob will also see private posts meant for him when visiting.
- If Alice allows people to make posts on her wall, Bob will be able to do that as well.
By default, each channel is given DAV access for file storage. This storage includes uploaded photo albums, and can allow for videos and other documents. Cloud storage can be accessed through a DAV client, and in some instances be integrated into the desktop file manager itself.
Channels are allowed to create web pages based on a templating system.
Themes and Layouts
Hubzilla can also function as an OpenID provider, allowing users to log into OpenID-enabled sites with their Hubzilla channels.