Public domain federated communications server. Provides a feature rich ActivityPub and Nomad communication node.
Find a file
2015-05-06 21:43:15 -07:00
app first pass name change 2015-05-05 03:56:10 -07:00
assets second pass name change 2015-05-05 03:59:51 -07:00
doc Merge branch 'master' of https://github.com/redmatrix/redmatrix 2015-05-06 18:39:12 -07:00
images first pass name change 2015-05-05 03:56:10 -07:00
include Hopefully this will make item_cache the default 2015-05-06 21:43:15 -07:00
install convert ITEM_WALL from bitfield to standalone 2015-05-06 21:03:33 -07:00
library first pass name change 2015-05-05 03:56:10 -07:00
mod convert ITEM_WALL from bitfield to standalone 2015-05-06 21:03:33 -07:00
tests rev update, fix autoname test "random" failure 2012-04-26 01:33:41 -07:00
util Merge branch 'master' of https://github.com/redmatrix/redmatrix 2015-05-06 18:39:12 -07:00
vendor PostgreSQL support initial commit 2014-11-13 12:21:58 -08:00
view change notification colour 2015-05-06 21:25:59 -07:00
.gitattributes Required for github/Windows 2012-06-14 18:39:48 +10:00
.gitignore add reddress to profile - but all is not as it seems. Copy to clipboard is blocked because it isn't really a reddress and won't work if you copy it and try and use it somewhere. We should really convert the symbol back to '@' on copy and allow it to be copied, but this isn't as easy as it sounds and is left as an exercise for the community. If we just allow it to be copied we'll get a lot of bugs that making friends doesn't work. It does, but that isn't a legitimate reddress and even if we made allowances for it, Diaspora and Friendica and other webfinger based services wouldn't and would just say it can't be found or it's an illegal address. So if we block copy we'll just get bugs that it can't be copied. Eventually somebody will see this checkin and take it on themselves to figure out how to fix the address when copied to clipboard and then allow it to be copied. And there will be joy. 2015-03-07 23:35:56 -08:00
.htaccess cherry pick pull request #544 2014-07-24 19:07:04 -07:00
boot.php second pass name change 2015-05-05 03:59:51 -07:00
index.php second pass name change 2015-05-05 03:59:51 -07:00
LICENSE first pass name change 2015-05-05 03:56:10 -07:00
README.md i think this is 100 2015-05-05 13:42:05 -07:00
version.inc turn consensus items into diaspora polls for that network 2015-05-05 19:23:21 -07:00

Hubzilla - Hub Deployment Platform

Hubzilla

What are Hubs?

Hubs are independant general-purpose websites that not only connect with their associated members and viewers, but also connect together to exchange personal communications and other information with each other.
This allows hub members on any hub to securely and privately share anything; with anybody, on any hub - anywhere; or share stuff publicly with anybody on the internet if desired.

Hubzilla is the server software which makes this possible. It is a sophisticated and unique combination of an open source content management system and a decentralised identity, communications, and permissions framework and protocol suite, built using common webserver technology (PHP/MySQL/Apache, although Mariadb or Postgres and Nginx could also be used - we're pretty easy). The end result is a level of systems integration, privacy control, and communications features that you wouldn't think are possible in either a content management system or a decentralised communications network. It also brings a new level of cooperation and privacy to the web and introduces the concept of personally owned "single sign-on" to web services across the entire internet.

Hubzilla hubs are

  • decentralised
  • inherently social
  • optionally inter-networked with other hubs
  • privacy-enabled (privacy exclusions work across the entire internet to any registered identity on any compatible hubs)

Possible website applications include

  • decentralised social networking nodes
  • personal cloud storage
  • file dropboxes
  • managing organisational communications and activities
  • collaboration and community decision-making
  • small business websites
  • public and private media/file libraries
  • blogs
  • event promotion
  • feed aggregation and republishing
  • forums
  • dating websites
  • pretty much anything you can do on a traditional blog or community website, but that you could do better if you could easily connect it with other websites or privately share things across website boundaries.