Hubzilla 3.4 Released!

For Hubzilla 3.4 we focused on overall usability improvements. A new permission role (social - federation) has been introduced. This is the most permissive role we provide and it aligns well with the capabilities of the protocols we federate with (diaspora, activitypub, ostatus).

An autosave functionality for posts and comments has been implemented. Posts and comments are now autosaved to the browsers local storage (no, we don't send your unfinished work to the server). If you accidentally reload your window or navigate somewhere else, you will not loose your work anymore. When you return back to your unsent post or comment, the text will be waiting there for you as if nothing happened. This functionality is enabled by default and can be disabled in additional features > post composition features settings if desired.

The technical skill level setting has been merged and streamlined with the additional features page. This makes it easier to adjust the skill level to a comfortable value.

Another important change to mention here is that the author menu has been moved from the item dropdown menu (bottom-right of posts and comments) to the author photo. All author related functions are now accessible directly by clicking the author photo.

Last but not least some of the redbasic theme schemas have been renamed to better reflect their purpose in the naming. The simple_* schemas are unmaintained at the moment and were therefore marked deprecated. If nobody from the community steps up and maintains them, they will be removed with the next release. Due to the renaming of the schemas you will have to set your schema again after your hub has been updated. This does not affect you if you are using the default schema (Focus).

Other notable changes:

  • Introduced trending tags for the public stream app
  • Implemented visible star status for starred posts
  • Fix issue where we were forced to log back in after leaving a delegated channel
  • Implemented last commented expiration setting for admins
  • Implement OAuth2/OpenIDConnect server
  • Chats are now saved obscurified in the DB (just like private mails)
  • Introduced a simple way to share links to wiki pages
  • The new member widget has been converted to a feature - it can now be turned on/off
  • Initial support for alternative sort orders on the cloud pages
  • Postgresql fixes
  • Introduction of the e-commerce/cart addon (beta - experimental)
  • Introduction of the fuzzloc addon - blur your browser location
  • Improved interoperability with mastodon (activitypub)
  • Numerous bugfixes and overall improvements

As always, a big THANK YOU! to all the translators and everybody who is helping to improve Hubzilla with each release.

Get it while it's hot!

To update an existing installation (installed via git) please execute util/udall from your Hubzilla webroot.
If you participated in the RC testing, remember to git checkout master (core and addon) before the update.

Please consider to support this project:

!Hubzilla Announcements  !Hubzilla Support Forum
@Ramdziana is still on 3.2.
Social - Federation is a new permission role and is not related to the federation plugins (diaspora, activitypub, ostatus).
I think you are confusing the new channel permission role "Social - Federation" with the ability to federate via the optional addons that must be installed by individual hub admins, Ramdziana. For reference, the help pages describe the new channel permission role like this:

The channel is a very permissive social networking profile which is compatible with other federated social networks. The permission policies are similar to Twitter and mostly compatible with Diaspora and Mastodon. Privacy is a lower priority than ease of access and connecting with others. Anybody in the network can comment on your public posts and send you private mail. By default posts and published items are public, but you can over-ride this when creating the item and restrict it. You are listed in the directory. Your online presence and connections are visible to others. This mode may increase your exposure to undesired communications and spam. This role is not generally recommended unless you need to interact regularly with members of other networks.  
Thanks for your explanation @Mario Vavti @Andrew Manning :) Yep, I knew between addons which I must enable when I want federation in my own hub and this new permission role in 3.4. I'm confuse when giac said about plugin, sorry english isn't my native language :D