Three days ago, Hubzilla contributor Mario Vavti announced the latest stable release of Hubzilla, version 3.2. In his own words:
The Hubzilla 3.2 release cycle was mostly dedicated to performance and usability improvements. We have managed to significantly improve the performance of item table queries. This means that the network and channel streams and also the notification updates are loading significantly faster now. In fact the whole app feels snappier.
That’s not all. This release implements the latest version of the Zot protocol, zot6.
This saves a verification callback and basically doubles delivery performance on both ends of the connection.
Aside from internal improvements to querying and federation performance, here’s what else landed in the new release:
Hubzilla now officially supports the Fork Awesome project, which supports logos for many other federated networks and open source projects. This is now the default icon set for the platform; a positive side effect is that it will be possible to use all of the new icons in the set.
New member widget
The new user registration flow now includes a handful of helpful links for getting started with the platform. This is part of a wider goal to streamline the user experience surrounding initial registration and creating a channel, with the goal of making the system a little easier to navigate in the beginning.
It’s also now possible to define what page users redirect to after registering a channel.
Hubzilla core now has a native articles feature, but it’s still fairly alpha quality — for instance, articles are currently designed to be read from the index view, and the article contents are only shown when clicking the View Article link.
The experience is a little jarring for anyone that’s used to publishing on WordPress or Medium, but with some further improvements it could become a serious contender against either, with the added bonus of federated comments.
Local Public Streams
In previous Hubzilla releases, it was possible to create a public stream that included all public posts that the hub was aware of. Now, it’s possible to do the same thing, but with only local content. This can be particularly helpful for hubs that are trying to build communities centered around specific topics or audiences.
Hubzilla also accepts donations via Bountysource: https://salt.bountysource.com/teams/hubzilla