server:~# a2dissite silverhaze.eu Site silverhaze.eu disabled. To activate the new configuration, you need to run: service apache2 reload server:~# service apache2 reload [ ok ] Reloading Apache httpd web server: apache2. server:~# postgres@server:~$ dropdb hubzilla postgres@server:~$
Hubzilla was a nice thing to try out, but I don't think that I've gained much benefit of this, because I also have #Friendica node running for years and a #Mastodon instance running for some time now.
Hubzilla is a nice software for what it is: a complete set of web applications. When you only want to have some kind of social web for the #Fediverse it's maybe a little over the top and you might want to try out Pleroma instead or others.
For me it made no sense to support three different software stacks for federation in my (few) spare time and Hubzilla was some kind of doubling the same sort of task that #Friendica was always giving me for years. I felt more comfort with Friendica than with Hubzilla, although Hubzilla has some positive aspects for me as well:
- it runs on #PostgreSQL database. Although the PostgreSQL support could be better (some DB updates are reguarly failing and need a hands-on) this is a big plus for me, because I think PostgreSQL is the better database. MySQL seems to be a memory and disk I/O hog, but that's the only negative thing I can say about Friendica in comparisons to Hubzilla.
- I liked the concept of "Channels" in Hubzilla. In Friendica you need to create a second account with the same mailaddress, connect both accounts and "Manage" the other profile. I think the way how Hubzilla solves this kind of "multiple" accounts with different "Channels" is better and far easier to handle. I would love to see "Channels" as a feature in Friendica as well...
In the end it was not a decision against Hubzilla, it was a decision for more spare time and less administration effort on the server. I believe, Hubzilla will still do well without my small hub (although it was once placed on place no 7 at https://the-federation.info/hubzilla ).
Some weeks ago I also started my Mastodon instance on https://nerdculture.de/ which is still quite small.
But somehow Hubzilla seems to be a little awkward or strange in my eyes. For a public hub some features are missing in my eyes. For example a user quota for uploaded files. I do miss that feature in Friendica as well, but the situation in Hubzilla is worse, because you can also enable generic websites, WebDAV, generic Files etc. in Hubzilla. It's more like "one size fits all" approach. If you don't have Nextcloud, you can use Hubzilla. If you don't have a blog, you can use Hubzilla. etc.
But I never got really warm with Hubzilla. One main advantage in my eyes is that it can run on PostgreSQL as a database.
So, I'm thinking of shutting down my Hubzilla hub at the end of the year to give the users enough time to move away...
But maybe I haven't understood #hubzilla yet and missed some points? If so, please shout and convince me to continue my hub...
All of those social networks do have their own focus:
Friendica: basically can connect to all other social networks, which is quite nice because there exists historically two different worlds: the Federation (Diaspora, Socialhome) and the Fediverse (GnuSocial, Mastodon, postActiv, Pleroma). Only Friendica and Hubzilla can federate with both: Federation and Fediverse.
Friendicas look&feel appears sometimes a little bit outdated and old, but it works very well and reliable.
Hubzilla: is the second player in the field of connecting both federations, but has a different focus. It is more of one-size-fits-all approach. If you need a microblogging site, a wiki, a cloud service, a website, etc. then Hubzilla is the way to go. The look&feel is a little bit more modern, but there are some quirks that appears a little odd to me. A unique feature for Hubzilla seems to be the concept of "nomadic accounts": you can move to a different hub and take all your data with you. Read more about that in the Hubzilla documentation.
Mastodon: this aims to be a replacement for Twitter as a microblogging service. It looks nice and shiny, has a bunch of nice clients for smartphones and has the largest userbase by far (which is not that important because of federation).
But the web GUI is rather limited and weird, as far as I can tell after just some days.
Technically spoken these are the main differences:
- Friendica: MySQL/MariaDB, PHP on the server, Clients: some Android clients, no iOS client
- Hubzilla: MySQL/MariaDB or PostgreSQL, PHP on the server, Clients: don't know, didn't care so far.
- Mastodon: PostgreSQL, Ruby on the server, Clients: many iOS and Android clients available
I'm not that big Ruby fan and if I remember correctly the Ruby stuff turned me away from Diaspora years ago and made me switch to Friendica, because back then it was a pain to maintain Diaspora. Mastodon addresses this by offering Docker container for the ease of installation and maintenance. But as I'm no Docker fan either, I followed the guide to install Mastodon without Docker, which works so far as well (for the last 3 days ).
So after all my Friendica node is still my favorit, because is just works and is reliable. Hubzilla has a different approach and offers a full set of webfeatures and nomadic accounts. The best I can say about Mastodon at this moment is: it runs on PostgreSQL and has nice clients on mobile devices.
Here are my instances:
- Friendica: https://nerdica.net/
- Hubzilla: https://silverhaze.eu/
- Mastodon: https://nerdculture.de/
PS: "A quick guide to The Free Network" by Sean Tilley on https://medium.com/we-distribute/a-quick-guide-to-the-free-network-c069309f334