We are happy to announce the availability of the release candidate for the upcoming Friendica 2022.05 release, to focus on fixing existing bugs and smoothing out of rough edges..

Since the release in March

• a regression was fixed that could lead to mentioning all accounts that received a non-public posting;
• the Dansk (da_DK) translation was added to the repository;
• the API was enhanced;
• there is an experimental setting to allow postings in the past (#11411);
• an addon was added which allows the usage of S3 services for the file storage back-end.

If you are running a custom addon, please note that the 2022.05 release does a breaking change removing the hooks settings_form and settings_post. Your addon should use the addon_settings hook instead.

What is Friendica

Friendica is a decentralised communications platform, you can use to host your own social media server that integrates with independent social networking platforms (like the Fediverse or Diaspora*) but also some commercial ones like Twitter.

How to use the 2022.05 RC Version of Friendica

If you want to help in the relase process, you can checkout the 2022.05-rc branch from the git repositories (core and addons).

git fetch
git checkout 2022.05-rc
git pull
bin/composer.phar install --no-dev

Note that you only need to pull the composer dependencies in the core repository. Alternatively you may download the tar archives from files.friendi.ca.

Should the upgrade process of the database get stuck

If you encounter this, please initiate the DB update manually from the command line by running the script

./bin/console dbstructure update

from the base of your Friendica installation. If the output contains any error message, please let us know using the channels mentioned above.

What to do with Quirks

The 2022.05-rc phase is meant to identify and preferable resolve quirks and bugs that should not be in the 2022.05 release. So if you switch your node to the 2022.05-rc version of Friendica, please let us know about rough edges you find, either at the issue tracker (github account required), in the support forum or in the development forum.

Thanks a lot for helping with the release 🙂