What makes Hubzilla special?
(principal Hubzilla developer) writes:
Hubzilla represents what I like to think of as state of the art in decentralisation technology. It goes far beyond what we did in Friendica when it comes to decentralising core services which used to be available only on centralised silos. We decentralise everything. This builds on work I started in Friendica but it took a platform re-write to fully realise. History of Hubzilla
Some federation bits were added a couple of years ago due to popular demand, but they are in conflict with a couple of core features such as nomadic identity. Nomadic identity is really special. You can create online clones of your channel and pop up at another site if your current site is having issues (either temporarily or permanently). This works incredibly well - unless you have friends on other networks. My original account has moved a few times now. All my original friends are still there. My Friendica and Diaspora friends however are not. They need to be reconnected, and this is silly because nomadic identity was created to address that problem.
The other feature we've spent a lot of time on is decentralised access control. This means you can publish webpages, videos, photos, create chatrooms, etc. and all of your web properties can have privacy settings that work seamlessly with anybody on Hubzilla. They don't need to have an account on your site. We can also create 'access tokens' and allow permissions to folks that don't have hubzilla accounts, so you can share a private video with your mom (as an example).
These features are totally alien to most every other network and service and you can't just create a patch to make them work. It's a completely different way of looking at the world and would take a complete re-write of most projects to realise or make compatible. As a result we were kind of forced to develop an entire suite of web publishing and cloud storage components which work with our services. This represents over four years of evolution from the original Friendica code base, so the projects are now quite different.
- A history of the origins of Hubzilla, and the thinking that went into its design. The Do-Everything System: An in-depth review of Hubzilla 3.0.
- A detailed review of Hubzilla's features. By @Sean Tilley List of Hubzilla hubs
- A list of Hubzilla hubs, some of which have open signups. Custom themes for Hubzilla
- Change how Hubzilla looks. Similar to Wordpress themes. Hubzilla Support Forum
- Go here to ask questions about installing Hubzilla, using Hubzilla, or feature requests. Hubzilla Development
- Go here to hang out with the developers, ask detailed technical questions. Hubzilla Issues
- Hubzilla's Github Issues page. Go here to submit bug reports, UI issues, and feature requests. Hubzilla's Github
- Hubzilla's Github page. Go here to download the latest copy of the code. Fork Awesome: A fork of the iconic font and CSS toolkit.
- The icon kit used by the Hubzilla project. Hubzilla documentation, for users, admins, and developers.
- Official documentation for the Hubzilla project. Note that you can also reach the documentation by selecting "Help" from the hamburger menu in the top right. A list of all apps/plugins/addons available for Hubzilla software.
Note that not every Hubzilla installation offers all of these apps. Go to /siteinfo/json ( of your hub) to see the the list of apps install on your hub. For example, https://start.hubzilla.org/siteinfo/json
shows all the apps available on https://start.hubzilla.org
. Hubzilla e-commerce app
- preliminary e-commerce app Mike Macgirvin post
on the difference between articles and cards:
Articles do not federate naturally. They are interactive. So think of it like an old fashioned blog.How to update a Hubzilla site from Github
Articles can provide summaries. These do not use industry standard methods of providing summaries since Mastodon has turned all of these into 'content warnings'; basically precluding anybody using them for summaries ever again.
Webpages are not interactive. Cards are interactive and actually very similar to articles but differ in the fact that one is called a 'card' and one is called an 'article'; and therefore readers might have different expectations of what they are and what they do. (The simple answer is that one is a 'card' and the other is an 'article'.)
A lot of people seemed concerned and upset that we provided webpages and cards and wikis and interactive posts but did not have a thing called 'articles'. Now we do.
Hope this clears things up.
Incidentally you can also provide summaries in posts and comments, but don't do it. The reason is that these could federate with Mastodon and Diaspora and GNU-Social and the summaries won't work in other networks (because Mastodon has made it impossible or impractical to try and translate to standard 'summary' fields without generating warnings). So we don't translate it at all. Readers on other networks will see a mess. Save summaries for 'articles'. That's what they're there for.
Missing at this point is separate feeds for articles (and cards and perhaps webpages). This would be a useful tool except for the fact that feeds use standard communication formats which provide separate 'summary' fields and Mastodon has pretty much fucked these up for everybody. So that's why we don't have article feeds. We might be able to provide 'summary' feeds and separate 'article' feeds at some point but it would be so much better to just rid the world of Mastodon so we could do this the right way once and be done with it.
git clone https: //github.com/redmatrix/hubzilla.git mywebsite
- and then you can pick up the latest changes at any time with
For keeping the addon tree updated, you should be on your top level website directory and issue an update command for that repository.
Another option is
This updates the add-ons as well.
What's the difference between webpages, cards, articles, and wikis?
webpages: building webpages
cards: planning and organising
articles: Authored works and long form content